Search Results
Search results 1-5 of 5.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Quote from SEGGER - Alex: “Agree or not, your choice. Fact is: All J-Link flash loaders are designed to work with the natively memory-mapped space of the chip. For the RP2040 this is 16 MB, according to the datasheet. This means, J-Link will be able to program & verify 16 MB of QSPI reliably. Moving the 16 MB “window” to another portion of the flash (so effectively configure the QSPI controller to use fixed high-bits != 0 during memory mapped accesses) is not supported and there is no plan to do…
-
I guess it doesn't really matter once L1 verification can be disabled, but I am not attempting to do anything different at all between the two chips. I am simply trying to flash the exact same code, to the exact same address (0x10000000 memory map, 0x00 flash address), in the exact same way on both chips. But when I am using a chip larger than 16MB, the JLink is not allowing me to write anything at all to the first 16 MB of the larger flash chip. Should I not able to flash the first 16MB of the …
-
I disagree that this is not a bug for the following reasons: 1. I am not flashing or debugging beyond the memory mapped space; anything above the map is for persistent storage only and does not interact with the JLink. 2. Your provided RP2040 examples do not work with the larger flash chip; these also are not going beyond the memory mapped space. 3. Your RP2040_M0_0 device specifies a flash size of 64MB, which is what I selected for my hardware. 4. I don’t see how a verification process, which I…
-
After more investigation into this, I would say there is definitely an error; possibly with the RP2040 flash loader but as I don't have access to the DSK, I cannot tell. The RP2040 IS capable of using more than 16MB of flash memory. Perhaps the error was made due to misinterpretation of the datasheet; XIP, not the chip itself, is only able to use 16MB. Anyways, as a complete hack of a workaround, you can change any of the web commander parameters by sending post requests via curl or wget. To det…
-
I've run into a issue where flashing / debugging the RP2040 chip is not possible if the attached flash chip is larger than 16MB. If I manually connect to the device using J-Link commander, and then disable L1 & L2 verification via the web control panel, I am able to successfully flash the chip. But if I try and flash / debug through ozone, embedded studio, or J-Link GDB server, sectors are erased properly, but the data does not get written properly. Unfortunately, I have not found a way to disab…