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.
-
I am trying to add a segment to a build for a RT1052 board. On the RT1052 you need to have a config section for QSPI which is located at the start of flash ( 0x60000000 ) which is 512 bytes long I inserted this section above the vector assignments in (MIMXRT1052_Vectors.s) Additionally you need to have IVT, which has info about the image in flash. I modified my flash_placement.xml file to add this segment, as follows. <ProgramSection alignment="4" load="No" name=".boot_hdr" start="0x60001000" />…
-
Hi Nino I am using this targeting a NXP eval board with QSPI flash on it. It sounds like there is no support on JLink QSPI at this time. I am considering using a LPC-Link2, which it looks like it make itself look like a JLink The eval board has 32MB of sdram on it so, that I could use. But when we load code the sdram has not been initialized. Is there a workaround for that. I created a sdram_placement.xml to place everything into sdram. By looking at the map file it looks to have worked. I am us…
-
I am trying to use a JLink Ultra+ on a NXP RT1052 eval board. I am using this with a Segger Embedded Studio. I have build one of the demo applications (Hello) and tried to flash it into QSPI memory on this board This board has a 1V8 QSPI 8MB device on it (IS25WP064AJBLE). I have changed the jumper at SW7 to boot from this QSPI device Once I have plugged in the JLink device on to this board I see the right 2 green leds illuminated When I disconnect the power I see the LED on right go out. When I …
-
I am trying to get a build for the NXP eval board with a RT1052 processor on it. I am using In thumb_crt0 there are some undefined variables, I think they would be define in ld script - __data_load_start__ // I think this should be __data_run_load_start__ - __data_start__ - __data_end__ - __text_load_start // I think this should be __text_run_load_start__ - __text_start__ - __text_end__ - __fast_load_start__ // I think this should be __fast_run_load_start__ - __fast_start__ - __fast_end__ - __ct…
-
Is there support for the NXP RT105x processors