System Issue with Tracker SOM EVAL Board

dilipkumarmadda · October 13, 2023, 1:14pm

Hello,

I have my Firmware based on the Tracker Edge Firmware Version 17. I am using MCP CAN and few other peripherals to have my application developed, but some times when i open Serial monitor for debug information i see the Following

Serial connection closed.  Attempting to reconnect...
Serial monitor opened successfully:
0000001341 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000001341 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000001342 [ncp.client] TRACE: Powering modem on, ncpId: 0x64
0000001343 [net.pppncp] TRACE: NCP event 3
0000001343 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_POWERING_UP
0000001344 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000001344 [system.nm] TRACE: Interface 4 power state changed: 4
0000003470 [app.gps.ubx] INFO: enable PUBX-POSITION
0000003476 [app.gps.ubx] INFO: enable PUBX-SVSTATUS
0000003478 [app.gps.ubx] INFO: enable PUBX-TIME
0000003503 [app.gps.ubx] INFO: enable GPS
0000003503 [app.gps.ubx] INFO: enable QZSS
0000003503 [app.gps.ubx] INFO: enable SBAS
0000003503 [app.gps.ubx] INFO: enable Galileo
0000003504 [app.gps.ubx] INFO: enable BeiDou
0000003504 [app.gps.ubx] INFO: enable GLONASS
0000003508 [app.gps.ubx] INFO: set to power management mode 0
0000003510 [app.gps.ubx] INFO: set dynamic platform model to 0
0000003515 [app] TRACE: waiting for stable GNSS lock for triggers
0000003517 [app] TRACE: waiting for stable GNSS lock for triggers
0000004517 [app] TRACE: waiting for stable GNSS lock for triggers
0000005517 [app] TRACE: waiting for stable GNSS lock for triggers
0000006517 [app] TRACE: waiting for stable GNSS lock for triggers
0000007517 [app] TRACE: waiting for stable GNSS lock for triggers
0000008517 [app] TRACE: waiting for stable GNSS lock for triggers
0000009517 [app] TRACE: waiting for stable GNSS lock for triggers
0000010517 [app] TRACE: waiting for stable GNSS lock for triggers
0000010726 [net.pppncp] TRACE: NCP event 3
0000010727 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_UP
0000010727 [system.nm] TRACE: Interface 4 power state changed: 2
0000010728 [ncp.client] TRACE: Modem powered on
0000011517 [app] TRACE: waiting for stable GNSS lock for triggers
0000011732 [ncp.client] TRACE: NCP ready to accept AT commands
0000012517 [app] TRACE: waiting for stable GNSS lock for triggers
0000012755 [mux] INFO: Starting GSM07.10 muxer
0000012756 [mux] INFO: Opening mux channel 0
0000012756 [mux] INFO: GSM07.10 muxer thread started
0000012857 [mux] INFO: Opening mux channel 1
0000012910 [ncp.client] TRACE: NCP state changed: 1
0000012911 [net.pppncp] TRACE: NCP event 1
0000012941 [ncp.client] TRACE: NCP connection state changed: 1
0000012941 [net.pppncp] TRACE: NCP event 2
0000012941 [net.pppncp] TRACE: State changed event: 1
0000012954 [ncp.client] TRACE: NCP connection state changed: 2
0000012955 [mux] INFO: Opening mux channel 2
0000013004 [net.pppncp] TRACE: NCP event 100
0000013004 [net.pppncp] TRACE: New auth info
0000013007 [net.pppncp] TRACE: NCP event 2
0000013008 [net.pppncp] TRACE: State changed event: 2
0000013517 [app] TRACE: waiting for stable GNSS lock for triggers
0000014090 [system.nm] INFO: State changed: IFACE_UP -> IFACE_LINK_UP
0000014093 [system.nm] INFO: State changed: IFACE_LINK_UP -> IP_CONFIGURED
0000014095 [net.pppncp] TRACE: Negotiated MTU: 1500
0000014095 [system] INFO: Cloud: connecting
0000014100 [system] WARN: Failed to load session data from persistent storage
0000014517 [app] TRACE: waiting for stable GNSS lock for triggers
0000014668 [system] INFO: Cloud socket connected
0000014668 [comm.protocol.handshake] INFO: Establish secure connection
0000014674 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2
0000015518 [app] TRACE: waiting for stable GNSS lock for triggers
0000016517 [app] TRACE: waiting for stable GNSS lock for triggers
0000016591 [comm.protocol.handshake] INFO: Sending HELLO message
0000016592 [comm.coap] TRACE: Sending CoAP message
0000016593 [comm.coap] TRACE: CON POST /h size=39 token= id=3
0000016905 [comm.coap] TRACE: Received CoAP message
0000016906 [comm.coap] TRACE: ACK 0.00  size=4 token= id=3
0000016907 [comm.protocol.handshake] INFO: Handshake completed
0000016908 [comm.protocol.handshake] TRACE: Updating cached session parameters
0000016908 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000016910 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 3
0000016946 [hal] TRACE: Cached ESP32 NCP firmware version: 7
0000017398 [hal] TRACE: Cached ESP32 NCP firmware version: 7
0000017412 [comm.coap] TRACE: Sending CoAP message
0000017412 [comm.coap] TRACE: CON POST /d?\x01 size=233 token=21 id=4
0000017422 [comm.coap] TRACE: Sending CoAP message
0000017422 [comm.coap] TRACE: CON POST /E/spark/device/last_reset size=42 token= id=5
0000017425 [comm.coap] TRACE: Sending CoAP message
0000017426 [comm.coap] TRACE: CON POST /E/particle/device/updates/enabled size=44 token= id=6
0000017429 [comm.coap] TRACE: Sending CoAP message
0000017430 [comm.coap] TRACE: CON POST /E/particle/device/updates/forced size=44 token= id=7
0000017433 [comm.coap] TRACE: Sending CoAP message
0000017434 [comm.coap] TRACE: CON GET /t size=7 token=22 id=8
0000017436 [comm.coap] TRACE: Sending CoAP message
0000017437 [comm.coap] TRACE: CON POST /d?\x02 size=30 token=23 id=9
0000017440 [comm.protocol] INFO: Sending subscriptions
0000017440 [comm.coap] TRACE: Sending CoAP message
0000017441 [comm.coap] TRACE: CON GET /e/particle?u size=17 token= id=10
0000017444 [comm.coap] TRACE: Sending CoAP message
0000017444 [comm.coap] TRACE: CON GET /e/spark?u size=14 token= id=11
0000017517 [app] TRACE: waiting for stable GNSS lock for triggers
0000017882 [comm.coap] TRACE: Received CoAP message
0000017884 [comm.coap] TRACE: ACK 0.00  size=5 token=21 id=4
0000017884 [comm.protocol] TRACE: Updating system DESCRIBE checksum
0000017885 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000017920 [hal] TRACE: Cached ESP32 NCP firmware version: 7
0000018371 [hal] TRACE: Cached ESP32 NCP firmware version: 7
0000018387 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 3
0000018488 [comm.coap] TRACE: Received CoAP message
0000018488 [comm.coap] TRACE: ACK 0.00  size=4 token= id=5
0000018517 [app] TRACE: waiting for stable GNSS lock for triggers
0000018590 [comm.coap] TRACE: Received CoAP message
0000018590 [comm.coap] TRACE: ACK 0.00  size=4 token= id=6
0000018692 [comm.coap] TRACE: Received CoAP message
0000018692 [comm.coap] TRACE: ACK 0.00  size=4 token= id=7
0000018794 [comm.coap] TRACE: Received CoAP message
0000018794 [comm.coap] TRACE: ACK 2.05  size=10 token=22 id=8
0000018795 [comm.protocol] INFO: Received TIME response: 1697202425
0000018826 [comm.coap] TRACE: Received CoAP message
0000018826 [comm.coap] TRACE: ACK 0.00  size=5 token=23 id=9
0000018828 [comm.protocol] TRACE: Updating application DESCRIBE checksum
0000018828 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000018830 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 3
0000018930 [comm.coap] TRACE: Received CoAP message
0000018930 [comm.coap] TRACE: ACK 0.00  size=4 token= id=10
0000019032 [comm.coap] TRACE: Received CoAP message
0000019032 [comm.coap] TRACE: ACK 0.00  size=4 token= id=11
0000019034 [comm.protocol] TRACE: Updating subscriptions checksum
0000019034 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000019036 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 3
0000019136 [comm.coap] TRACE: Received CoAP message
0000019136 [comm.coap] TRACE: CON POST /E/particle/device/updates/pending size=47 token=01 id=49105
0000019138 [comm.coap] TRACE: Sending CoAP message
0000019138 [comm.coap] TRACE: ACK 0.00  size=4 token= id=49105
0000019141 [system] INFO: Cloud connected
0000019517 [app] TRACE: waiting for stable GNSS lock for triggers
0000020001 [app] INFO: cloud sent: {"cmd":"sync","time":1697202426,"hash":"C7B69385F66DF2EAA1DB8E3BE52E1C32"}
0000020002 [comm.coap] TRACE: Sending CoAP message
0000020003 [comm.coap] TRACE: CON POST /E/sync size=86 token= id=12
0000020425 [comm.coap] TRACE: Received CoAP message
0000020425 [comm.coap] TRACE: ACK 0.00  size=4 token= id=12
0000020517 [app] TRACE: waiting for stable GNSS lock for triggers
0000021517 [app] TRACE: waiting for stable GNSS lock for triggers
0000022517 [app] TRACE: waiting for stable GNSS lock for triggers
0000023517 [app] TRACE: waiting for stable GNSS lock for triggers
0000023947 [comm.coap] TRACE: Received CoAP message
0000023948 [comm.coap] TRACE: CON GET /d?\x04 size=9 token=02 id=49106
0000023949 [comm.protocol] INFO: Received DESCRIBE request; flags: 0x04
0000023950 [comm.coap] TRACE: Sending CoAP message
0000023951 [comm.coap] TRACE: ACK 0.00  size=4 token= id=49106
0000023988 [comm.coap] TRACE: Sending CoAP message
0000023988 [comm.coap] TRACE: CON 2.05  size=193 token=02 id=13
0000024265 [comm.coap] TRACE: Received CoAP message
0000024266 [comm.coap] TRACE: ACK 0.00  size=4 token= id=13
0000024517 [app] TRACE: waiting for stable GNSS lock for triggers
0000025517 [app] TRACE: waiting for stable GNSS lock for triggers
0000026517 [app] TRACE: waiting for stable GNSS lock for triggers
0000027517 [app] TRACE: waiting for stable GNSS lock for triggers
0000028517 [app] TRACE: waiting for stable GNSS lock for triggers
0000029517 [app] TRACE: waiting for stable GNSS lock for triggers
0000030517 [app] TRACE: waiting for stable GNSS lock for triggers
0000031517 [app] TRACE: waiting for stable GNSS lock for triggers
0000032517 [app] TRACE: waiting for stable GNSS lock for triggers
0000033517 [app] TRACE: waiting for stable GNSS lock for triggers
0000034517 [app] TRACE: waiting for stable GNSS lock for triggers
0000035517 [app] TRACE: waiting for stable GNSS lock for triggers
0000036517 [app] TRACE: waiting for stable GNSS lock for triggers
0000037517 [app] TRACE: waiting for stable GNSS lock for triggers
0000038517 [app] TRACE: waiting for stable GNSS lock for triggers
0000039517 [app] TRACE: waiting for stable GNSS lock for triggers
0000040517 [app] TRACE: waiting for stable GNSS lock for triggers
0000041517 [app] TRACE: waiting for stable GNSS lock for triggers
0000042517 [app] TRACE: waiting for stable GNSS lock for triggers
0000043517 [app] TRACE: waiting for stable GNSS lock for triggers
0000044517 [app] TRACE: waiting for stable GNSS lock for triggers
0000045517 [app] TRACE: waiting for stable GNSS lock for triggers
0000046517 [app] TRACE: waiting for stable GNSS lock for triggers
0000047517 [app] TRACE: waiting for stable GNSS lock for triggers

