Hi, the steps you wrote do use the "sf" commands, there is nothing wrong with it. And I have no issues using "sf" to read/write flash, and ROM loader to boot from it. The question was: even if U-Boot uses config mode to read/write QSPI via "sf" command, what does mean "mapped at"? For me, using "cp length" should make a copy of QSPI flash to RAM since the QSPI is mapped for reading. U-Boot's "cp" is flash-aware, so it should understand that some address is in flash, and use proper method to read/write it. It works in both directions for parallel NOR flash mapped at 08000000. But since it does not work for "cp" from QSPI, it may mean that U-Boot "thinks" that the memory is mapped, and just does memcpy(), but there is no real mapping, and thus no QSPI data is copied. Please, feel free to close this thread if desired. The main question of booting was resolved. But I still do not understand why mapped GPMC/NOR works (can be read/write with "cp"), but mapped QSPI can't be read with the same "cp". I think that "sf read/write" must work in any case (using config mode and QSPI commands), but "cp" should also read QSPI content if it is mapped at address space.
↧