- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been programming a CYBLE-416045-02 with PSoC Creator 4.2.
Does the chip verify its program on startup? I've seen similar questions with answers that
say things like the bootloader automatically verifies flash on startup.
However, I am unable to add a bootloader or bootloadable component to the design,
and they don't show up in the components list unless I make a new project for a different chip.
No bootloader component (should be under system)
Does the CYBLE-416045-02 not have a bootloader? If so, how can I get it to verify flash on startup?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the bootloader always verifies the flash.
It's PSoC 63 device mounted inside CYBLE-416045-02 module. The bootloading architecture of PSoC 6 device is different from the one of PSoC 4. DFU middleware is adopted for PSoC 6 device, instead of bootloader/bootloadable component.
To get start with P6 DFU function flow, you may refer to the following AN doc - https://www.cypress.com/file/385706/download, in which how to cerate a bootloader/bootloable project with a target device is introduced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I just want to confirm this:
The DFU verifies the flash on startup.
However, does this mean I have to enable the DFU under build settings, or will it do the verification automatically even if I don't?
If I have to include it, do I need to call functions to check it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for the delay.
Genarelly, the flash would be verified during the firmware programming. Can you let me know the reason you need the verify process?
It looks not worthy to eable DFU functionality just merely for this purpose.