Traces and Development Mode

IoT Modules Development tools
1

Hi All,

I’m using a Fastrack Supreme 20.
After much effort, I have finally managed to get traces to show up in the trace window.

My problem is, after a few minutes, In Target Management Mode, I get a message, “Target is not in development mode (click here to fix)”. When this happens, my traces stop as well.

I click the link to restore development mode, and I get a flood of traces.

Any idea why it switches out of development mode?

system:
Fastrack Supreme 20, with i/o (USB and COM2)
Firmware: R7.43.0.201003261552
Bootloader: V08b0j
Open AT OS Package: 6.32.0.03
Developer Studio 1.2.0.201012171243-R6026

tia

2

Is the target restarting?

3

That’s what I am trying to determine, but I suspect it is.

Thing is, same code on my dev kit with Q2687 and latest Firmware, seems to run fine.

4

In that case, the DS behaviour is normal.

It is not uncommon to have a “latent” bug that happens not to manifest on one target, but does on another.
This is a common experience in software development - not at all specific to Open-AT!

5

Looking at the Backtraces I seem to have a watchdog reset.

Watch dog reset. Tsk 30
Unknown function (0)
Unknown function (0)

6

Below i have a trace that shows some detail.

Looking at the first line, and it’s repeat on line 10, we see traffic that happens about once a minute.

Just after the second packet of data, we have some trouble. (see bold)
Does this mean that the firmware has caused a watchdog reset?

11/02/09,12:26:13:120 - 001;ADL;6;UART2 - Data received from Panel. Number of bytes: 57
11/02/09,12:26:13:126 - 002;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_ETX
11/02/09,12:26:13:132 - 003;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_EOT
11/02/09,12:26:13:137 - 004;ADL;5;ZCP2_2 - EOT Received
11/02/09,12:26:13:142 - 005;ADL;5;ZCP2_2 - CheckSum passed
11/02/09,12:26:13:148 - 006;ADL;5;ZCP2_2 - Panel to PC test message
11/02/09,12:26:13:154 - 007;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_SOH
11/02/09,12:26:13:158 - 008;ADL;5;ZCP2_2 - ZCP2_2_SendAck
11/02/09,12:26:13:164 - 009;ADL;5;ZCP2_2 - Communicating TargetID = 2
11/02/09,12:27:17:137 - 001;ADL;6;UART2 - Data received from Panel. Number of bytes: 57
11/02/09,12:27:17:143 - 002;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_ETX
11/02/09,12:27:17:149 - 003;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_EOT
11/02/09,12:27:17:168 - 004;ADL;5;ZCP2_2 - Panel to PC test message
11/02/09,12:27:17:173 - 005;ADL;5;ZCP2_2 - eZCP2_2_state = ZCP2_2_e_SOH
11/02/09,12:27:17:177 - 006;ADL;5;ZCP2_2 - ZCP2_2_SendAck
11/02/09,12:27:17:180 - 007;ADL;5;ZCP2_2 - Communicating TargetID = 2
11/02/09,12:27:17:826 - 008;FLASH;1;WM mirror set up
11/02/09,12:27:17:829 - 009;SYS;1;OAT Task index : 0
11/02/09,12:27:17:832 - 010;SYS;1;Watch dog reset. Tsk 30
11/02/09,12:27:17:882 - 011;SYS;1;OAT Task index : 0
11/02/09,12:27:17:892 - 012;RTK;6;A | 16 | 1 | 15 | 070100 | 0x180d416c |@0026aeb1
11/02/09,12:27:17:896 - 013;RTK;6;A | 16 | 1 | 15 | 070100 | 0x180d418c |@002653dd

tia, again!

7

Fairly unlikely - far more likely to be your application.

8

Means that the watchdog reset occurred in Open AT task 0.