- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solved! Go to Solution.
- Labels:
-
PSoC4 MCU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For anyone who is reading this thread, the answer was that the internal flash memory we were using to store data was not the USER FLASH, but SFLASH and we were crushing our boot loader data, causing the bootloader to keep triggering. It worked on the first program, because we had not written to flash yet in the main program.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Did you check 'BLE_OTA_FixedStack_Bootloadable' and 'BLE_OTA_FixedStack_Bootloader' code example projects from the PSoC Creator ? Please let me know your observations on this example project.
BondMgmt.h file is missing in the project. Could you please share this file.
Thanks,
P Yugandhar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
P Yugandhar, thank you for your reply, we based the project on that example and have used it on four different projects successfully, but cannot get this one to work.
You say bond management is missing the project, in the bootloader, or bootloadable?
Thanks for the support, we are super stuck here and need to solve this asap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Adding back in BondMgmt.h had no effect.
We need to resolve this, who can tell us why the code is stuck in the bootloader and how to fix it?
BTW, I cited the wrong file in the original posting, we are stuck on line 121 of the file boot_loader.c in the generated source and we do not understand why the target is wrong, it is pointing at the bootloader 0x80, not the bootloadable 0x40. Where is this set?
#define Bootloader_SCHEDULE_BTLDB (0x80u)
#define Bootloader_SCHEDULE_BTLDR (0x40u)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For anyone who is reading this thread, the answer was that the internal flash memory we were using to store data was not the USER FLASH, but SFLASH and we were crushing our boot loader data, causing the bootloader to keep triggering. It worked on the first program, because we had not written to flash yet in the main program.