STM32F4 failure on semaphore release in termios.
Karel Gardas
karel.gardas at centrum.cz
Thu Aug 29 21:36:27 UTC 2013
On 08/29/13 09:24 AM, Sebastian Huber wrote:
> On 2013-08-28 23:30, Karel Gardas wrote:
>>
>> I'm trying to get my STM32F4 discovery board working with RTEMS. So
>> far I've
>> just modified linkcmd of this BSP to get ROM start address to 0x08000000:
>>
>> MEMORY {
>> RAM_INT : ORIGIN = 0x20000000, LENGTH = 128k
>> ROM_INT : ORIGIN = 0x08000000, LENGTH = 1M
>> }
>
> I think this will not work. You have to map the code to address 0x0. For
> the load command in your debugger use an offset of 0x08000000 as
> described by Jiri.
OK, I did reverted this change and now I'm again on 0x0 address:
$ arm-rtemseabi-objdump -h hello.exe
hello.exe: file format elf32-littlearm
Sections:
Idx Name Size VMA LMA File off Algn
0 .start 000002e8 00000000 00000000 000000c0 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .text 00018cb8 00000300 00000300 000003c0 2**5
[....]
I've build .bin from this by:
arm-rtemseabi-objcopy -R -S -O binary hello.exe hello.bin
and loaded this using OpenOCD with using:
tar ext thinkpad:3333
monitor reset halt
monitor flash write_image c:/tmp/hello.bin 0x8000000
actually, OpenOCD is running on Windows OS and I'm copying hello.bin to
c:/tmp/ using ssh for this to work as gdb does not support remote file
transfer from my Solaris machine where I'm paying with RTEMS -- at least
I've not found such support yet.
and when I run it I've hit exactly the same issue like reported in
original email. I'm using the same tool-chain as for my LM4F120 hacking
(GCC 4.7.2, binutils 2.23.1) and the RTEMS HEAD git tree, the last
patches (public) which I see there are:
commit ef3c17fb892a2e3c637eaa737c57dc9026cf28b4
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Thu Aug 8 14:22:07 2013 +0200
sptests/spintrcritical19: Typos
commit 6b0cd960e520f0558a142669b53606b20751a9c9
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Thu Aug 8 13:58:10 2013 +0200
sptests/spintrcritical19: PR2136: New test
I've not updated for sometime to keep the tree for LM4F120 contributing...
May this be the issue?
Thanks a lot!
Karel
More information about the devel
mailing list