RTEMS Fatal Error on IMX7D SABRE Board.

jameszxj jameszxj at gmail.com
Wed Jan 6 13:43:02 UTC 2021


Hi Christian


> Hello,
> 
> On 06/01/2021 13:25, jameszxj wrote:
> > 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.
> 
> Sounds like some low power mode. I would suggest to check the settings 
> in the CCM. Check whether the system enters low power mode on a WFI 
> instruction and disable that feature. Especially interesting would be 
> the CCM_CLPCR.MASK_CORE0_WFI and similar bits. If these seem to be 
> correct, I would check the CCGR* registers.
>


Thanks for the details. I forget to remove some power test code, it makes the system enter low power mode. ;)
Now rtems is running successfully.


Thanks again.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20210106/0e396a7f/attachment.html>


More information about the users mailing list