-until the following

0000099423 [ncp.esp32.client] TRACE: NCP state changed: 0
0000099424 [ncp.esp32.client] TRACE: Deinit modem serial.

and later is see nothing from the Serial other than the RGB Led breathinf CYAN
what does it means
Please Explain this and Pressing the Reset also did not help other than Flashing the Software again

Thanks

rickkas7 · October 13, 2023, 1:30pm

The LED is breathing cyan because it cloud connected here:

0000019141 [system] INFO: Cloud connected

This message means that the GNSS (GPS) unit does not have a lock. It stops outputting that when it gets a lock, which presumably you eventually did. It takes longer if there are obstructions.

0000024517 [app] TRACE: waiting for stable GNSS lock for triggers

This may or may not be relevant. It's related to the Wi-Fi module that's used for Wi-Fi geolocation, but I think this message may always occur after the location event it sent, which it would have after getting a lock.

0000099423 [ncp.esp32.client] TRACE: NCP state changed: 0
0000099424 [ncp.esp32.client] TRACE: Deinit modem serial.

Are you sure you never get any more messages? It might take 23 minutes before the next logging message if the system is stable, and then only if in trace mode. In normal (LOG_LEVEL_INFO) you might not get a message until the next location event it sent, which would depend on your settings in the console.

dilipkumarmadda · October 13, 2023, 2:43pm

0000099423 [ncp.esp32.client] TRACE: NCP state changed: 0
0000099424 [ncp.esp32.client] TRACE: Deinit modem serial.

After i get this the device continuously breathing CYAN and i cannot see anything from the Serial Port,
Sorry for asking again Can you elaborate this a bit more

Are you sure you never get any more messages? It might take 23 minutes before the next logging message if the system is stable, and then only if in trace mode. In normal (LOG_LEVEL_INFO ) you might not get a message until the next location event it sent, which would depend on your settings in the console.

I did not understand what you mean here.......................
Also i will explain my concept
I used Tracker Edge Firmware 17 version to build firmware and i am using CAN to receive the data and i also used the location Service class to get the data from the GPS and i am publishing this data to the cloud whenever i want.

like i said sometimes i see the logs which i posted before and it stops.

I also have one more question in the Tracker Edge Firmware github code

//PRODUCT_ID(TRACKER_PRODUCT_ID);
PRODUCT_VERSION(TRACKER_PRODUCT_VERSION);

i compile this . But in my case i want to use 10 Devices of Tracker SOM under a product lets say Product1 and i want to have the version of this product as 1 is this possible? because i built my firware based on Tracker Edge Firmware 17 does means that i cannot this value to 1 ??

I also want to Know if i have to enable and disable anything from the Tracker Edge Firware 17 if i want to have control over my Software

Thanks in Advance

system · April 13, 2024, 2:43am

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Tracker in unknown state after wake up from discharge Edge Systems tracker , tracker-som	27	879	October 27, 2023
Tracker device restarts without obvious reasons after system request to power off interface Device OS tracker	3	740	March 11, 2022
Tracker One crashes Firmware	3	461	January 6, 2022
[LTE] Tracker SoM with Tracker Edge sometimes crashes when trying to publish to Cloud Edge Systems	5	292	March 20, 2023
[SOLVED] Using library Can-mcp25x causes "Failed to power on modem" on Tracker One Libraries	13	1278	November 28, 2020

System Issue with Tracker SOM EVAL Board

Related topics