> I did flash the AXFS rootfs with the following CommanderScript as well but it did not seem to help:
But, when you called the script, did you start JLinkExe with
-device R7S721001
or
-device R7S721001_DualSPI
Since your JLink is connected to Linux, you could also try using "./build.sh jlink" which only uses single QSPI (-device R7S721001) at the moment, so that would be fine for you.
./build.sh jlink output/linux-3.14/arch/arm/boot/xipImage 0x18200000
./build.sh jlink output/axfs/rootfs.axfs.bin 0x18800000
Also, make sure you are using a relativity new version of J-Link. There was an update (at the beginning of the year?) to fix that Jlink would not program correctly past a 16MB address for single SPI (32MB for dual SPI)
> After reflashing it, it successfully boots Linux up until a certain point and then hangs.
That part doesn't make any sense why it would just stop there (unless part of your kernel didn't program correctly).
Maybe after you flash it, you could use md 0x######## in u-boot and just make sure it programmed all the way to the end.
If your kernel started at 0x18200000, and your rootfs started at 0x18800000, that's 6MB of space for your kernel. How big is your kernel? If it is bigger than 6MB, then when you program in your rootfs after the kernel, the rootfs will erase and overright the end of your kernel binary.