MVME2500 (qoriq_e500) no longer boots with RTEMS6

Gedare Bloom gedare at rtems.org
Fri Feb 19 17:40:22 UTC 2021


Advise how you built. We are starting to see some bitrot breakage in
configuration. The cutover to waf will come soon, and I don't expect
rtems6 release to support autoconf build of rtems itself. I suggest
you change over to waf build of rtems kernel if you haven't yet.

On Fri, Feb 19, 2021 at 9:30 AM Heinz Junkes <junkes at fhi-berlin.mpg.de> wrote:
>
> When I use the kernel from RTEMS6 my MVME2500 (qoriq_e500)
> does not boot anymore and hangs:
>
> VME2500=> run rtems_myTests
> reading mvme2500.dtb
> 12363 bytes read in 13 ms (928.7 KiB/s)
> Speed: 1000, full duplex
> Using eTSEC1 device
> TFTP from server 141.14.128.9; our IP address is 141.14.128.89
> Filename 'ticker.img'.
> Load address: 0x10000000
> Loading: #####
>         6.4 MiB/s
> done
> Bytes transferred = 60182 (eb16 hex)
> WARNING: adjusting available memory to 30000000
> ## Booting kernel from Legacy Image at 10000000 ...
>   Image Name:   RTEMS
>   Created:      2021-02-18  20:18:21 UTC
>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>   Data Size:    60118 Bytes = 58.7 KiB
>   Load Address: 00004000
>   Entry Point:  00004000
>   Verifying Checksum ... OK
> ## Flattened Device Tree blob at 20000000
>   Booting using the fdt blob at 0x20000000
>   Uncompressing Kernel Image ... OK
>   Loading Device Tree to 03ff9000, end 03fff04a ... OK
>>
> no more output
>
> Heinz
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users


More information about the users mailing list