RT1050_QSPI DAPLINK Flashing not working.
- Dominant language
- C
- Stars
- 2.8k
- Forks
- 1.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
We have a RT1050_EVB board with QSPI flash boot enabled.
DAPLink firmware compiled out within this ARMmbed/DAPLink isn't working.
I have tried all below three, none of them works for me.
1. 0254_k20dx_mimxrt1050_evk_qspi_0x8000.bin from release254.
2. Self compiled k20dx_mimxrt1050_evk_qspi_if_crc_legacy_0x8000_master.bin from latest master branch.
3. Self compiled k20dx_mimxrt1050_evk_qspi_if_crc_legacy_0x8000_May2019.bin from some old version.
There is one working I found from NXP website. https://www.nxp.com/assets/downloads/data/en/initialization-boot-device-driver-code-generation/k20dx_mimxrt1050_evk_qspi_if_crc_20180419.zip
While I could never found that git-hash source code in this ARMmbed/DAPLink repo.
@mmahadevan108 , seems like some compatibility issue there. Any ideas how could we fix this here?
From: | | Work? | Hash
-- | -- | -- | --
NXP_WEBSite | | V | 342d091d6d64ad1f8dbb3a5384c08be7fe926f5b
master | | x | 300c8203a07b3aff916ea86becd16a30f6952e9b
May_2019 | | x | 483b3b3c19e877b69180249b5b76d339f681624f
V254 | | x | f499eb6ec4a847a2b78831fe1acc856fd8eb2f28
Below is the test binaries and results.
[DAPLinks.zip](https://github.com/ARMmbed/DAPLink/files/4311429/DAPLinks.zip)
Contributor guide
Research direction
Start with the attached DAPLinks.zip and compare the reported results for the NXP_WEBSite, master, May_2019, and V254 binaries and their listed hashes. Trace the RT1050 EVB QSPI flashing path to identify the compatibility difference; done means a firmware built from this repository flashes and boots successfully with QSPI enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100