MicroMod Beta Testing

Running without the HardFault code enabled ...

Seeing the T.MM put into OFF? Half second press On/Off brings it back?

So maybe when I was not seeing the T.MM and switching USB ports it was losing OFF state memory since I have no Battery on? It wasn't the PC port - but the T.MM switching OFF?

Is that from ? :: tempmon_PwrDwn()

<edit> Added : Serial.printf( "\tdeg C=%u\n" , (uint32_t)tempmonGetTemp() );
it is showing:: C=52

Started Ex_2 again - all stuff - no HardFault ....
 
FYI I just pushed up new branch/PR with a 'V' version of the 'F' that uses UpdateScreenAsync(true) and updates the screen each time we get a new camera update...

It looks better but sound not as good!
 
Restarted again - showing 52C - my IR Thermo see's highest external board temp at 30.2C

Something very odd?

Restarting from RUN - then starts SSD1306 - nothing else and has restarted 3 times again?

After 3rd restart it was ignoring the P_Button - then a few seconds later restarted again?

Then I hit Program - get T.MM orange light ... then it restarts again?

And it just did that again and I had TyComm closed?

And again - from T.MM orange light in Program - it just restarts?

Doing 15s Restore ... will come back and try updated Zelda.

Okay - before I could leave - T.MM restarted. I pushed Button, and it then restarts again {From Program Mode}? And that repeated? And now again?

Moved to USB on HUB ... took a couple tried to get 15s Restore to trigger?

Looking I don't see LED blink?
> Camera in 8 bit socket
> SD card in socket
> Cable to ili9341 direct to socket, except DC pin wired to #4
> Rx5 crossed to Tx5 with jumper on 20 and 21
> SSD1306 unplugged from SCL1/SDA1 Qwicc

Programmed simple blink with Serial loop()/sec count ... running okay ... Some 30 seconds ...

Then Power OFF

Then restarted - ran 34 seconds and restarted

... updated sketch to count seconds for me and removed some early spew ... restarted ... okay at 80 secs
 
FYI I just pushed up new branch/PR with a 'V' version of the 'F' that uses UpdateScreenAsync(true) and updates the screen each time we get a new camera update...

It looks better but sound not as good!

Ok just did the merge and downloaded.

Gave it a try and see what you mean about the audio. But first just to let you know it now works from within a thread - I go curious.

A funny thing with the audio is that the buzz (for lack of me knowing another term) happens on the update, when the # sign prints. Could be a delay in audio someplace caused by each update or.... Not an audio guy so don't know.
 
Running without the HardFault code enabled ...

Seeing the T.MM put into OFF? Half second press On/Off brings it back?

So maybe when I was not seeing the T.MM and switching USB ports it was losing OFF state memory since I have no Battery on? It wasn't the PC port - but the T.MM switching OFF?

Is that from ? :: tempmon_PwrDwn()

<edit> Added : Serial.printf( "\tdeg C=%u\n" , (uint32_t)tempmonGetTemp() );
it is showing:: C=52

Started Ex_2 again - all stuff - no HardFault ....

Think think temp powerdown did a restart unless it hit panic temp - have to look again know we made some changes. But don't know why you should be hitting that kind of temp. I've been doing all kinds of stuff with it just shutting off on me. Will have to play with your set up to see whats going on but to be honest I am only using 4 bit mode on the BB.
 
Think think temp powerdown did a restart unless it hit panic temp - have to look again know we made some changes. But don't know why you should be hitting that kind of temp. I've been doing all kinds of stuff with it just shutting off on me. Will have to play with your set up to see whats going on but to be honest I am only using 4 bit mode on the BB.

Was wondering it the 1062 on this PCB needed any diff calibration or is that internal? Nothing seems hot outside - that was just the only reason to see it shutdown that came to mind as we haven't been doing watchdogs. It did make me disable the HardFault in case that was an issue.

Doesn't explain failure of Blink in 15s Restore ... seems that was an early test that worked?

I did go back to 8 bit {_hmConfig == 2} - but that was just toggling to test speed diff shown by 't' where 4 bit loses a fps.
 
Was wondering it the 1062 on this PCB needed any diff calibration or is that internal? Nothing seems hot outside - that was just the only reason to see it shutdown that came to mind as we haven't been doing watchdogs. It did make me disable the HardFault in case that was an issue.

Doesn't explain failure of Blink in 15s Restore ... seems that was an early test that worked?

I did go back to 8 bit {_hmConfig == 2} - but that was just toggling to test speed diff shown by 't' where 4 bit loses a fps.

Calibration comes from the chip registers. But i did just check in the cores. 52 is still below the high temp alarm so shouldn't be an issue:
Code:
static uint32_t highAlarmTemp   = 85U;
static uint32_t lowAlarmTemp    = 25U;
static uint32_t panicAlarmTemp  = 90U;

