⚠️
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.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
REEASD
Offline
Last seen:1 year 9 months ago
加入:2019-07-15 04:05
QSPI program fail

Dear dialog:

I try to program bin file by QSPI ,it build ok,but when use Run > External Tools > program_qspi_jtag,i get this error:

EGGER J-Link GDB Server V6.40 Command Line Version

JLinkARM.dll V6.40 (DLL compiled Oct 26 2018 15:06:02)

Command line: -if swd -device Cortex-M33 -endian little -speed 8000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -log jlink.log -singlerun -rtos GDBServer/RTOSPlugin_FreeRTOS
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: on
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: Cortex-M33
Target interface: SWD
Target interface speed: 8000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OB-SAM3U128 V3 compiled Jul 12 2018 12:17:50
硬件:V3.00
S / N: 483087475
Checking target voltage...
Target voltage: 3.30 V
ERROR: Failed to listen at socket (Err = -1)
ERROR: Failed to open listener port 2331
Restoring target state and closing J-Link connection...
Shutting down...
Failed to open listener port 2331

I can program and debug PAM ok.

so what can i do for this?

Device:
PM_Dialog
Offline
Last seen:2 days 18 hours ago
工作人员
加入:2018-02-08 11:03
Hi REEASD,

Hi REEASD,

I suppose that you ran the DA1469x-00-Debug_QSPI firstly and it was executed successfully. If yes, I would suggest you to the the program_qspi_config script adding the correct parameters and then erase_qspi_jtag (or erase_qspi_serial). Are you using any of our development boards or you have a custom board? After that having selected the DA1469x-00-Debug_QSPI generated folder from the “Project Explorer” windows, execute program_qspi_jtag (or program_qspi_serial). If you are unable to program the QSPI flash through JTAG, please try it through UART (serial option). Please try the above steps and let me know with the results.

Thanks, PM_Dialog

REEASD
Offline
Last seen:1 year 9 months ago
加入:2019-07-15 04:05
Dear Dislog:

Dear Dislog:

Hi,i use the development boards(DA14699).This is my program_qspi_config:

Product ID :DA1469X-00

Product Header:

active_image_address:0X2000

updata_image_address:0x2000

flash_size:4M

flash_burstcmda_reg_value:0xa8a500eb

flash_burstcmdb_reg_value:0x66

flash_write_config_command:0x1 0x40 0x7.

I can use erase_qspi_jtag and erase_serial success,but when i use program_qspi_jtag or program_qspi_serial, i can get this:

Variable references empty selection: ${project_loc}

i try Priject->Clean,but it is not work.

thanks.

PM_Dialog
Offline
Last seen:2 days 18 hours ago
工作人员
加入:2018-02-08 11:03
Hi REEASD,

Hi REEASD,

Please check the attached file and follow the suggested steps. This is a reference for the ble_adv example of the SDK. The project_loc should be set with your full path to the selected project. Make sure that you have the same configurations. After that, as described in step_5, having selected the ble_adv from the “Project Explorer” window, try to program the QSPI flash. Please let me know if this procedure figures your issue out.

Thanks, PM_Dialog

附件: