Hi Omar,
Thanks for the reply.
I have one follow-up question regarding to the entry data of the ivt region.
I encountered a weird issue after using the HAB signed boot.
The tool I used was the NXP-MCUBootUtility (https://github.com/JayHeng/NXP-MCUBootUtility).
For trial, I used some small applications like led-blinky and it worked well.
After deploy my own application(around 350KB code size), the MCU would hang or crash when executing a certain function.
After comparing the binary file built from McuXpresso and the signed binary generated by the NXP-MCUBootUtility, the entry data of ivt is different.
The entry data of ivt for binary built by McuXpresso is 0x60002000

The entry data of ivt for binary built by NXP-MCUBootUtility is 0x60002305

After manually modify the ivt entry data generated by NXP-MCUBootUtility to 0x60002000 and sign it again, the code works well without crash or hang.
So I am quite confused about the entry data of the ivt region.
Some articles in the forum suggested that the value that NXP-MCUBootUtility generated was correct but some application note from NxP said that it should be 0x60002000.
I would asume that if this value was wrong, the whole application should not be working, not only a certain function.
But for my case, 0x60002000 works not the 0x60002305.