Skip to main content

SmartSnippets v3.7 CLI will not work if download firmware by hand

5 years ago

SmartSnippets v3.7 CLI will not work if download firmware by hand

Posted bysummer201005140 points 4 replies
0 upvotes

I test the SmartSnippets v3.7 CLI tool, and I find this strange problem.

First I download the firmware by clicking the CONNECT button using the SmartSnippets v3.7 GUI, everything goes well, and the log is

[INFO @15-04-28 18:50:40] Firmware File C:\Users\SUMMER\SmartSnippets\resources\jtag_programmer.bin has been selected for downloading.
[INFO @15-04-28 18:50:40] Cortex-M: Debugger tries to set PC to odd value. Corrected register value from 0x000800B5 to 0x000800B4
[INFO @15-04-28 18:50:40] Successfully downloaded firmware file to the board.

But if I download the firmware by hand, which refers to the Command Line Interface, using the command
SmartSnippets.exe -type booter -chip DA14580-01 -jtag 123456 -file "C:\Users\SUMMER\SmartSnippets\resources\jtag_programmer.bin"
the log is definitely the same as the one generated by SmartSnippets v3.7 GUI

Firmware File c:\users\summer\desktop\burn\jtag_programmer.bin has been selected for downloading.
Cortex-M: Debugger tries to set PC to odd value. Corrected register value from 0x000800B5 to 0x000800B4
Successfully downloaded firmware file to the board.

but everything goes wrong, I can't perform any operations successfully any more.

And what's more, if I download the firmware by GUI, and then use CLI, everything goes well again.

What's wrong with CLI ?

5 years ago

summer20100514 0 points

I use an logic analyzer to monitor the SPI bus, I find that there is noise signal which I think the firmware isn't loaded successfully at all. But why do I get the success log output ?

5 years ago

JE_Dialog

Hello Summer, we are arranging for Skynoon to contact you : Huayu from our local office i believe reached out to you. Can you confirm they are in contact ?
BR JE_Dialog

5 years ago

summer20100514 0 points

Thank you, I solved the problem.

5 years ago

summer20100514 0 points

I solve the problem. I add [-firmware] option to each command I want to execute, and everything goes well.