Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
When using a bootloader to update main program from .hex file generated for psoc creator, how is the hardware(UDB) reprogrammed in PSoC 3/5? Sorry if this is a stupid question but where is the information on TRM about hardware programming for Universal Digital Blocks? Thanks
When you make designs in PSoC Creator the configuration is really just data that gets linked into the final downloaded image in flash. When the device boots that data gets copied (usually by DMA) into the digital blocks and routing. In a bootloader situation the same is true - twice. You have a "bootloader" design that is programmed into the device normally (i.e. via MiniProg3) and, when it powers up, it initializes the UDBs. If a bootload is required then the host will send a "bootloadable" design, via I2C, which replaces the original and then resets, which boots up and configures the UDBs just as before. -- mgs