Chipshouter CW250 Dead But With Small Signs Of Life

One of our Chipshouters stopped responding to our script during one of our sessions.

I could not enter the terminal instead I was greeted with the string:

ZN0H51~

It seemed like it was resetting and each time it reset it would emit this string.

I wrote a C program to dump the serial port and this is the raw result.

(The first line is ZN0H51~)

5A 4E 30 48 35 31                  
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
00 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 
00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F 
5A 4E 30 48 35 31 
7E 16 00 09 00 00 00 00 00 00 7F

Any idea on how this can be fixed ?

I have access to a various embedded programming devices in case it needs to be reprogrammed.

Your device is just in bootloader mode. You can reprogram by following the instructions here: ChipSHOUTER/documentation/Firmware Update.md at master · newaetech/ChipSHOUTER · GitHub

Thank you that solved the issue.

Any idea why this happened ?

I looked at this a while back, and I think it had something to do with the trigger button pin (which can be used to enter the bootloader) occasionally not being in the right state. Fixing this would require a new bootloader, which can’t be reprogrammed by an end user.

1 Like

Thank you for the explanation.