CHIRP

Hi,

I actually find this to be a strange response.... as the entire CHiRP project is dedicated to advancing the free and open access to hardware that is somewhat shunned by the traditionals - i.e. Icom, Yaesu, Kenwood and major manufacturers such as FTDI.

The reason that I raise the CH340G is in relation to its exposure out there with the Arduino "Clones" etc.

Note that I have been able to apply the CH340G in almost every application and see it work better than chips that are prices 10 - 100 times its price. The only application that I cannot see it functioning correctly in is CHiRP.

I have seen this error a number of times before in very early CHiRP versions....

Therefore perhaps it is worthy of investigation/reinvestigation?

Steve I

No, really. As Brian says, CHIRP has no idea which driver or chip you're using. It can't. It's insulated from all of that by the serial line discipline abstraction layer of the operating system. We have no existing code in chirp that is specific to any driver or chip because we can't.