cli programmer error cannot open serial port

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
jagath52
Offline
Last seen: 1 year 6 months ago
Joined: 2020-07-06 10:40
cli programmer error cannot open serial port

Hello 

I am using dialog 1469 usb development kit and not able to program or use cli_programmer.exe for writing data. Device is connected in com3 port. Any procedure is there for

writing data with cli_programmer.exe

What is the procedure for writing data with cli_programmer.exe

 

currently devices is programmed using jtag through USB can cli_programmer.exe be used to write data in same port.

 

E:\socialDistancing\iOT3_WiRA\binaries>cli_programmer.exe com3 read_qspi 0xFE100 - 0x20
cli_programmer 1.26
Copyright (c) 2015-2019 Dialog Semiconductor

Using serial port com3 at baud rate 1000000.
cannot open serial port

E:\socialDistancing\iOT3_WiRA\binaries>cli_programmer.exe COM3 read_qspi 0xFE100 - 0x20
cli_programmer 1.26
Copyright (c) 2015-2019 Dialog Semiconductor

Using serial port COM3 at baud rate 1000000.
cannot open serial port

E:\socialDistancing\iOT3_WiRA\binaries>cli_programmer.exe COM3 boot uartboot.bin
cli_programmer 1.26
Copyright (c) 2015-2019 Dialog Semiconductor

Using serial port COM3 at baud rate 1000000.
cannot open serial port

 

Thank you

Jagath

Device: 
LC_Dialog
Offline
Last seen: 1 year 4 months ago
Staff
Joined: 2016-09-19 23:20
Hi Jagath,

Hi Jagath,

Looks like the programmer is unable to open the COM port and communicate over the serial interface. I am trying to reproduce this on my end. I will follow up again with a solution. Will keep you posted.

Also, can you please if the COM port is accurate. COM3 can be a system port on some PCs. Check if you are using the right JLink CDC UART port.

Best regards,
LC_Dialog

 

jagath52
Offline
Last seen: 1 year 6 months ago
Joined: 2020-07-06 10:40
Hello 

Hello 

I have tried com3 and com4 same problem is there.

I tried to run the jlink gdb server and i coudn't find the device number da1469 in jlink gdb window.

Is there any other to write the data into NVMS_PARAM_PART of nvms

Thank you

Jagath

jagath52
Offline
Last seen: 1 year 6 months ago
Joined: 2020-07-06 10:40
Hello 

Hello 

Please can anyone answer for this issue 

I want to store data in nvpram NVMS_PARAM_PART part through cli_programmer but cli_programmer is giving error.

Is there any other way to store data NVMS_PARAM_PART

In social distancing example project in documentation NVMS_PARAM_PART base address is 0x0FE000 for proDK board.

For usb development board what is the base address NVMS_PARAM_PART and i am not able to use cli_programmer for usb development board

 

Thank you

Jagath

 

KB_Dialog
Offline
Last seen: 4 weeks 1 day ago
Staff
Joined: 2020-01-20 09:45
Hello Jagath,

Hello Jagath,

I've been unable to repoduce the problem you are seeing here with my WiRa dev kits.

As LC_Dialog mentioned, please check the COM port in Windows Device Manager.

For my Laptop, my USB WiRa board is on COM118.

C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries>cli_programmer com118 read_qspi 0xff100 - 0x20
cli_programmer 1.26

Copyright (c) 2015-2019 Dialog Semiconductor

Using serial port com118 at baud rate 1000000.
bootloader file not specified, using internal uartboot.bin

Setting serial port baud rate to 115200.
Connecting to device... 
Press RESET. 
Uploading boot loader/application executable... 
Executable uploaded. 

Setting serial port baud rate to 1000000. 
000FF100 ; FF 7F FF FF FF FF FF FF FF FF FF FF FF FF FF FF ;.............. 
000FF110 ; FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ; ................ 
done. C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries> 

The GDB server is not needed for UART coms, but can be enabled with the following commands:-
First launch the GDBserver deamon - 

 C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries>cd "c:\Program Files (x86)\SEGGER\JLink_V660f"
c:\Program Files (x86)\SEGGER\JLink_V660f>JLinkGDBServer -if swd -speed auto -device Cortex-M33

Next we read the flash:-

c:\Program Files (x86)\SEGGER\JLink_V660f>cd C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries

C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries>cli_programmer.exe gdbserver read_qspi 0xff100 - 0x20
cli_programmer 1.26
Copyright (c) 2015-2019 Dialog Semiconductor

bootloader file not specified, using internal uartboot.bin

Uploading boot loader/application executable...
Executable uploaded.

000FF100   FF 7F FF FF FF FF FF FF FF FF FF FF FF FF FF FF   ...............
000FF110   FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF   ................
done.

C:\Users\KB_Dialog\SDK\WiRa_10.440.8.4\binaries>

The flash used on the USB and Pro Dev kit is the same so the NVMS_PARAM_PART address can be referenced.

BR,

KB_Dialog