Hi Dialog,
我试图根据AN-B 20使用CLI编程OTP自定义代码。
But following message is shown and programming procedure can not be successful.
"null port is not a valid FTDI device uart port"
The above phenomenon occurs even if we use USB-UART FTDI device that is mounted on the DA14580 motherboard (UM-B-014).
This is appeared from SmartSnippest 3.2 and there was no problem with SmartSnippest 3.1.
What does the above error mean? Also, can you resolve?
Hello Shuhei,
我们在SmartSnippets的3.2中找到了几个错误。
These are fixed in the new version 3.4.
Please, give this new version a try.
Best regards, BB_Dialog.
Dialog BLE Support Team.
你好对话小组
Thanks for your reply.
I tried with SmartSnippets 3.4. But no changes.
In Dialog environment, does this phenomenon occur ? or not occur?
Hello Shuhei,
it works well for me.
Please could you copy/paste your CLI command here, so that we can try the same command.
Best regards, BB_Dialog.
你好对话小组
Thanks for your reply.
We tried by the follwing CLI commnd . Please confirm.
C:\Program Files\SmartSnippets_ver3_4\bin\SmartSnippets.exe -type otp -chip DA14580-01 -com_port 10 -baudrate 57600 -uart P0_4 -cmd write_custom_code -file "C:\Program Files\SmartSnippets_ver3_4\bin\full_emb_sysram.hex" -offset 0x0
-------------------------------------------------------------------------------------------------------
For your information,
OTP write/read procedure is successful with Smart Snippets GUI. With CLI, Error ouurs.
Therefore, we think that there is no problem in hardware connection.
-------------------------------------------------------------------------------------------------------
Hi Shuhei,
Thanks.
I could reproduce the error using your command.
We are working on it to solve it.
Best regards, BB_Dialog.
Hi Shuhei,
the error has been confirmed. Working on a solution for next version.
For the time being, when changing the syntax, by adding the -firmware option, it works for us.
所以,请在你身边尝试一下:
example:
SmartSnippets.exe -type otp -chip DA14580-01 -com_port 44 -baudrate 57600 -uart P0_4 -cmd write_custom_code -firmware "D:\SmartSnippets\resources\programmer_ES5.bin" -file "D:\SSTest\full_emb_sysram.hex" -offset 0x0 -y
Best regards, BB_Dialog.
Hi, it seems that the new version smartsnippets v3.7 doesn't fix the problem. I still need to add [-firmware ] option to execute the command line successfully.
你好对话小组
Thanks for your reply.
I confirmed that OTP writing works well with the command that you proposed.
For the time being,we will introduce this changed syntax.
However, In this syntax, it is necessary to boot the firmware(programmer_ES5.bin) every time writing OTP header and OTP image.
Therefore we look forward to improvements in the next Version.
Hello Shuhei,
good to hear it's working for you now.
We sure will fix this in next version.
best regards, BB_Dialog.
Dialog BLE Support Team.
你好对话小组
Please let know release date of nexte version.
我们需要的信息。
Best regards, Shuhei Matsushita
Hello Shuhei,
we will announce it on this website.
Best regards, BB_Dialog.
你好对话小组
Is there any update ?
We need the next ver SmartSnippets.
Best regards
Hi Shuhei,
the relase will be in the end of this week.
Best regards, BB_Dialog.
你好对话小组
Thanks for your information.
We are looking forward to the release in this weekend.
Best Regards
Hi Dialog,
I am trying to use the latest version of SmartSnippets through the CLI to program the EEPROM on my device. This works properly through the graphical version of SmartSnippets, but not through the CLI.
I successfully manage to put the flash_programmer.bin firmware onto my device with this command:
SmartSnippets.exe -type booter -chip DA14580-01 -com_port 16 -uart P0_2 -file flash_programmer.bin
That command states that it successfully loads the flash_programmer.bin file, but does not state that it has disconnected from the COM port. I then attempt to program the EEPROM with this command:
SmartSnippets.exe -type eeprom -chip DA14580-01 -com_port 16 -uart P0_2 -cmd write -offset 0x0000 -file image.hex
That command asks if I want to make my device bootable, and then attempts to connect to COM16. It returns an error saying that COM16 is already in use. What is the proper way of programming EEPROM over CLI?