I am trying to execute this very basic code in the Lua VM: for i=1,1000 do print(i) end What happens is that after “i” reaches 380+, the modem resets, without any warning/error. When checking the backtrace, the following errors show up: Current OAT task index 0 ARM Data Abort caught at 0028723A…

Big Loops Are Bad! They trip the watchdog. FAQ: wavecom.com/modules/movie/sc … iki#p16098

don’t link to the old forum! :stuck_out_tongue: [image] FAQ forum/wiki? Forum and Source related topics Hiya, Does anyboy else think that it would be a good idea to have a FAQ area on either the Forum or Developer’s website? I’ve noticed that the same questions are ask…

:blush: Oops - good point. The trouble is, all the references in existing posts are to the old forum! What I did was a search for “FAQ Wiki”, and then just followed the link in the first post it found - which, of course, ended up at the old forum! See: viewtopic.php?f=7&t=4579&p=18492#p18492

I am not sure if the infinite loop problem applies to the Lua VM. If it does, than I strongly believe it should be considered a bug. I tried adding a wait() function call to the loop to let the other threads do their job, but the same happens: for i=1,1000 do print(i);wait(5);end After “i” reache…

I’m not sure either, but I suspect it does Why? The Lua VM, as I understand it, isjust an Open-AT app - so the watchdog limitation would be expected to apply?

I do not have any LuaW HW available here, but I doubt that OpenAT watchdog trigger reset is the reason for this behaviour. LuaW makes use of adl_wdPut2Sleep func for watchdog triggering prevention for at least 1 minute (see src_orig\lvm.c for details). To see if memory is the problem, run somethin…

Hmm… sounds like a risky idea! In any embedded system, the watchdog is there for a purpose - so disabling it without specific, careful thought is not a good idea! Now wandering off-topic… Newcomers to the embedded world often consider watchdog resets to be a fault in themselves - but this is to …

Just to note that I do realise that it is not proven that watchdog resets are involved here…

Indeed, I think this was one of the problems - after setting LUAW_MEM_ALARM_THRESHOLD to 140 KB “mem().USED_MEM_NOW” never went above that value. However there was another detail that I missed before and it seems it’s responsible for the reset: I have an adl_tmr_t timer callback C function used f…

Just to note that I do realise that it is not proven that watchdog resets are involved here… I don’t think the watchdog has anything to do with the crash because the VM seems to reset the watchdog periodically as long as it’s executing bytecode. Also, I would’ve considered this to be a bug since…

VM crashes OpenAT

Legacy Open AT

Madouc February 12, 2010, 8:53am 3

don’t link to the old forum!

is the correct link

Topic		Replies	Views
LuaVM related watchdog reset Open AT	5	3555	June 9, 2010
Lua-interactive failure Open AT	7	4104	June 30, 2009
Latest lua sources Open AT	16	6125	January 28, 2010
FAQ: frequent error "Failed to allocate [...] EMERGENCY GC" Open AT	0	1631	July 5, 2009
Wavecom now offers scripting with Open AT Lua Open AT	11	3697	April 3, 2008

VM crashes OpenAT

Related topics