Forums - Flash the image failed

7 posts / 0 new
or Register
Last post
Flash the image failed
skyzhao
Join Date: 5 Dec 18
Posts: 6
Posted: Thu, 2018-12-27 17:21
Top

Hi everyone

I use the QCA4020 in our project, not in the CDB20, when flash the image using the USB, see the next log:

qflash.py Info: Generate partition table...
qflash.py Info: Generate FWD table...
[2018-12-28 09:09:24,558] INFO: Checking for fi
are Descriptor Table 0 File:gen_fwd_table.py:67
[2018-12-28 09:09:24,575] INFO: Done Generating
d_table.py:711 Function:gen_xml_program
qflash.py Info: Download device programmer...
qflash.py Info: Device Programmer loaded succes
qflash.py Info: Skipping to program image
qflash.py Info: Program flash. Please wait...
 
wait long time (more than 5 mins) no respond, I guess some settings are wrong in my board, output\port_trace.txt messages are below, there are some errors,  can you give me some advices in this issue.
 
09:09:25: DEBUG: XML FILE (96 bytes): CharsInBuffer=1000-96=904
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: SPINOR Error -1 (3)"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'ERROR: SPINOR Error -1 (3)'
09:09:25: DEBUG: XML FILE (96 bytes): CharsInBuffer=904-96=808
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: SPINOR Error -1 (3)"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'ERROR: SPINOR Error -1 (3)'
09:09:25: DEBUG: XML FILE (117 bytes): CharsInBuffer=808-117=691
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the SPI NOR Device -1 (3)"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'ERROR: Failed to open the SPI NOR Device -1 (3)'
09:09:25: DEBUG: XML FILE (123 bytes): CharsInBuffer=691-123=568
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device 2 slot 0 partition 0"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'ERROR: Failed to open the device 2 slot 0 partition 0'
09:09:25: DEBUG: XML FILE (119 bytes): CharsInBuffer=568-119=449
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Device type 2, slot 0, partition 0, error 3"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'INFO: Device type 2, slot 0, partition 0, error 3'
09:09:25: DEBUG: XML FILE (130 bytes): CharsInBuffer=449-130=319
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="WARN: Get Info failed to open 2 slot 0, partition 0, error 3"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'WARN: Get Info failed to open 2 slot 0, partition 0, error 3'
09:09:25: DEBUG: XML FILE (118 bytes): CharsInBuffer=319-118=201
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="storage_device_get_num_partition_sectors FAILED!"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'storage_device_get_num_partition_sectors FAILED!'
09:09:25: DEBUG: XML FILE (122 bytes): CharsInBuffer=201-122=79
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="parseSectorValue could not handle start_sector value"/>
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: INFO: TARGET SAID: 'parseSectorValue could not handle start_sector value'
09:09:25: DEBUG: XML FILE (79 bytes): CharsInBuffer=79-79=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
-------------------------------------------------------------------------------------------
 
09:09:25: DEBUG: Response was 'NAK'
 
 
_____                    
|  ___|                   
| |__ _ __ _ __ ___  _ __ 
|  __| '__| '__/ _ \| '__|
| |__| |  | | | (_) | |   
\____/_|  |_|  \___/|_|  
 
 
09:09:25: {ERROR: handleErase:6931 Something failed with the <erase> command. The port_trace.txt can shed more information on this
Note that for eMMC <erase> is only valid for physical_partition 0. For UFS <erase> is valid for all LUNs
 
 
Many thanks
SkyZhao
  • Up0
  • Down0
Re: Flash the image failed
jaydenk
Join Date: 21 Jun 18
Posts: 64
Posted: Mon, 2019-01-07 15:48
Top

Hi SkyZhao,

Could you let us know which flash part is used for your board?

Thanks
BR,
Jayden

  • Up0
  • Down0
Re: Flash the image failed
Dias
Join Date: 16 Jul 18
Posts: 4
Posted: Sun, 2019-05-26 23:55
Top

Hi Jayden,

I use QCA4024 in our project.

When flashing the image using the USB, I got the same error (SPINOR Error -1 (3)) in the port_trace.txt with Winbond W25Q32FV 3V 32M-BIT flash.

Could you please help to address this issue?

Thanks a lot.

 

Here is my test environment:

PC <-USB-> QCA4024 (Entered EDL mode by controlling GPIO) <-QSPI-> Winbond flash

 

Dias

 

  • Up0
  • Down0
Re: Flash the image failed
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Wed, 2019-06-05 20:58
Top
Kindly confirm if you are using QCA4024 SDK to build and flash the image on 4024 device: QCA4024.OR.3.0 QCA OEM SDK+CDB ( https://developer.qualcomm.com/download/qca4020-qca4024/qca4024or11-qca-... ) In case of 4020 kindly use QCA4020.OR.3.0 QCA OEM SDK+CDB (https://developer.qualcomm.com/download/qca4020-qca4024/qca4020or11-qca-... )
  • Up0
  • Down0
Re: Flash the image failed
Dias
Join Date: 16 Jul 18
Posts: 4
Posted: Wed, 2019-06-26 02:44
Top

Hi Jayden,

 

After using correct flash, I can burn the flash.

Thank you for your help.

 

Best regards,

Dias

  • Up0
  • Down0
Re: Flash the image failed
s_yuan
Join Date: 2 Mar 20
Posts: 2
Posted: Fri, 2020-09-18 00:25
Top

Hi,raja_pedada

I got the same error on the different plateform,mine is QCS405.

But there is not related forums about mine plateform,so I reply you here.

Could you please share me some suggestions about this case,thanks.

 

2020-09-18 11:15:14.033    11:15:14: INFO: TARGET SAID: 'INFO: Calling handler for program'

2020-09-18 11:15:14.033    
2020-09-18 11:15:14.034    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 0 partition 0'
2020-09-18 11:15:14.034    
2020-09-18 11:15:14.034    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:0 partition:0 error:0'
2020-09-18 11:15:14.035    
2020-09-18 11:15:14.035    11:15:14: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 147279664'
2020-09-18 11:15:14.035    
2020-09-18 11:15:14.036    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3
  • Up0
  • Down0
Re: Flash the image failed
s_yuan
Join Date: 2 Mar 20
Posts: 2
Posted: Fri, 2020-09-18 00:26
Top

Hi,raja_pedada

I got the same error on the different plateform,mine is QCS405.

But there is not related forums about mine plateform,so I reply you here.

Could you please share me some suggestions about this case,thanks.

 

2020-09-18 11:15:14.033    11:15:14: INFO: TARGET SAID: 'INFO: Calling handler for program'

2020-09-18 11:15:14.033    
2020-09-18 11:15:14.034    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 0 partition 0'
2020-09-18 11:15:14.034    
2020-09-18 11:15:14.034    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:0 partition:0 error:0'
2020-09-18 11:15:14.035    
2020-09-18 11:15:14.035    11:15:14: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 147279664'
2020-09-18 11:15:14.035    
2020-09-18 11:15:14.036    11:15:14: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3
  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.