vedderb / nrf51_vesc Goto Github PK

Can you elaborate on this command? What directory do you run this under? How does openocd know what hex file to use?

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

The Vesc Tool application connects to NRF51 but receives the message that FW version cannot be processed and disconnects.

Hi Benjamin,

can you please add the other hex files too?

Hello, Benjamin. I saw you say "This is code for a NRF51822 for communicating between the VESC and VESC Tool (linux and mobile) over BLE." Can this be used on Windows 10? My operating system is Windows 8. If Bluetooth can be connected on Windows 10, I will upgrade to Windows 10. thank you.

Hi,
I building my first eskate board, and want to add mobile phone connectivity. I bough Vesc Tool for android, and flashed chip NRF nRF51822 board without any problem, then connected every thing to vesc board, but the BLE device seems to be not visible via my mobile phone (huawey P20).
I was trying the same with chip HC06 BT module, just to make sure if serial connection working fine, and i can connect from windows app via BT to VESC, so it means, that serial connection works fine.
The log from NRF flashing looks like following

C:\Users\kku\Downloads>openocd -f openocd.cfg -c "init" -c "halt" -c "nrf51 mass_erase" -c "program nrf51_vesc_ble_wt.hex verify reset exit"
Open On-Chip Debugger 0.10.0 (2021-03-01) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 1000 kHz
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.217895
Info : nrf51.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : starting gdb server for nrf51.cpu on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0xc1000003 pc: 0xfffffffe msp: 0xffffffd8
Info : nRF51822-QFAA(build code: H2) 256kB Flash, 16kB RAM
Info : Mass erase completed.
Info : A reset or power cycle is required if the flash was protected before.
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
Info : Flash write discontinued at 0x000007c0, next section at 0x00001000
Warn : Adding extra erase range, 0x000007c0 .. 0x000007ff
Info : Padding image section 1 at 0x0001afe0 with 32 bytes
Warn : Adding extra erase range, 0x0001f2d8 .. 0x0001f3ff
** Programming Finished **
** Verify Started **
** Verified OK **
** Resetting Target **
shutdown command invoked

And the board is connected as shown at attached pic

What do i wrong?
Thank you in advance.
Kris

Hi Benjamin,
can you please upload the SDK?

Best regards
Sasan