EDIT: I know example2 is in the lib but just wanted the latest version. Been a bit preoccupied today with going a bunch of bags with sensors and putting them with labels in a box = argh
 
T.MM has been unplugged some minutes.

Plugged in holding Button, Release button to Orange Program LED

2 seconds later it leaves Windows and is OFF. Half second press of On/Off and it restarted to not blinking 15s Restore code.
 
T.MM has been unplugged some minutes.

Plugged in holding Button, Release button to Orange Program LED

2 seconds later it leaves Windows and is OFF. Half second press of On/Off and it restarted to not blinking 15s Restore code.

What I am seeing is that if I do a ON/OFF it restarts the sketch.

If I do a 15s restore it blinks yellow - I release the button and wait for what seems forever then it starts blinking - I hear the beep telling me it reconnected and I am seeing it as a RawHid device. So all is well in my test. Not sure what is going on with yours.
 
Calibration comes from the chip registers. But i did just check in the cores. 52 is still below the high temp alarm so shouldn't be an issue:
Code:
static uint32_t highAlarmTemp   = 85U;
static uint32_t lowAlarmTemp    = 25U;
static uint32_t panicAlarmTemp  = 90U;

EDIT: I know example2 is in the lib but just wanted the latest version. Been a bit preoccupied today with going a bunch of bags with sensors and putting them with labels in a box = argh

Thanks for confirm on calbrate #'s - I wasn't sure if there was any other underlying 'map' factor to control those values. Weird thing is 52C is quite warm at 125F and I don't feel ANY sense of that. Thermometer showing 1062 at 30.2 didn't even feel warm to my cold finger at 27C when my wrist is 31C. I know the sensor isn't the same as surface temp - but 30.2 is only 86F.

This version of example_2 had the SSD1306 added and also the Serial5 code that talks to itself. I turned off the dot print as on restart it would prints uncontrolled until 't' or 'F' was turned on.
 
Thanks for confirm on calbrate #'s - I wasn't sure if there was any other underlying 'map' factor to control those values. Weird thing is 52C is quite warm at 125F and I don't feel ANY sense of that. Thermometer showing 1062 at 30.2 didn't even feel warm to my cold finger at 27C when my wrist is 31C. I know the sensor isn't the same as surface temp - but 30.2 is only 86F.

This version of example_2 had the SSD1306 added and also the Serial5 code that talks to itself. I turned off the dot print as on restart it would prints uncontrolled until 't' or 'F' was turned on.

If you remember we always had issues with the temp monitor reading hotter that we expected. You might want to try @LAtimes library: https://github.com/LAtimes2/InternalTemperature keep meaning to check it out - think he does something different.
 
Mike - does this say yours shuts down as times? :: "I've been doing all kinds of stuff with it just shutting off on me."

If you remember we always had issues with the temp monitor reading hotter that we expected. You might want to try @LAtimes library: https://github.com/LAtimes2/InternalTemperature keep meaning to check it out - think he does something different.

It was always a good indicator though on T_4's much closer than 35+ degrees. When tempmon read 50-60 it was over 100F. But when OC's it could die just over 50's.

At this point it isn't usable when a 15s Restore won't blink and a simple blink won't run, and powering up to 'Program' pops out in 2 seconds.

HOWEVER: Just plugged T.MM into a USB power bank and did the 15s Restore and it came up blinking! Program mode won't light Orange LED with no data lines - but it does stop the blinking. Then repowering returns to Blue Blink ????

I'm going to reinstall TD 1.54 Beta 7 - to wipe out any local changes. Are there any changes I need to make from git/CORES?

It is either some CORES edit - or my PC ??? seems like PC as something kept the 15s Restore from completing to Blue Blink. Put it back on my PC USB and it is blue blinking until I reinstall Beta 7.
 
Tim
Sorry - mine has never just shut down on me for no reason like you are seeing. Have had problems but that was my own fault not for temp.

Just tried the 15s restore with the Zelda sketch and camera with no problems.

As for core updates - don't remember think there was some stuff from @KurtE and @Paul. I would probably just download the latest core?
 
Left T.MM running the Battery Pack installed 15s Restore blink - plugged back into PC - ran the string trimmer down the driveways to get rid of some angst ...

Came in and T.MM was resetting - speakers were on and wife says "Yeah, it's been busy doing that " chimming - for some 15 minutes perhaps every 20-30 seconds?

Just started stopwatch and moved the T.MM to an SFun ATP board ...
 
Left T.MM running the Battery Pack installed 15s Restore blink - plugged back into PC - ran the string trimmer down the driveways to get rid of some angst ...

Came in and T.MM was resetting - speakers were on and wife says "Yeah, it's been busy doing that " chimming - for some 15 minutes perhaps every 20-30 seconds?

