Philipp Klaus Krause
Philipp Klaus Krause
On the other hand, VID and PID are permant. AFAIK the "Device" number can change if you unplug and replug the device.
I wonder if there is an ST-Link-specific identifier that we could use? Maybe the STM32 in it has a serial number that can be read out?
Since linusb -v can display the serial number, then I think stm8flash should be able to get it through libusb.
I'm in France for a few days, and have only an STM8A-Discovery here. When I'm back in Germany, assuming I'll find some time, I'll have a look at the pull...
I also encountered the problem with multiple "303030303030303030303031" serial numbers. However, I only see that number after having used stm8flash once with that programmer. On the first invokation of stm8flash...
In other places it was reported that the "303030303030303030303031" serial numbers after first use are an ST-Link/v2 firmware bug, and that updating the ST-Link/v2 to the latest firmware version will...
On the SDCC side, nothing needs to be done. SDCC already should support all pdk13, pdk14, pdk15 devices. pdk16 is not yet supported by SDCC, though. And SDCC currently only...
Actually, the current SDCC release 4.2.0 supports C11 by default (and C17 is just a clarification of C11).
Yes, then the code work with sv2v, but no longer with Icarus 11.
I've since refactored my design to use neither break nor disable. Still, both are in the Verilog standard, so the right solution would be to have both 1 (this ticket)...