Hi,

> Hello,
> 
> On 06/01/2021 10:04, jameszxj wrote:
> > Hi,
> > 
> > I can't find "timer" node in your devicetree. 
> > Function arm_generic_timer_get_config() in file bspstart.c will 
find 
> > node "/timer"
> > and get "clock-frequency" value for system tick.
> 
> note that at least the clock-frequency is added by U-Boot on the 
i.MX7 
> during boot and is not in the typical device tree sources.
> 
> On i.MX6UL/ULL there is still an ugly hack necessary:
> 
> 
https://github.com/grisp/rtems/commit/02270d5ec82684007ae9973070a6f29428be1543
> 
> It's on my TODO-list to avoid that patch, but I haven't done that yet.
> 


I add the timer_init in bsp, but the tick interrupt still seems pending.
When I type something in shell, ticks will come.


> > 
> > ------------------ Original ------------------
&gt; &gt; *From:* "JunBeom Kim (EmbedCoreTech)" <jb...@e-coretech.kr&gt;;
&gt; &gt; *Date:* Wed, Jan 6, 2021 04:46 PM
&gt; &gt; *To:* 
"'jameszxj'"<james...@gmail.com&gt;;"'users'"<users@rtems.org&gt;;
&gt; &gt; *Subject:* RE: RTEMS Fatal Error on IMX7D SABRE Board.
&gt; &gt;&nbsp;
&gt; &gt; Dear James,
&gt; &gt;&nbsp;
&gt; &gt; As I know before, because this BSP is tested on Phytec??s 
PhyBOARD-i.MX7&nbsp;
&gt; &gt; board, I am considering to purchase this board, too.
&gt;&nbsp;
&gt;&nbsp;
&gt; The last test on that board is some time back because I currently 
don't&nbsp;
&gt; have access to it (working from home). So also I would hope it, I&nbsp;
&gt; wouldn't guarantee that it runs out of the box.
&gt;&nbsp;


thanks.


&gt;&nbsp;
&gt; &gt;&nbsp;
&gt; &gt; Best Regards,
&gt; &gt;&nbsp;
&gt; &gt; JunBeom
&gt; &gt;&nbsp;
&gt; &gt; *From:*JunBeom Kim (EmbedCoreTech) <jb...@e-coretech.kr&gt;
&gt; &gt; *Sent:* Wednesday, January 6, 2021 5:39 PM
&gt; &gt; *To:* 'jameszxj' <james...@gmail.com&gt;; 'users' <users@rtems.org&gt;
&gt; &gt; *Subject:* RE: RTEMS Fatal Error on IMX7D SABRE Board.
&gt; &gt;&nbsp;
&gt; &gt; Dear James,
&gt; &gt;&nbsp;
&gt; &gt; I used two files(imx7d-sdb.dts and imx7d.dtsi) for making 
imx7d-sdb.dtb.
&gt; &gt;&nbsp;
&gt; &gt; There is clock-frequency configuration in imx7d.dtsi.
&gt; &gt;&nbsp;
&gt;&nbsp;
&gt;&nbsp;
&gt; Again: Normally U-Boot should add that clock-frequency.
&gt;&nbsp;
&gt;&nbsp;
&gt; &gt; Best Regards,
&gt; &gt;&nbsp;
&gt; &gt; JunBeom
&gt; &gt;&nbsp;
&gt; &gt; *From:*users <users-boun...@rtems.org 
<mailto:users-boun...@rtems.org&gt;&gt;&nbsp;
&gt; &gt; *On Behalf Of *jameszxj
&gt; &gt; *Sent:* Wednesday, January 6, 2021 4:13 PM
&gt; &gt; *To:* users <users@rtems.org <mailto:users@rtems.org&gt;&gt;
&gt; &gt; *Subject:* Re:RTEMS Fatal Error on IMX7D SABRE Board.
&gt; &gt;&nbsp;
&gt; &gt; Hi,
&gt; &gt; I use IMX7 bsp on my imx6ull board. I have encountered maybe the 
same&nbsp;
&gt; &gt; problem. Please check your device-tree, BSP needs "clock-frequency" 
at&nbsp;
&gt; &gt; node "timer".
&gt;&nbsp;
&gt; Do you use an i.MX6ULL with U-Boot or Barebox? They might have 
slightly&nbsp;
&gt; different behavior regarding the timer.
&gt;&nbsp;


I use barebox.


