RTEMS Fatal Error on IMX7D SABRE Board.
jameszxj at gmail.com
Wed Jan 6 07:13:15 UTC 2021
I use IMX7 bsp on my imx6ull board. I have encountered maybe the same problem. Please check your device-tree, BSP needs "clock-frequency" at node "timer".
But I encountered another problems, the ARMv7-AR Generic Timer can not generate interrupt.
imx7d has the same core with imx6ull，if your board run RTEMS successfully, please let me know, thanks.
------------------ Original ------------------
From: "JunBeom Kim (EmbedCoreTech)" <jbkim at e-coretech.kr>;
Date: Wed, Jan 6, 2021 01:05 PM
To: "users"<users at rtems.org>;
Subject: RTEMS Fatal Error on IMX7D SABRE Board.
After I purchased i.MX7D SABRE board, I am trying to test RTEMS kernel using
lastest RTEMS kernel and source builder for RTEMS 6.0
As I knew before, RTEMS BSP for i.MX7D was not tested for i.MX7D SABRE
When I tested this, my testing result is in below;
<REMARK> rtems.img is made by calling mkimage.
At this time, I am trying to debug RTEMS BSP using GDB with J-Link probe.
There is problem for executing start.S assembly code as source code level.
Please advise me.
U-Boot 2020.10 (Jan 05 2021 - 09:44:38 +0900)
CPU: Freescale i.MX7D rev1.3 1000 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 38C
Reset cause: POR
Model: Freescale i.MX7 SabreSD Board
Board: i.MX7D SABRESD in non-secure mode
DRAM: 1 GiB
PMIC: PFUZE3000 DEV_ID=0x30 REV_ID=0x11
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default
Hit any key to stop autoboot: 0
=> fatload mmc 0 0x80800000 rtems.img
36463 bytes read in 23 ms (1.5 MiB/s)
=> fatload mmc 0 0x83000000 imx7d-sdb.dtb
33369 bytes read in 22 ms (1.4 MiB/s)
=> bootm 0x80800000 - 0x83000000
## Booting kernel from Legacy Image at 80800000 ...
Image Name: RTEMS
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 36399 Bytes = 35.5 KiB
Load Address: 80200000
Entry Point: 80200000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Uncompressing Kernel Image
Using Device Tree in place at 83000000, end 8300b258
Starting kernel ...
*** FATAL ***
fatal source: 6 (RTEMS_FATAL_SOURCE_BSP)
fatal code: 3072 (0x00000c00)
RTEMS version: 6.0.0
RTEMS tools: 10.2.1 20201222 (RTEMS 6, RSB
d3dc0bc3861362978cdf65725e4ba2b64e283d32, Newlib 415fdd4)
Executing thread is NULL
users mailing list
users at rtems.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users