board/lm3s6965-ek: restore 128K kflash

[yf13]

Summary

This reverts both 2afdcfb and 0a0af89 to restore the 128K kflash design as the implementation depends on that to work, checked with:

$ qemu-system-arm -M lm3s6965evb -nographic -device loader,file=nuttx.bin,addr=0x0 -device loader,file=nuttx_user.bin,addr=0x20000

Thanks to patch 12873, 128K uflash is enough now for qemu-protected.

Impact

lm3s6965-ek device

Testing

• local check with lm3s6965-ek:qemu-protected
• CI checks

[yf13]

@masayuki2009, this is to restore 128K kflash for lm3s6965-ek device.

[masayuki2009]

See #12876

[masayuki2009]

@yf13

Hmm, I encountered the following error.

$ /home/ishikawa/opensource/QEMU/qemu-9.0.0/build/qemu-system-arm -M lm3s6965evb -nographic -device loader,file=./nuttx.bin,addr=0x0 -device loader,file=./nuttx_user.bin,addr=0x2000
qemu-system-arm: Some ROM regions are overlapping
These ROM regions might have been loaded by direct user request or by default.
They could be BIOS/firmware images, a guest kernel, initrd or some other file loaded into guest memory.
Check whether you intended to load all this guest code, and whether it has been built to load to the correct addresses.

The following two regions overlap (in the cpu-memory-0 address space):
  ./nuttx.bin (addresses 0x0000000000000000 - 0x000000000000e6f4)
  ./nuttx_user.bin (addresses 0x0000000000002000 - 0x00000000000101dc)

[yf13]

@masayuki2009, please retry with addr=0x20000, I am sorry the address in commit message missed a 0 when copying.

Here is my session log:

$ qemu-system-arm -M lm3s6965evb -nographic -device  loader,file=nuttx.bin,addr=0 -device loader,file=nuttx_user.bin,addr=0x20000
Timer with period zero, disabling
ABCDEF
telnetd [3:100]

NuttShell (NSH) NuttX-12.4.0
nsh>