Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Timeout waiting for ACK/NACK after 'Send data (0x24)' #123

Open
SuperPauly opened this issue May 2, 2022 · 3 comments
Open

ERROR: Timeout waiting for ACK/NACK after 'Send data (0x24)' #123

SuperPauly opened this issue May 2, 2022 · 3 comments

Comments

@SuperPauly
Copy link

SuperPauly commented May 2, 2022

I'm running
python3 cc2538-bsl.py -p /dev/ttyUSB0 -e -v -w --bootloader-sonoff-usb CC1352P2_CC2652P_launchpad_coordinator_20220219.hex -V

And I'm getting this output:

sonoff
Opening port /dev/ttyUSB0, baud 500000
Reading data from CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:24:C9:20:33
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
ERROR: Timeout waiting for ACK/NACK after 'Send data (0x24)'

I have tried different baud rates and I always get the same error. How can I fix this?

@SuperPauly
Copy link
Author

UPDATE:
I changed USB ports and now it works but I'm getting a different error:

sonoff
Opening port /dev/ttyUSB0, baud 500000
Reading data from CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:24:C9:20:33
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
ERROR: No response from target on status request. (Did you disable the bootloader?)

@JelmerT
Copy link
Owner

JelmerT commented May 2, 2022

seems like in both cases your chip isnt answering after the write cycle. Are you sure you're using a correct firmware for your chip, and you're not disabling the bootloader in the chip?

@ledhed2222
Copy link

@SuperPauly I was having the same issue. Decided to stop a bunch of user services. Homebridge, running on the same pi, seemed to be the culprit. Perhaps it was trying to access the same serial port for some reason? no idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants