Developement vs Production

⚠️
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//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
Sun, 2020-10-11 07:14
#1
Subramanyan
Offline
Last seen:5 days 15 hours ago
Joined:2020-07-15 12:43
Developement vs Production

Hi,

I am using WiRA 10.440.8.6 SDK on DA14695 Development Kit. Until now, I have been working with DEVELOPMENT mode configured in custom_config_qspi.h

#define dg_configIMAGE_SETUP DEVELOPMENT_MODE

我能够flash和可以看到f的结果lashing with address location in the Console.

However, when I changed it to PRODUCTION_MODE and flashed, I dont see the flash addresses anymore.

I only see the following messages on the Console.

........................................................................................................................
..
.. PROGRAM QSPI
..
........................................................................................................................
.
........................................................................................................................
..
.. Programming image
..
........................................................................................................................
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.

After a couple of minutes of waiting, when I reset the board, I get the following messages

Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Writing to address: 0x00002000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x2000 failed. Retrying ...
Write to qspi failed. Abort.

write to QSPI failed: unknown error (-300)

.
........................................................................................................................
. ERROR:
. cli_programmer.exe" has exited with code: 1
.
. call: "D:\Nodle_Workspace_10.6\WiRa_10.440.8.6\WiRa_10.440.8.6\binaries\cli_programmer.exe" --cfg C:\Users\subbu\AppData\Local\Temp\tmp2oe_jyok --check-booter-load --no-kill gdbserver write_qspi 8192 C:\Users\subbu\AppData\Local\Temp\tmp5o8ry8l1
........................................................................................................................
.
.
........................................................................................................................
..
.. FINISHED
..
........................................................................................................................

I think because I set to Production mode, it is no longer able to flash. Is there something I need to do differently ? A quick response is deeply appreciated.

Thanks and Regards,

Subramanyan

Device:
DA1469x
Mon, 2020-10-12 15:40
PM_Dialog
Offline
Last seen:1 day 18 hours ago
Staff
Joined:2018-02-08 11:03
Hi Subramanyan,

Hi Subramanyan,

I am not able to replicate this. Did you build the project for production mode successfully and without any errors?

Would it be possible to provide extra inputs to replicate this?

Thanks, PM_Dialog

Mon, 2020-10-12 17:40
Subramanyan
Offline
Last seen:5 days 15 hours ago
Joined:2020-07-15 12:43
Yes, the Production build

Yes, the Production build built successfully without any issue. The Production build also flashed fine. After that if I flash any other build, I see the issue mentioned.

Regards,

Subramanyan

Mon, 2020-10-12 17:41
Subramanyan
Offline
Last seen:5 days 15 hours ago
Joined:2020-07-15 12:43
Hi,

Hi,

Could the production build which is running be disabling any further flash operations?

Regards,

Subramanyan

Tue, 2020-10-13 15:00
PM_Dialog
Offline
Last seen:1 day 18 hours ago
Staff
Joined:2018-02-08 11:03
Hi Subramanyan,

Hi Subramanyan,

The PRODUCTION_MODE has nothing to do with the flash programming. I am not able to replicate in my side. The python scripts that are used for the flash programming, download raw binary data into the flash regardless from the firmware.

I would suggest you erase the QSPI Flash first, and then try to program it. Are you able to erase it using the python scripts from the SDK?

Thanks, PM_Dialog