Maybe watchdog erroring out? #10351
Unanswered
8888clockradio
asked this question in
m.iMX RT / Teensy 4.x
Replies: 4 comments 7 replies
-
When I have teensy debug running this is what I get instead in the debug log:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
This is my makefile
|
Beta Was this translation helpful? Give feedback.
0 replies
-
This is my ld file:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
AFAIK, unless you start the watchdog timer deliberately, there is none. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Okay what would cause micropython to soft-reboot after 8 seconds (cannot reproduce in debugger, debugger doesn't reboot or call breakpoint/error). I believe I turned watchdog timers off with a -D in the Makefile. Of course I should explain myself, I'm trying to combine the teensy 4.1 core with micropython, so I can get the teensy audio library alongside micropython, because it is very nice. Of which I'm considering just porting the audio library to c python or whatever I have to do at this point and using the SGTL5000 driver in micropython instead of the teensy core. However, I've been using this code base forever and that would be a giving up sort of option. It boots teensy code fine but I removed the reset_Handler() completely from Startup.S or whatever. Loaded the isr_vector into the teensy core in place of the dummy_isr() in interrupts.c. My theory is it is a timer that is being overwritten or something or maybe it doesn't get out of a loop somewhere. All I'm calling is this in the beginning. It seems to load but then reboots after 8 seconds, always on the dot. 8 seconds from boot where the serials become active from the teensy core. I have also added threading support, somewhat, through freeRTOS for teensy but I actually use teensy threads to call the thread for micropython although that is actually commented out.
I have a feeling it has to do with this because that's the end of the log before it resets
need to switch to alternate clock during reconfigure of ARM PLL
Any help? Some code and other stuff below.
When would the USB PLL be reconfigured in micropython, I call ImageVector first in my .ld file and removed reset_handler() completely from the .S associated with micropython
This is the teensy 4.1 printf debug log;
I have also patch mphalport.c -> mphalport.cpp
Beta Was this translation helpful? Give feedback.
All reactions