Thread: DIY - KeK
View Single Post
Old 08-13-2012, 10:03 PM   #261
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
This article takes a slightly different approach and is fairly recent (2010):
http://balau82.wordpress.com/2010/04...t-on-qemu-arm/

It might be worth checking if the mentioned patches are already in our qemu sources before starting to follow that article. Mainstream may have picked them up but implemented the features a bit differently.

Edit:
One point you will not find in the general articles . . .
The i.MX Freescale SoC has a hardware watchdog which can not be disabled and if not serviced, will reset the core.

So any program running in control of the processor (iBootloader, U-boot, kernel in that order) has to provide code to service the watchdog often enough to keep it from tripping.

Things may not be the same under emulation - I don't know if qemu emulates the non-maskable hardware watchdog.

Last edited by knc1; 08-13-2012 at 10:34 PM.
knc1 is offline   Reply With Quote