boot: flash-resident bootloader
peripherals: uart
IDE: MCUXpresso IDE
SDK Version: SDK_2_8_0_TWR-KV58F220M.zip
boot example: twrkv58f220m_tower_bootloader
Application example:twrkv58f220m_led_demo_tower_a000
Tool: KinetisFlashTool.exe
after update, four led blinks one by one, everything was all right. But when i add some other resource (for example SPI), application was stop in the DefaultISR. What's the reason? why application cannot enter into the right ISR?
Kind regards,
Roger
Hi Roger,
There are several SPI examples in SDK_2_8_0_TWR-KV58F220M. Do you have reference to its peripheral initialization code and interrupt settings?
You can upload a simple test project so that I can quickly analyze the cause of the problem.
Best Regards,
Robin
Hi,Robin
I think i have find the bug. It's the startup file problem.
the example twrkv58f220m_led_demo_tower_a000 use "startup_MKV58F24.S".
and normal example use "startup_mkv58f24.c".
the SDK support two different example based on "KSDK driver" or "transactional API".
the difference is "KSDK driver" use SPI0_IRQHandler directly, "transactional API" use SPI0_DriverIRQHandler which not define in "startup_MKV58F24.S".
I hope NXP engineer can fix this bug. I waste nearly one week time on this problem, hope these can help other NXP users. Thank you!
Best Regards,
Roger
Hi, Robin
Thanks for your reply. I use "dspi_interrupt_b2b_transfer_master" from SPI examples in SDK_2_8_0_TWR-KV58F220M. And the test projects are attached.
I also search some relate topic,
https://community.nxp.com/t5/S32K/s32k148-bootloader-to-app-can-t-work-interrupt/m-p/1165845
unfortunately don't get the right answer.
Best Regards,
Roger