raspberry BSP: Maybe there is a bug in the linker file?

[Christian Mauderer]

On 20/12/2019 09:22, Christian Mauderer wrote:
> On 20/12/2019 07:33, Sebastian Huber wrote:
>> On 19/12/2019 15:28, Niteesh wrote:
>>> As far as I know, 0x8000 is a fixed address where the bootloader jumps
>>> to after loading the application assuming the CPU is in 32bit mode.
>>> For 64bit mode, it jumps to 0x80000.
>>
>> Would you mind testing this patch:
>>
>> https://lists.rtems.org/pipermail/devel/2019-December/056551.html
>>
> 
> On the Pi 1 now the binary has three time the size (with a lot of 0x00
> in it) and at least RTEMS starts. But it runs into an exception quite
> fast. I'll investigate that a bit.
> 
> @Niteesh: For the Pi 3 I would expect that it still doesn't print
> anything on the console due to the different UART pins.
> 
> The output on the Pi 1 is:
> 
> executing�
> *** FATAL ***
> fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
> 
> R0   = 0xfc037f80 R8  = 0x00000000
> R1   = 0xfc345980 R9  = 0x00000010
> R2   = 0x00000001 R10 = 0xfc037f8a
> R3   = 0x03fc8080 R11 = 0x0030da00
> R4   = 0xfc037f80 R12 = 0xfc345988
> R5   = 0x00000008 SP  = 0x00300ba8
> R6   = 0x0030d9fe LR  = 0x00205a78
> R7   = 0x00305218 PC  = 0x00205ac8
> CPSR = 0x600001d3 VEC = 0x00000004
> RTEMS version: 5.0.0.254f38583fe68c3e17dfe274a2deeb00a5a538d6
> RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (6c65fc237b9e modified),
> Newlib d14714c69)

The exception seems to be caused by some of the changes in bspstart.c
and bspgetworkarea.c in patch a4d7e4cee77d16b0e34ef543f0804e7eb2954137.
So the fix for the linker command file is fine.