&gt; &gt;&nbsp;
&gt; &gt; But I encountered another problems, theARMv7-AR Generic Timercan 
not&nbsp;
&gt; &gt; generate interrupt.
&gt; &gt; imx7d has the same core with imx6ull??if your board run RTEMS&nbsp;
&gt; &gt; successfully, please let me know, thanks.
&gt;&nbsp;
&gt; As you might have seen above, I'm using the BSP on i.MX6ULL based&nbsp;
&gt; boards. The board uses Phytec Phycore i.MX6UL/ULL modules (different&nbsp;
&gt; variants in different projects). One of the projects is an open 
source&nbsp;
&gt; one and you can find all sources at:
&gt;&nbsp;
&gt;&nbsp; &nbsp; &nbsp; https://github.com/grisp/grisp2-rtems-toolchain
&gt;&nbsp;
&gt; &gt;&nbsp;
&gt; &gt; ------------------ Original ------------------
&gt; &gt;&nbsp;
&gt; &gt; *From:*"JunBeom Kim (EmbedCoreTech)" <jb...@e-coretech.kr&nbsp;
&gt; &gt; <mailto:jb...@e-coretech.kr&gt;&gt;;
&gt; &gt;&nbsp;
&gt; &gt; *Date:*Wed, Jan 6, 2021 01:05 PM
&gt; &gt;&nbsp;
&gt; &gt; *To:*"users"<users@rtems.org <mailto:users@rtems.org&gt;&gt;;
&gt; &gt;&nbsp;
&gt; &gt; *Subject:*RTEMS Fatal Error on IMX7D SABRE Board.
&gt; &gt;&nbsp;
&gt; &gt; Hello,
&gt; &gt;&nbsp;
&gt; &gt; After I purchased i.MX7D SABRE board, I am trying to test RTEMS 
kernel using
&gt; &gt; lastest RTEMS kernel and source builder for RTEMS 6.0
&gt; &gt;&nbsp;
&gt; &gt; As I knew before, RTEMS BSP for i.MX7D was not tested for i.MX7D SABRE
&gt; &gt; board.
&gt; &gt;&nbsp;
&gt; &gt; When I tested this, my testing result is in below;
&gt; &gt; <REMARK&gt; rtems.img is made by calling mkimage.
&gt; &gt;&nbsp;
&gt; &gt; At this time, I am trying to debug RTEMS BSP using GDB with J-Link 
probe.
&gt; &gt; There is problem for executing start.S assembly code as source code 
level.
&gt;&nbsp;
&gt; Can you try to set a breakpoint on at least _Terminate and do a&nbsp;
&gt; backtrace (bt in gdb)? I think the _ARM_Exception_default could be a&nbsp;
&gt; useful one too.
&gt;&nbsp;
&gt; Best regards
&gt;&nbsp;
&gt; Christian
&gt;&nbsp;
&gt;&nbsp;
&gt; &gt;&nbsp;
&gt; &gt; Please advise me.
&gt; &gt;&nbsp;
&gt; &gt; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
&gt; &gt; U-Boot 2020.10 (Jan 05 2021 - 09:44:38 +0900)
&gt; &gt;&nbsp;
&gt; &gt; CPU:Freescale i.MX7D rev1.3 1000 MHz (running at 792 MHz)
&gt; &gt; CPU:Commercial temperature grade (0C to 95C) at 38C
&gt; &gt; Reset cause: POR
&gt; &gt; Model: Freescale i.MX7 SabreSD Board
&gt; &gt; Board: i.MX7D SABRESD in non-secure mode
&gt; &gt; DRAM:1 GiB
&gt; &gt; PMIC: PFUZE3000 DEV_ID=0x30 REV_ID=0x11
&gt; &gt; MMC:FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
&gt; &gt; Loading Environment from MMC... *** Warning - bad CRC, using default
&gt; &gt; environment
&gt; &gt;&nbsp;
&gt; &gt; Video: 480x272x24
&gt; &gt; In:serial
&gt; &gt; Out:serial
&gt; &gt; Err:serial
&gt; &gt; Hit any key to stop autoboot:0
&gt; &gt;&nbsp;
&gt; &gt; =&gt; fatload mmc 0 0x80800000 rtems.img
&gt; &gt; 36463 bytes read in 23 ms (1.5 MiB/s)
&gt; &gt;&nbsp;
&gt; &gt; =&gt; fatload mmc 0 0x83000000 imx7d-sdb.dtb
&gt; &gt; 33369 bytes read in 22 ms (1.4 MiB/s)
&gt; &gt;&nbsp;
&gt; &gt; =&gt; bootm 0x80800000 - 0x83000000
&gt; &gt; ## Booting kernel from Legacy Image at 80800000 ...
&gt; &gt; Image Name:RTEMS
&gt; &gt; Image Type:ARM Linux Kernel Image (gzip compressed)
&gt; &gt; Data Size:36399 Bytes = 35.5 KiB
&gt; &gt; Load Address: 80200000
&gt; &gt; Entry Point:80200000
&gt; &gt; Verifying Checksum ... OK
&gt; &gt; ## Flattened Device Tree blob at 83000000
&gt; &gt; Booting using the fdt blob at 0x83000000
&gt; &gt; Uncompressing Kernel Image
&gt; &gt; Using Device Tree in place at 83000000, end 8300b258
&gt; &gt;&nbsp;
&gt; &gt; Starting kernel ...
&gt; &gt;&nbsp;
&gt; &gt;&nbsp;
&gt; &gt; *** FATAL ***
&gt; &gt; fatal source: 6 (RTEMS_FATAL_SOURCE_BSP)
&gt; &gt; fatal code: 3072 (0x00000c00)
&gt; &gt; RTEMS version: 6.0.0
&gt; &gt; RTEMS tools: 10.2.1 20201222 (RTEMS 6, RSB
&gt; &gt; d3dc0bc3861362978cdf65725e4ba2b64e283d32, Newlib 415fdd4)
&gt; &gt; Executing thread is NULL
&gt; &gt; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
&gt; &gt;&nbsp;
&gt; &gt; Best Regards,
&gt; &gt; JunBeom Kim
&gt; &gt;&nbsp;
&gt; &gt; _______________________________________________
&gt; &gt; users mailing list
&gt; &gt; users@rtems.org <mailto:users@rtems.org&gt;
&gt; &gt; http://lists.rtems.org/mailman/listinfo/users&nbsp;
&gt; &gt; <http://lists.rtems.org/mailman/listinfo/users&gt;
&gt; &gt;&nbsp;
&gt; &gt;&nbsp;
&gt; &gt; _______________________________________________
&gt; &gt; users mailing list
&gt; &gt; users@rtems.org
&gt; &gt; http://lists.rtems.org/mailman/listinfo/users
&gt; &gt;&nbsp;
_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Reply via email to