Thanks. So here's a follow-up question. Here is the vendor's response, verbatim: "0x0187,B3:Wirelsee start,B2:function enable". Do you suppose the B3 and B2 refer to the third and second bits within the 0x0187 byte? Is that typical notation?On Wed, Jan 24, 2018 at 2:34 PM, Rhett Robinson <rrhett@gmail.com> wrote:Yes, hexdump prints each line as 16 bytes: two blocks of 8 bytes each, beginning with the address of the first byte. So, in your example:00000180 63 ff ff ff 32 ff ec f3 f2 87 44 03 14 23 01 01 |c...2.....D..#..|The first byte, 63 is at 0x180. The second byte, ff is at 0x181. The 7th byte, at address 0x187, is f3. After that it is f2 at 0x188, 87 at 0x189, 44 at 0x18a through 01 at 0x18f. So each block will be 0x???0 through 0x???f.Hope that helps!RhettOn Wed, Jan 24, 2018 at 11:13 AM, Rob Owens via chirp_devel <chirp_devel@intrepid.danplanet.com > wrote:-RobI understand the concept of different base numbering systems, but I'm rusty. And I'm brand new to this Chirp driver stuff...Is that the "f3" byte?Here are two consecutive lines from a 'hexdump -C' of a Chirp image:Based on information from the radio vendor (Leixen), I am interested in memory address 0x0187.
00000180 63 ff ff ff 32 ff ec f3 f2 87 44 03 14 23 01 01 |c...2.....D..#..|
00000190 0f 37 1d 65 05 f0 fc d3 00 0a 0a 00 3c 00 e3 3c |.7.e........<..<|
_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers