Hello @jeremyzhou
Thank you. We are happy with using mcubootutility as it work for us.
First Issue
We have a customized board. We don't use flexspi. We are able to verify our board with mcubootutility SEMC NAND. We used one of the example files from mcubootutility folder (led_blinky_0x00002000.srec) to verify the SEMC NAND.
Now, when we compile and generate a .hex/.s19 from mcuxpresso and try to use in mcubootutility it doesn't work.
Second issue
We also use Jtag to debug. We are unable to debug with jtag. We don't have a flexspi flash so processor always halt at 0x221304. We can communicate and even try to load using jtag but unfortunately nothing work. Jay Heng explained why this happen but we are looking for a solution.
Segger Ozone
We tried to use segger Ozone to debug from Jtag. We used our .hex or .hex examples from mcubootutility folder. As excepted we get the same 0x221304 problem.
We tried to change linker and memory configuration but it doesn't work.
Important
File name led_blinky_0x0000a000.hex is attached. This file we got from mcubootutility folder (apps).
This is the only file that worked with Segger Ozone.
Please can you provide me with the configurations used to generate this file so we can use in our program ?
Thanks,
TM