Closed juhhov closed 4 years ago
Hi All,
I believe https://github.com/mbedmicro/pyOCD/pull/838 + https://github.com/mbedmicro/pyOCD/pull/845 should have fixed the pyocd flash command issue.
While the pyocd erase command still have "No ACK received" errors.
Just FYI.
Thanks.
Sounds like this case could be closed a new one should be raised for the --erase, instead.
After few flash rounds the board goes to "No cores were discovered!" state and has to be restored with dip switch altering and erase. This blocks CI usage.
Steps:
pyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash printer_MIMXRT1050_EVK.hex
pyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash payload_MIMXRT1050_EVK.hex
pyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash payload_null_MIMXRT1050_EVK.hex
Using pyoCD version mbedmicro/pyOCD@fdc69fac102880de4b845bcedf540dbd0c43d7b5. daplink.txt no_cores_were_discovered_trace.txt binaries.zip
Ok, then this definitely cannot be closed. This is a blocker issue, @mmahadevan108 @maclobdell - can we get some runtime, please? Test automation simply will not work this kind of behaviour.
Created #861 and #862. I'll close this.
Flash MIMXRT1050-EVKB board constantly fails. There seems to be two type of errors occurring. Daplink details.txt and full traces are attached.
Error number one:
pyocd.probe.pydapaccess.dap_access_api.DAPAccessIntf.TransferError: No ACK received
Error number two:pyocd.core.exceptions.DebugError: No cores were discovered!
daplink.txt trace.txt trace2.txt