Can only use Debugger with DA14695 on SmartSnippets Studio

⚠️
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.
4 posts / 0 new
Last post
stevenchick
Offline
Last seen: 3 years 4 months ago
Joined: 2019-05-22 13:34
Can only use Debugger with DA14695 on SmartSnippets Studio

Dear all,

I've recently just started working with the DA14695 Development Kit with SDK 10.0.4.66.2, in order to try to upload the proximity reporter example using the QSPI Serial Programmer. I am able to upload the Code using the Debugger, however when I use the Serial Programmer, the advertising data does not send and I receive the following output when Programming:

Setting serial port baud rate to 57600.
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00002000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00004000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00006000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00008000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0000a000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0000c000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0000e000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00010000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00012000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00014000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00016000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00018000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0001a000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0001c000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0001e000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00020000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00022000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00024000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00026000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00028000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0002a000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0002c000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0002e000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00030000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00032000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00034000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00036000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00038000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0003a000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0003c000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0003e000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00040000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00042000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00044000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00046000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00048000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0004a000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0004c000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0004e000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00050000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00052000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00054000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00056000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x00058000 chunk size: 0x00002000
Writing to address: 0x00002000 offset: 0x0005a000 chunk size: 0x00001f80
done.

 

........................................................................................................................
..
.. Programming product header
..
........................................................................................................................
. Using configuration:
. Product ID: DA1469x-00
. Product Header:
.     active_image_address: 0x2000
.     update_image_address: 0x2000
.     flash_name: MX25U3235F
.     flash_size: 4M
.     flash_burstcmda_reg_value: 0xa8a500eb
.     flash_burstcmdb_reg_value: 0x66
.     flash_write_config_command: 0x1 0x40 0x7
.
cli_programmer 1.26
Copyright (c) 2015-2019 Dialog Semiconductor

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

Writing to address: 0x00001000 offset: 0x00000000 chunk size: 0x00001000
done.

 

I have also tried using the JTag programmer, however I also receive an error message saying the command netstat is either written incorrectly or cannot be found. If anyone has also experienced this problem, or has some guidance towards this issue, I would greatly appreciate any feedback. I can also provide any other data/code as necessary. Many thanks in advance.

Steven

 

Device: 
PM_Dialog
Offline
Last seen: 9 months 1 day ago
Staff
Joined: 2018-02-08 11:03
Hi Steve,

Hi Steve,

Please check from the attachments the steps you should follow in order to burn the QSPI flash with the PXP Reported firmware. It is recommended to erase the QSPI Flash before programming it. Also, you should select the appropriate COM port in which the DK is connected. Open the Window’s Device Manager in order to find the COM port and select the smaller one COM port number. After this procedure, you should reset the board and the chip will start advertising. You could clarify it by using a generic BLE mobile application. In case that you are trying to program the flash though JTAG, could you please share me a screenshot with the error message?

Thanks, PM_Dialog

Attachment: 
stevenchick
Offline
Last seen: 3 years 4 months ago
Joined: 2019-05-22 13:34
Hi,

Hi,

Thanks for your reply, everything is working now :)

It seems my problem was that I had not reset the board after flashing. I tested this with other applications as well and it is working perfect. Next time I will keep these steps in mind if I run into these kinds of problems again.

Many thanks,

Steven

PM_Dialog
Offline
Last seen: 9 months 1 day ago
Staff
Joined: 2018-02-08 11:03
Hi Steven,

Hi Steven,

Glad that you figured your issue out. If you have any other issues, please create a new forum thread and do let us know.

Thanks, PM_Dialog