Just started stopwatch and moved the T.MM to an SFun ATP board ...

Well I moved the SSD1306 to sda/scl since that is Wire2 and SDA1/SCL1 is actually Wire - you probably mentioned that earlier but I just noticed it. At least for this test.

If I start with a 't' I see the 1306 screen updating and then if I do a 'f' the ssd1306 stops updating but the sketch is still running so that is probably a code issue. "F" doesn't work takes a single snap shot. Anyway this a capture from the Arducam App no problem and then tried a few commands again:
Code:
LP#=1	Pri#=1001	last Pri=67537	ms=307446	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=311118	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=314790	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=318462	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=323970	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=327642	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=331314	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=334986	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=338658	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=342330	ipCyc%=0.05	deg  C=54
Reading frame
Finished reading frame
LP#=1	Pri#=1001	last Pri=67537	ms=346130	ipCyc%=0.05	deg  C=54
* continuous mode started
redraw rate = 0.01 Hz	 secs = 347		deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=349826	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=355334	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=359006	ipCyc%=0.05	deg  C=54
redraw rate = 0.45 Hz	 secs = 359		deg  C=54
* continuous mode stopped
LP#=1	Pri#=1001	last Pri=67537	ms=362678	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=366350	ipCyc%=0.05	deg  C=54
Reading frame
Finished reading frame
LP#=1	Pri#=1001	last Pri=67537	ms=370147	ipCyc%=0.05	deg  C=54
Reading frame
Finished reading frame
LP#=1	Pri#=1001	last Pri=67537	ms=373959	ipCyc%=0.05	deg  C=54
LP#=1	Pri#=1001	last Pri=67537	ms=377631	ipCyc%=0.05	deg  C=54

no hangs so far will let it run but change back to wire first.
 
I just used the code copied from AdaF example - and plugged it in to one and it worked. The code shows &Wire - so yeah it was on the Qwiic that worked.

Nothing should stop the SSD1306 boxes running ?

Unchanged 'f' should be single and "F" should be continuous if it is working?

21 minutes and the ATP mounted T.MM is still blinking blue without interruption? Maybe something odd on the PJRC.BB ????

Seems I can move that back to SFun.ML and run that sketch moved to ML settings ... Let me go grab a git/CORES ....
 
Switching back to wire I am seeing this now when I do a 'f'
Code:
LP#=1	Pri#=1001	last Pri=67537	ms=48431	ipCyc%=0.05	deg  C=50
Reading frame
error writing to HM01B0
Finished reading frame
LP#=1	Pri#=1001	last Pri=67537	ms=52285	ipCyc%=0.05	deg  C=50
LP#=1	Pri#=1001	last Pri=67537	ms=57793	ipCyc%=0.05	deg  C=50
[COLOR="#FF0000"]Reading frame
error writing to HM01B0
Finished reading frame[/COLOR]
LP#=1	Pri#=1001	last Pri=67537	ms=61649	ipCyc%=0.05	deg  C=51
but the snapshot still updates.

OK let this case run for awhile:
Code:
LP#=36	Pri#=1001	last Pri=67537	ms=1072082	ipCyc%=0.05	deg  C=54
LP#=35	Pri#=1001	last Pri=67537	ms=1073070	ipCyc%=0.05	deg  C=54
LP#=35	Pri#=1001	last Pri=67537	ms=1074083	ipCyc%=0.05	deg  C=54
LP#=35	Pri#=1001	last Pri=67537	ms=1075071	ipCyc%=0.05	deg  C=53
Reading frame
Finished reading frame
LP#=31	Pri#=1001	last Pri=67537	ms=1076074	ipCyc%=0.05	deg  C=53
LP#=36	Pri#=1001	last Pri=67537	ms=1077088	ipCyc%=0.05	deg  C=53
LP#=35	Pri#=1001	last Pri=67537	ms=1078075	ipCyc%=0.05	deg  C=54
LP#=35	Pri#=1001	last Pri=67537	ms=1079089	ipCyc%=0.05	deg  C=54
LP#=35	Pri#=1001	last Pri=67537	ms=1080077	ipCyc%=0.05	deg  C=54
LP#=36	Pri#=1001	last Pri=67537	ms=1081090	ipCyc%=0.05	deg  C=54
no restarts or hangs that I can see.
 
I just used the code copied from AdaF example - and plugged it in to one and it worked. The code shows &Wire - so yeah it was on the Qwiic that worked.

Nothing should stop the SSD1306 boxes running ?

Unchanged 'f' should be single and "F" should be continuous if it is working?

21 minutes and the ATP mounted T.MM is still blinking blue without interruption? Maybe something odd on the PJRC.BB ????

Seems I can move that back to SFun.ML and run that sketch moved to ML settings ... Let me go grab a git/CORES ....

