vedderb / nrf52_vesc Goto Github PK

Hi,

i get this:

/usr/bin/arm-none-eabi-gcc' -O3 -g3 -mthumb -mabi=aapcs -L/home/busta/src/nRF5_SDK_15.3.0_59ac345/modules/nrfx/mdk -Tld_sd_52840.ld -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -Wl,--gc-sections --specs=nano.specs -u _printf_float @_build/nrf52840_xxaa.in -Wl,-Map=_build/nrf52840_xxaa.map -o _build/nrf52840_xxaa.out
/usr/lib/gcc/arm-none-eabi/12.2.1/../../../arm-none-eabi/bin/ld: _build/nrf52840_xxaa/storage.c.o:/home/busta/src/nrf52_vesc/storage.h:26: multiple definition of `m_config'; _build/nrf52840_xxaa/main.c.o:/home/busta/src/nrf52_vesc/storage.h:26: first defined here
collect2: error: ld returned 1 exit status
make: *** [/home/busta/src/nRF5_SDK_15.3.0_59ac345/components/toolchain/gcc/Makefile.common:294: _build/nrf52840_xxaa.out] Error 1

Compiling on Kali Linux Rolling

Any ideas? Thanks!

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?

EDIT: Apart from that, now comparing the chip numbers more carefully, looks like I messed up. I bought this module: https://www.ebay.de/itm/122543237978 but it's NRF51xxx and not 52xxx, I guess that was a mistake too?
EDIT2: Ah, now found https://github.com/vedderb/nrf51_vesc, I will try that now.

thanks,
Ethan