STM32F4 discovery loading issue.

Karel Gardas karel.gardas at
Wed Aug 28 21:46:32 UTC 2013

Hi Jiri,

thanks for confirmation. The difference between our setups looks to be in:
- you are writing raw binary and you decide to do on 0x8000000 directly 
while I've been trying with RTEMS generated hello.exe, i.e. ELF file.

Could you be so kind and let me know where exactly hello.bin prints its 
messages? To USART 3 as I assume? If so then am I right that for 
debugging/printing you use custom level shifter (to rs-232) and connects 
directly to appropriate pins on board?


On 08/28/13 11:40 PM, Jiri Freyvald wrote:
> Hi Karel,
> it actually works very well (I mean for STM32F4 discovery board) and out
> of the box.
> I myself use stlink (on linux) for uploading RTEMS binaries with the
> same parameters for stlink as for any STM32F4 binary (without RTEMS)
> for example:
> flash write o-optimize/hello.bin 0x8000000
> regards,
> Jiri
> On 28/08/13 18:53, Karel Gardas wrote:
>> Hello,
>> I'm trying to use STM32F4 discovery board to run some RTEMS programs,
>> actually starting with hello.exe but I've found that neither using
>> OpenOCD 0.7.0 on Windows nor using stlink (HEAD) I've been able to
>> load the program on the board. Stlink was a little bit clearer here
>> and I've found that if I change flash address from 0x0 to 0x08000000
>> my program loads successfully.
>> My question then is: if STM32F4 BSP is tested, then how to switch my
>> STM32F4 discovery board to be able to use RTEMS's tests/samples on it
>> as it was done on reference/developer platform?
>> Thanks!
>> Karel
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at
> _______________________________________________
> rtems-users mailing list
> rtems-users at

More information about the users mailing list