October 06, 2024, 10:17:01 AM

H104 examples

Started by Detlef_A, November 23, 2014, 02:30:39 AM

Previous topic - Next topic

Detlef_A

Hi,

I followed the tutorial on
http://www.angstromsandalgorithms.com/
to setup Eclipse with gdb for running/debugging my Olimex board.

The tutorial refers to the Olimex STM32-E407_blink_FLASH example on the STM32-E407 board.
I want to run the program on a STM32-H405 board and an ARM-USB-OCD-H debugger.

The project compiles fine and the JTAG seems to communicate with the board. Though, I cannot get it running. I get the attached error messages.
I assume that it could have something to do with the board configuration files.

What can I do to get the E407 example running on a H104 board?
or
Is there a spcific examle for the H104 board

Thank you
Detlef


Open On-Chip Debugger 0.7.0 (2013-05-05-10:41)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m3 reset_config sysresetreq
Info : max TCK change to: 30000 kHz
Info : clock speed 1000 kHz
Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
Info : JTAG tap: stm32f4x.bs tap/device found: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0)
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3333
Info : device id = 0x10016413
Info : flash size = 1024kbytes
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Info : dropped 'gdb' connection
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Info : dropped 'gdb' connection
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Info : dropped 'gdb' connection
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Info : dropped 'gdb' connection
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Info : dropped 'gdb' connection

JohnS

#1
You are confusing: you say H405 but then H104.  I'm not sure which H104???

You might like to ask on an OpenOCD list - they will want -d 3 output.  They may well also want your input.

OpenOCD has cfg scripts for other STM32 boards so maybe you can see what they do and make small changes if needed.

John

leon_heller

There is no such thing as an H104!

Detlef_A

ehm, apologies for that, it was too late.

I'm fiddeling with the STM32-H405 board (that seems to be similar to the STM32-H103, I mixed up the numbering of the two).
I tried to fire up an example made for the STM32-E407 board, could not get it to work.

My questions:
Where are the board specifics I have to change to get the E407 example running on the H405?
or
Are there any examples for the H405 for gcc toolchain?

Sorry for my buggy initial post.
THX
Detlef






JohnS

I never studied the 407 but the places to be looking are probably the chip data sheets and board manuals etc.  I'm doubtful a 103 is a good place but go looking :)

What I would do is ignore the H or E, but as well as data sheets google for the actual chips or near ones.

All STM32 are very similar so this is not rocket science at all, just ordinary work.

John

veritek

I am working with an h405 board and jtag (ARM-USB-TINY-H) and CrossWorks.  Getting a "cannot find debug register"

Do you have any ideas what I may not have set up or loaded?