Ok now that I moved it back to wire (SDA1/SCL1) boxes still running with 't' running. But "F" still does not show on the ILI9341
 
T.MM on ATP up for 29 minutes while I fought github to get the right CORES ... over wrote them.

SSD1306 plugged into Qwiic on ML and working.

ili9341 does 'f' here , but like yours "F" is NO UPDATE ... look for "if (0)" in code - I turned off the display update to assure it wasn't behind my faulting.

And also fps requested as (60) in that sketch
 
Change that to if (1) to get "F"

ALSO line ~369 back to 30 - fails on (60) :: hm01b0.set_framerate(30); //15, 30, 60, 120
 
Change that to if (1) to get "F"

ALSO line ~369 back to 30 - fails on (60) :: hm01b0.set_framerate(30); //15, 30, 60, 120

Yeah 60 don't work well except with GPIO version.

Back to this with 4bit on the breakout everything is working now including @KurtE's 'V' mode.
Code:
LP#=36	Pri#=1001	last Pri=67537	ms=18185	ipCyc%=0.05	deg  C=49
Reading frame
Finished reading frame
LP#=30	Pri#=1001	last Pri=67537	ms=19172	ipCyc%=0.05	deg  C=49
LP#=36	Pri#=1001	last Pri=67537	ms=20185	ipCyc%=0.05	deg  C=49
Reading frame
Finished reading frame
LP#=30	Pri#=1001	last Pri=67537	ms=21184	ipCyc%=0.05	deg  C=49
Reading frame
Finished reading frame
LP#=30	Pri#=1001	last Pri=67537	ms=22182	ipCyc%=0.05	deg  C=49
LP#=36	Pri#=1001	last Pri=67537	ms=23196	ipCyc%=0.05	deg  C=50
LP#=34	Pri#=1001	last Pri=67537	ms=24184	ipCyc%=0.05	deg  C=49
LP#=36	Pri#=1001	last Pri=67537	ms=25197	ipCyc%=0.05	deg  C=49
LP#=35	Pri#=1001	last Pri=67537	ms=26185	ipCyc%=0.05	deg  C=49
* continuous mode started
redraw rate = 0.04 Hz	 secs = 27		deg  C=49
LP#=31	Pri#=1001	last Pri=67537	ms=27231	ipCyc%=0.05	deg  C=50
LP#=15	Pri#=1001	last Pri=67537	ms=28238	ipCyc%=0.06	deg  C=49
LP#=14	Pri#=1001	last Pri=67537	ms=29219	ipCyc%=0.06	deg  C=49
LP#=15	Pri#=1001	last Pri=67537	ms=30226	ipCyc%=0.06	deg  C=50
LP#=14	Pri#=1001	last Pri=67537	ms=31207	ipCyc%=0.06	deg  C=49
LP#=15	Pri#=1001	last Pri=67537	ms=32215	ipCyc%=0.06	deg  C=50
LP#=14	Pri#=1001	last Pri=67537	ms=33196	ipCyc%=0.06	deg  C=50
LP#=15	Pri#=1001	last Pri=67537	ms=34203	ipCyc%=0.06	deg  C=49
LP#=15	Pri#=1001	last Pri=67537	ms=35210	ipCyc%=0.06	deg  C=50
* continuous mode stopped
LP#=16	Pri#=1001	last Pri=67537	ms=36203	ipCyc%=0.06	deg  C=50
LP#=35	Pri#=1001	last Pri=67537	ms=37190	ipCyc%=0.05	deg  C=50
LP#=36	Pri#=1001	last Pri=67537	ms=38230	ipCyc%=0.05	deg  C=51
* continuous mode (Video) started
redraw rate = 0.08 Hz	 secs = 39		deg  C=50
LP#=31	Pri#=939	last Pri=67411	ms=39235	ipCyc%=0.05	deg  C=50
LP#=20	Pri#=605	last Pri=66739	ms=40209	ipCyc%=0.03	deg  C=50
going to let it run for awhile and see what happens, but looks like its working. No tearing or splits.
 
SSD stops updating about here:
Code:
LP#=5	Pri#=594	last Pri=66721	ms=163181	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=593	last Pri=66721	ms=169493	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=606	last Pri=66739	ms=173739	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=605	last Pri=66739	ms=177947	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=607	last Pri=66749	ms=182193	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=606	last Pri=66739	ms=186401	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=594	last Pri=66721	ms=190609	ipCyc%=0.03	deg  C=52
LP#=1	Pri#=606	last Pri=66739	ms=194855	ipCyc%=0.03	deg  C=52
but display in 'V' mode still working and so is the sketch.

Sorry time for zzz's now for me.

All I can say is that I am not seeing the same problems you were seeing on the TMM.BB while in 4bit mode.
 
Back
Top