AnsweredAssumed Answered

Discrepancy between AN-1160 and CM3WSD

Question asked by enpa on Aug 4, 2017
Latest reply on Aug 15, 2017 by enpa

I sniffed the communication between CM3WSD and ADuCM350.

I've found a different behaviour from what described in the Application Note.

 

First question:

07 0e 15 57 00 00 01 20 9b 70 00 00 9d 70 00 00 9f 70 00 00 a1 70 00 00 3b
07 0e 09 57 00 00 01 30 a3 70 00 00 5c
07 0e 15 57 00 00 01 34 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 6f

The first line writes 16 bytes to the address 0x00000120.

The second line writes only 4 bytes to the address 0x00000130.

The third line goes on at 0x00000134 (which is correct).

Why? Is this a page boundary? What is the size of the pages?

 

Second question:

Similar, but around address 0x000007f4. Here the shorter write command is sent twice:

07 0e 15 57 00 00 07 e4 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff b9
07 0e 09 57 00 00 07 f4 ff ff ff ff a9
07 0e 09 57 00 00 07 fc 58 dc 0d fe 5e
07 0e 15 57 00 00 08 00 01 21 10 f0 1f 02 91 40 df f8 e8 29 40 b2 43 09 52

 

Third question:

the verify commands should use two messages (according to the AN). I see three of them:

07 0e 0d 57 00 05 ff f8 00 00 00 00 00 00 00 00 a0 (last write command at address 0x0005fff8)

07 0e 09 56 80 00 00 00 58 dc 0d fe e2 (first verify message, as described in the AN)
07 0e 09 56 90 00 00 00 ff ff ff ff 15 (weird verify message, with 0x9******* as Value field)
07 0e 09 56 00 00 00 00 58 dc 0d fe 62 (second message?)

 

Can someone please clarify these points so that I can write a bootloader host?

 

Thank you, Enpa

Outcomes