mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* Are there any operations may influence WFI instruction?
@ 2021-05-01 13:20 jameszxj
  2021-05-03  9:48 ` Ahmad Fatoum
  0 siblings, 1 reply; 2+ messages in thread
From: jameszxj @ 2021-05-01 13:20 UTC (permalink / raw)
  To: barebox

Hi,
  I run rtems6 on my imx6ull board, just initialize a GPT timer to flash a LED.  I load rtems with barebox, after output some initialized messages, system enters shell and stalls, interrupt(GPT timer, arch7 timer for tick) do not happen again. Shell (connect to UART1,interrupt mode) still works, when I type something, the LED flashes. It seems that system only responses to UART1 interrupt, and triggers the other interrupts respones. I remove wfi instruction from idle task, system runs ok.
And when I replace barebox with uboot, everything seems OK. I think maybe some initialized differences between barebox and uboot, but I haven't find any clues that  may influence WFI.


Any suggestion?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Are there any operations may influence WFI instruction?
  2021-05-01 13:20 Are there any operations may influence WFI instruction? jameszxj
@ 2021-05-03  9:48 ` Ahmad Fatoum
  0 siblings, 0 replies; 2+ messages in thread
From: Ahmad Fatoum @ 2021-05-03  9:48 UTC (permalink / raw)
  To: jameszxj, barebox

Hi,

On 01.05.21 15:20, jameszxj wrote:
> Hi,
>   I run rtems6 on my imx6ull board, just initialize a GPT timer to flash a LED.

You can describe heartbeat LED in the barebox device tree just as you'd do in
Linux and barebox will take care to blink it during bootstrap. No need to involve
interrupts.

> I load rtems with barebox, after output some initialized messages, system enters shell and stalls, interrupt(GPT timer, arch7 timer for tick) do not happen again. Shell (connect to UART1,interrupt mode) still works, when I type something, the LED flashes. It seems that system only responses to UART1 interrupt, and triggers the other interrupts respones. I remove wfi instruction from idle task, system runs ok.
> And when I replace barebox with uboot, everything seems OK. I think maybe some initialized differences between barebox and uboot, but I haven't find any clues that  may influence WFI.

barebox on i.MX uses one of the available GPT timers as clocksource.

HTH,
Ahmad

> 
> 
> Any suggestion?
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-05-03  9:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-01 13:20 Are there any operations may influence WFI instruction? jameszxj
2021-05-03  9:48 ` Ahmad Fatoum

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox