And I remember seeing that odd symbol when using those old drivers, but IIRC it did not prevent the drivers from working properly.

Those boards are very old and I don't think I have access to any, so I can't test. You might get some luck from searching our old forums. For example, I found these: https://www.flowcode.co.uk/mmforums/viewtopic.php?p=107881&hilit=eb006+driver#p107881 https://www.flowcode.co.uk/mmforums/viewtopi...

I'm not too familiar with ADC sampling on that particular chip, so bear that in mind and hopefully others will have a better answer. If it were me, I would first read at 12 bits and see if the speed is acceptable. It's probably not much of a difference to the speed, and there could be greater saving...

The other thing you could do is to edit the fcfx project file directly in a text editor. Although if you choose to do this, make sure you keep a backup of your file and thoroughly test because manually editing the file could invalidate it and cause it to fail to load. Also, any editing should be don...

Thanks for that. We're investigating and hope to have a fix for you soon.

Sorry, I don't know about this particular chip. But the "E-Blocks2 AVR Programmer" fcd might hold a clue. This one has the following section and maybe you need something similar: <configuration address='0x0000' mult='1' progonly='1' > <format><byte address='Low' value='0xFF' /><byte addres...

Can you please post a sample project with the error and we'll take a look.

Could it be that you have the v7/8 driver installed, but you need the v9 one? If so, try uninstalling the driver and downloading the one for v9.

Thanks for the suggestion. It might be a challenge to implement this, but I will add it to our list and think how we can do it.

Ben is more familiar with that part of FCD files than I am, but I think it's one or both of these 2 sections you need to pay attention to: The first is the use of the batch files and the "UsesComm" and "$(comport)" of the <programmer> section within <build>. The second is the <co...