On Wed, Dec 24, 2014 at 4:05 PM, Dan Smith dsmith@danplanet.com wrote:
I think I figured it out. The tests run against the .img files in the repository. The one for the Leixen isn't a good .img since it only read the memories and names.
It came from a real radio though, right? If so, we probably need to make sure it's still handled properly.
Yes. Straight out of my radio.
You can look in tests/logs/ for more details on each run and the associated failure.
The "Leixen_VV-898.img" in the repository has no data from 0x0000 to 0x0d00 (except for 0x0900 to 0x0906 which is the Custom Display message). The current driver intentionally skips over this area. This area is where all of the settings are. From 0x0D00 to 0x2000 are only channels and names.
The failure is because I am changing the match_model to look at a different area to detect the data file. The current place is editable by the OEM software and once the user changes it, CHIRP no longer detects the image and it had to be manually selected. The current driver fills almost all of the data from 0x0000 to 0x0D00 with 0xFF as it is skipped. The data that should be there for my patch to detect isn't there and it won't be until my first patch is approved.
What is the correct way to submit a image file for this. Just upload it to my issue?
If you do need to get a different image into the tree, you can email it directly to me or upload it to your issue. The latter is actually a little easier for me.
I have already uploaded it to my issue.
--Dan
Thanks, Jim