<div dir="ltr">Hi,<div><br></div><div>On Tue, Feb 12, 2013 at 9:06 AM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> I subscribed to chirp_devel in digest mode. I've switched to per<br>
> message mode, and I just wanted to let you know I have read your<br>
> messages via that web interface and intend on:<br>
> Resending the patch with the headers you want.<br>
<br>
</div>Cool. Let us know if you need help.<br>
<br>
> Looking at bug #409.<br>
<br>
Suh-weet, thanks :)</blockquote><div><br></div><div style>There is an array of 6 VFO info structures of 128 bytes each starting at 064A in the dump. Each structure ends with a single checksum byte. Structures 0/1 are VFO A, 2/3 are VFO B and 4/5 might be a scratch area or the fm broadcast receiver. The checksum and duplication appears to be protection against power failure during structure updates (if 0 is corrupt use 1 etc). I've identified the field that seems to govern whether banks are available (u16 at offset 000A). It's FFFF until the manual workaround is applied, after which it is the active bank number. I've got more experimentation to do to identify more fields.</div>
</div><div><br></div>-- <br><div><span style="color:rgb(102,102,102)">Sean</span></div>
</div></div>