HI Qualcomm Team:
i no connect J34 pin1 and pin2, but it enter EDL mode(Download Mode ),same time it can not flash image, Before can be normal flash image.
https://upload.cc/i1/2019/01/16/UiGau3.png
How can I solve it?
Best Regards
Rick
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.
Can you please provide us your build path and instructions used for the flashed image ?
We are not able to view the image, kindly share us differend shared location.
The issue usually occurs if you try to flash manufacturing image instead of mission mode image.
Kindly note the mission mode image will be available in location @target\quartz\demo\XXXX_demo\build\gcc
Hi
i updata the image,
https://drive.google.com/file/d/1lmWdl_TqqidLLbOD_ZF0MuCzcU9EYhtw/view?u...
i just use USB connect J6, no connect J34.
my build path is
C:\Users\user\Desktop\qca4020.or_.3.0_00011.1\QCA4020.OR.3.0_00011.1\target\quartz\demo\QCLI_demo\build\gcc
Best Regards.
Rick.
The path you are building the application is correct but after looking into your pin configurations, I request you try below pin setting for flashing and booting the application in QCA4020.
hi gesqdn-forum:
I follow your steps and the result is the same.
The point is that I didn't connect any foot of J34, he always showed QDLoader 9008(EDL mode).
you can look
https://drive.google.com/open?id=1lnMPIWYX0xTg8UvR3sYLydplb6G-TuMM
Is it possible that there is a problem with the hardware?
Best Regards
Rick
Its hard to comment on the hardware fault at this stage.
Can you try to build and flash latest SDK image to check if the problem still persists ?
Hi raja_pedada:
now i next step need do what?
Best Regards,
Rick.
From the port_trace.txt we could observe the device fails to erase few sectors and its unable to complete programming the flash.
> Can you confirm there is no modifications performed with respect to flash configuration and rebuild the image ?
>Can you confirm if you are able to flash same image on to different CDB device.
> The issue can be due to loaded corrputed image on CDB device.
> However, if you install jumper on J34 1 and 2 the device should go to "HS-USB QDLoader 9008" to let you flash the image.
> After successful flash you should be able to come out of EDL mode.
Hi raja_pedada:
> Can you confirm there is no modifications performed with respect to flash configuration and rebuild the image ?
>Can you confirm if you are able to flash same image on to different CDB device.
> The issue can be due to loaded corrputed image on CDB device.
> However, if you install jumper on J34 1 and 2 the device should go to "HS-USB QDLoader 9008" to let you flash the image.
> After successful flash you should be able to come out of EDL mode.
Its hard to debug the issue as we dont see such cases where device stuck in EDL mode always.
Kindly follow the below steps to resolve the issue:
> Unplug the device from USB and remove the USB cable from laptop/PC.
> Based on latest image provided via drive link, remove the Jumpers on J16, remove jumper on J33.
> Put jumper on J34 1&2, insert USB cable on J6 and other end to different slot on PC/laptop.
> Check if you are able to detect the EDL and flash the image.
> If you still face issue while flashing or unable to come out of EDL mode after flashing, we suspect issue some issue might be with the hardware as you confirmed that with same image you are able to flash on different CDB device.
Hi raja_pedada
I tried it many times and the results are the same.
if hardware issue, how i can do it?
Where can I send it for repair?
Best Regards,
Rick.
Its suggested to check with the vendor on how to ship the device for hardware issues.
I'm running in to the same issue, trying to use EDL mode. The erase step fails with SPI-NOR Errors. Has anyone run into this and found a solution. (I'm using a Silex module.)
Hi,
I ran into a similar problem once, when we got a new batch of Silex modules. The root cause was that the Silex module used a different flash type not supported by SDK version I used. I needed to step-up to a new SDK version, now on 3.1 and it worked again.
Maybe this works for you as well.
Andreas
Thanks Andreas. Sounds like I ran into the same thing. I have been meaning to follow up on this and confirm that going to the v3.2SDK solved the issue. In my case, I had migrated to the new SDK but had an environment variable set pointing to the old one, which meant that I was actually mixing both. Once I removed that, it worked.
Chuck