@rshipman
I'm not sure if I ever tried the blinky demo. I was using the SAI demo, so you might want to see if that works for you.
I was just going over my notes and it looks like I could use the LinkServer and access SDRAM without problems. Hopefully the demo will for you too. That was slow, but when I got that jlinkScript, I could run it with JTAG and that was a lot faster.
Later when we were trying to do more with the board, we ran into other related issues with using flash and SDRAM at the same time. We're on the 1050 board right now and it seems to have similar issues..... still working through it. Here is my coworkers notes on the subject for the 1020 board. Hope this helps :
`evkmimxrt1020_sdram_init.jlinkscript` is a jlink script file that NXP provides in their demo projects for their MIMXRT1020EVK dev board that scripts the JLink debugger to configure the sdram prior to downloading code into the sdram.
This is problematic for a couple reasons:
1) It seems to interfere with operation of the spi flash. The spi flash doesn't seem to work after this script executes. It seems that NXP thinks you'll use the spi flash and sdram mutually exclusively.
2) The iMXRT1020 boot rom is supposed to configure the sdram via the DCD if it exists. However, the debugger seems to skip this part. Possibly the reason NXP provides the script in the 1st place. Thus, the sdram is not guaranteed to be configured the same whether booting from rom or debugger.
The above issues have been addressed in the code by copying a small section of startup code/data to internal ram, executing from internal ram to configure the sdram (among other things), and then proceeding with normal code/data ram loading and execution. Thus, the jlink script file should no longer be necessary.