![]() Now let's see if I can get a blink example to work. Verified 980 bytes in 0.030723s (31.150 KiB/s)Īll this thanks to advice from great thanks! Wrote 1024 bytes from file /home/sheep/dev/3rdparty/stm32f0-discovery-basic-template/main.bin in 0.104813s (9.541 KiB/s) Target halted due to breakpoint, current mode: Thread XPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc Target halted due to debug-request, current mode: Thread After running that, and resetting the chip, I finally got: openocd -f extra/fff.cfg -f extra/stm32f0-openocd.cfg -c "stm_flash `pwd`/main.bin" -c shutdown No problem, we can unlock it with "stm32x unlock 0". XPSR: 0xc1000003 pc: 0xfffffffe msp: 0xfffffffcĮrror: failed erasing sectors 0 to 0OK, so apparently the chip is write-protected. Target halted due to debug-request, current mode: Handler HardFault Info : stm32f0x.cpu: hardware has 4 breakpoints, 2 watchpoints Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748 Info : Unable to match requested speed 1000 kHz, using 950 kHz Srst_only separate srst_nogate srst_open_drain connect_deassert_srst ![]() The results might differ compared to plain JTAG/SWD Info : The selected transport took over low-level target control. I got a new error with this: openocd -f extra/fff.cfg -f extra/stm32f0-openocd.cfg -c "stm_flash `pwd`/main.bin" -c shutdown Fully protected Dual H-Bridge: L6205/6225. First of all, the error I'm getting was described in an issue and seems like adding "reset_config none separate" fixes that. Aircon compressor and fans, industrial control, washing- machine. In procedure 'program_error' called at file "embedded:startup.On a quest to configure OpenOCD properly. In procedure 'program' called at file "openocd.cfg", line 11Įrror executing event reset-init on target stm32f4x.cpu:Įmbedded:startup.tcl:449: Error: ** Programming Failed ** Warn : STM32 flash size failed, probe inaccurate - assuming 1024k flash XPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffcĮrror: Failed to read memory at 0x1fff7a24 ![]() In procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 214 After that, you need to physically remove power from the device in order for. Info : Listening on port 3333 for gdb connectionsĮrror: Translation from khz to jtag_speed not implementedĮrror executing event reset-start on target stm32f4x.cpu: Most likely your STM32 is locked (readout protection). Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints Info : This adapter doesn't support configurable speed Anyone got any ideas on how I can fix? Also included is the openocd.cfg file. However, as you can see in the image, unlocking of STM32 devices is supported natively (upper marking in the screenshot) If you type in 'con' multiple times, does it unlock the device multiple times We also provide a tool to reset the option bytes of STM32 devices to factory default. I have managed to get it to connect to the vesc (can be seen in the openocd output.txt) but it won't program due to the device being protected. the unlock command only supports the devices listed. From my research I found that this could perhaps be a firmware or bootloader issue so I have been trying to redo it using a raspberry pi running openocd and the GPIO pins connected to the vesc. It now only displays a blue light when on (no green like my other working vesc). ![]() I was riding my skateboard the otherday when it suddenly lost power and wouldnt reboot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |