[chirp_devel] [ft-90] fix memmap to expose ID bytes to developer mode and fix demomsg fields #1187
# HG changeset patch # User Jens Jensen kd4tjx@yahoo.com # Date 1383659016 21600 # Node ID efaf2763449055559d5f423d66e222263f1ef749 # Parent 1c8ef954a71b6028c560e3203e8d5dc94809c4c5 [ft-90] fix memmap to expose ID bytes to developer mode and fix demomsg fields #1187
diff -r 1c8ef954a71b -r efaf27634490 chirp/ft90.py --- a/chirp/ft90.py Wed Oct 30 08:22:46 2013 -0500 +++ b/chirp/ft90.py Tue Nov 05 07:43:36 2013 -0600 @@ -52,6 +52,7 @@ _block_lengths = [ 2, 232, 24 ] + ([200] * 18 ) + [205] mem_format = """ + u8 id[2]; #seekto 0x22; struct { u8 dtmf_active; @@ -109,8 +110,9 @@ key_p2:4; u8 unk13:4, key_acc:4; - u8 demomsg1[32]; - u8 demomsg2[32]; + #seekto 0xF7B; + char demomsg1[50]; + char demomsg2[50]; } settings;
u8 demomsg1[32];
u8 demomsg2[32];
- #seekto 0xF7B;
char demomsg1[50];
char demomsg2[50];
Seeking in a structure like this is kinda nasty. Can you just declare some filler bytes to use up the space?
--Dan
updated this patch, including write delay fix for #1187
On Friday, November 15, 2013 8:31 PM, Dan Smith dsmith@danplanet.com wrote:
- u8 demomsg1[32]; - u8 demomsg2[32]; + #seekto 0xF7B; + char demomsg1[50]; + char demomsg2[50];
Seeking in a structure like this is kinda nasty. Can you just declare some filler bytes to use up the space?
--Dan
_______________________________________________ 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
participants (2)
-
Dan Smith
-
Jens J.