search

vedderb / nrf51_vesc

BLE-UART bridge for the VESC with packet handling and VESC Tool compatibility
57 stars 35 forks source link

hex filename changed/wrong? #8

Open arnolde opened 1 year ago

arnolde commented 1 year ago

Hello,

I am using Ubuntu 18.04, installed openocd 0.10.0 via apt-get, cloned this repo, bought a STlink 2.0 adapter and nrf51822 board similar to the one in the README photo, but when running the script I get:

ea@Q520:~/vesc/nrf51_vesc$ ./upload_merged
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.284379
Info : nrf51.cpu: hardware has 4 breakpoints, 2 watchpoints
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0xc1000003 pc: 0xfffffffe msp: 0xffffffd8
Warn : Unknown device (HWID 0x000000d1)
target halted due to debug-request, current mode: Thread 
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
auto erase enabled
Error: couldn't open hex/nrf51_vesc_ble.hex
** Programming Failed **
shutdown command invoked

In the hex/ directory, there is (only) a file named nrf51_vesc_ble_wt.hex Is it safe to rename it to match the name expected by the upload script?

thanks, Ethan

arnolde commented 1 year ago

I used the nrf51_vesc_ble.hex from a previous commit and that is now working with the Android app. Thanks for the great work! I would still appreciate a quick comment if I could have used the _wt version too, in case I reflash my module someday. I used this one https://www.ebay.de/itm/122543237978 and it worked straight away, no problem.