How to program an Olimex STM32-E407

[mk_stm]

I am having a hard time figuring out working with the STM32-E407 which is built on STM32F407ZGT6 MCU. I also brought an ARM-USB-TINY-H as it was recommended in its documentation. How and where do I start ? Say I want to interface this board with a radar sensor.

[mƎALLEm]

Hello @mk_stm and welcome to the community,

That board is not an ST board.

Did you ask that question in Olimex community: https://www.olimex.com/forum/index.php  ?

[Andrew Neil]

Welcome to the forum.

Please see  How to write your question to maximize your chances to find a solution for best results.

As neither the STM32-E407 board nor the ARM-USB-TINY-H is an ST product, you should really be going to Olimex for support with their products:

support@olimex.com 

https://www.olimex.com/forum/

You haven't said what tools you're using to program this board.

The ST tools are STM32CubeIDE and STM32CubeProgrammer - I think neither of them supports the ARM-USB-TINY-H.

I would suggest that you get an ST-Link; they are widely supported (unlike the ARM-USB-TINY-H) - and cheaper!

Just be sure to get a genuine one.

The board's debugger pinout is described in the User Manual:

https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407.pdf#page=14

It matches the pinout of the ARM-USB-TINY-H - so you can just plug it in:

https://www.olimex.com/Products/ARM/JTAG/_resources/ARM-USB-TINY_and_TINY_H_manual.pdf#page=10

For a beginner getting started, I would strongly suggest that a Nucleo board would be a far more appropriate starting point; eg, NUCLEO-F411RE as this includes the ST-Link - so no need to mess about with connecting and configuring it.

And it's cheaper.

And it gives you a well-known, widely-used platform with plenty of ready-to-go examples, tutorials, etc.

[mk_stm]

Does the nucleo board you suggested support MicroROS ? I want to implement
MicroROS with Zephyr RTOS.

[mƎALLEm]

---

@mk_stm wrote:
Does the nucleo board you suggested support MicroROS ? I want to implement
MicroROS with Zephyr RTOS.

---

It was listed in this link (Zephyr link):

https://docs.zephyrproject.org/latest/boards/st/nucleo_f411re/doc/index.html

So it supports Zephyr RTOS

[Andrew Neil · Accepted solution]

---

@mk_stm wrote:
Does the nucleo board you suggested support MicroROS ?

---

No more nor less that the Olimex board would.

There are Nucleo boards for the whole range of STM32s - so pick one which has a suitable STM32 on it:

https://www.st.com/en/evaluation-tools/stm32-nucleo-boards/products.html

As @mƎALLEm suggested, you can check Zephyr board support here:

https://docs.zephyrproject.org/latest/boards/st/index.html 

---

@mk_stm wrote:
I want to implement MicroROS with Zephyr RTOS.

---

That sounds a bit ambitious given your earlier questions?

But we digress from the original question.

If your original question has been answered, please Mark The Solution and start a new thread for a new question.

I saw this recently on Linkedin - A set of utilities for integrating micro-ROS in a STM32CubeMX project:

https://github.com/micro-ROS/micro_ros_stm32cubemx_utils 

PS:

MicroROS lists a number of supported Nucleo boards here:

https://micro.ros.org/docs/overview/hardware/

But this (and Zephyr support) is not so much about the board as whether the software is available off-the-shelf and ready-to-go.

You can always do the porting yourself ...

[Ozone]

> I am having a hard time figuring out working with the STM32-E407 which is built on STM32F407ZGT6 MCU.

The board is fine. The debug connector is the 20-pin boxed header standardized by ARM. The standalone ST-Link and the Segger JLink pods come with such a cable, if I remember correctly.

> I also brought an ARM-USB-TINY-H as it was recommended in its documentation.

This might be a problem, because you need a toolchain that supports this debug adapter for flashing and debugging.
Connect it to the host, and exeute the 'lsusb' command (or whatever the Windows equivalent is ...). Probably a CMSIS-DAP.
Years ago I had used Crossworks for Arm, which supported this adapter directly.
CubeIDE might as well, you will need to check.
OpenOCD most probably, but I have no experience with it under Windows.
Although not so long ago, I flashed an Atmel M7 board with their onboard CMSIS-DAP version, which worked fine. 

[mk_stm]

I know it's a bit ambitious :). I just thought of the bigger picture and now am trying to figure out how to reach it.

[Ozone]

> I know it's a bit ambitious :).

Having some ambitions is an initial step. 
For the rest, you might need some experience - or you will gain it on the way ...

Before choosing an MCU and a debug adapter, check the toolchains that support this combination first.
Which is for instance a critical point for me. Trying stuff with MCUs from different vendors, I toolchains that support only one MCU vendor or debug adapter model. Vendor-locked bloatware with 1...3 GB per MCU family is out of the question for me.

According the Olimex site, OpenOCD is supported under Windows as well.
However, mentioning CooCox as IDE confuses me. This IDE is dead for almost a decade now ...

[mƎALLEm]

Hello @mk_stm ,

I think the original question has been answered. If you have another question or require more details or more guidance please open a new thread for that specific question.

Thank you.