stolen / pico_cc_flasher

No-software RP2040-based flasher for CC25xx
MIT License
2 stars 0 forks source link

clock status 00 #2

Open ondras12345 opened 2 months ago

ondras12345 commented 2 months ago

Hi, I have flashed this firmware onto an RP2040-Zero board (git clone and make install), but when I connect a target CC2530, I only get

clock status 00

printed over and over on the serial port.

I tested two chinese CC2530 modules, the behavior is the same with both.

How should I proceed with debugging? I have already checked with an oscilloscope that there is a reset pulse (low for ~150 us), and there is some activity on both DC and DD pins.

ondras12345 commented 2 months ago

Without changing anything else, I programmed the target once using an Elnec BeeProg via ISP. After that, everything started working and this tool can both read and write flash. It seems like whatever comes pre-programmed in these Chinese modules breaks some assumptions pico_cc_flasher makes. Perhaps there are some readout protection fuses? I haven't studied the CC2530 datasheet yet.

I will keep the other target board unchanged in case you want to investigate this further.

bitblaster commented 2 months ago

Just happened the same to me on a new cc2531 module. The other 2 I have works without problems, but I flashed them before with a Raspberry PI. So I'll try to flash this one as well with the RPI and see what happens.

EDIT: confirmed working after flashing once with another method.

ondras12345 commented 2 months ago

Just for the record, before successfully flashing with BeeProg, I tried CCLoader on ESP8266 (Wemos D1 mini) and it errored out with "Verify failed!". It was doing pretty much the same thing with the chip completely disconnected (I think it just failed a bit sooner). So CCLoader won't work as an alternative method for first flashing.