Skip to main content
Remi Demers
Associate II
Apr 1, 2025 4:00 PM UTC
Solved

BLUENRG-LPS flashing problem

Hi,

I am starting to work with STEVAL-IDB012V1A. I use Wise-studio version: 1.3.1_R on Linux. I can compile successfully the example "Profiles_Peripheral_with_Library". In the launch configuration I selected CMSIS-DAP. I do hold PUSH1 button while pressing reset before launching the programming. When I click the green arrow to program I get this in the console:

Open On-Chip Debugger 0.12.0-rc2+dev-00962-g12ce17094-dirty (2022-11-07-16:26)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 0254
Info : CMSIS-DAP: Serial# = 0720000197969908a5a5a5a505d5ff383650503043146928
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 1200 kHz
Info : SWD DPIDR 0x0bc11477
Info : [bluenrg-lps.cpu] Cortex-M0+ r0p1 processor detected
Info : [bluenrg-lps.cpu] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for bluenrg-lps.cpu on 3333
Info : Listening on port 3333 for gdb connections
[bluenrg-lps.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x100017e8 msp: 0x20005ff8
** Programming Started **
Info : Padding image section 0 at 0x1005eb9c with 4 bytes (bank write end alignment)
Warn : Adding extra erase range, 0x1005eba0 .. 0x1005efff
Error: CMSIS-DAP transfer count mismatch: expected 12, got 4
Info : SWD DPIDR 0x0bc11477
Error: Failed to write memory at 0x20004214
Error: error writing to flash at address 0x10040000 at offset 0x00000000
** Programming Failed **
shutdown command invoked

Warn : Flash driver of bluenrg-lps.flash does not support free_driver_priv()

 

The addresses where the memory write failed are not the same every time. I got it programmed successfully a few times before but now it always fail. Any clue to get out of this?

Thanks,

Rémi

This topic has been closed for replies.
Remi Demers
Remi DemersBest answer
Associate II
Apr 1, 2025 5:26 PM UTC

I found the problem. My USB hub had not enough power. Connected directly to the computer it works.

1 reply

Remi Demers
Remi DemersAuthorBest answer
Associate II
Apr 1, 2025 5:26 PM UTC

I found the problem. My USB hub had not enough power. Connected directly to the computer it works.