On Wed, Feb 11, 2015 at 1:21 PM, Tom Hayward tom@tomh.us wrote:
On Wed, Feb 11, 2015 at 1:11 PM, Kurt ksaves2@sbcglobal.net wrote:
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
The non-working example you gave is how I program my AP510 every time, from Linux. I've only verified it works with the latest 20141008 (rx free) firmware. Is this the version you have?
As mentioned in a private email, Kurt actually has firmware version 20141215. Thanks for tipping me off--this is a new version I haven't tested, and it was not released through the same channels as previous versions.
I flashed my AP510 with the new firmware and it woke up in a boot loop. I was eventually able to get it to connect to the stock programming software and load the default configuration. This tamed it. This is a good indication that some significant internal changes took place between versions.
I snooped the serial protocol a bit and found they modified the command to put it into configuration mode. This is why Chirp is unable to read your AP510. I have not looked much farther than this, however I suspect they did not change the initialization on a whim, but to prevent accidental programming with software intended for older versions.
I will need to take a thorough look at the new protocol before updating Chirp. Hopefully I can support both the new and old protocols concurrently, unlike the stock software.
Tom KD7LXL