Yes, simply customize the BL to read those areas of EE and FLASH and
com them out.
http://www.cypress.com/?rID=56014 PSoC® 3, PSoC 4, and PSoC 5LP Introduction To Bootloaders
http://www.cypress.com/?rID=83293 AN86526 - PSoC® 4 I2C Bootloader
http://www.cypress.com/?rID=50230 AN68272 - PSoC® 3, PSoC 4 and PSoC 5LP UART Bootloader
But isn't modifying the generated API a bad thing? It's going to be overwritten if a regenerate the project right?
From the ap notes I poisted -
So what you're saying is that I should add my eeprom read and whatnot before the CyBtlrStart (which is a blocking function and doesn't allow us to do any other) and that I need to re-implement usb commands and whatnot?
What would be best would be to simply add a new command code in the bootloading mode with the correct format (stop bits, command, length of data, data, checksum and end bits) and adding a case for that.
I don't think the state machine with the timed interrupt would be a good thing as we could be transferring at the same time. Unless I got what you said wrong.
1 of 1 people found this helpful
I have not done a custom BL, but looking thru files I do not see
any banner areas for user code. So I think its correct, that user
non BL related capability is implemented before the start.
To confirm this, consider posting a CASE and point to this thread.
You might point out to Cypress that should be clear in ap note(s).
To create a technical or issue case at Cypress -
“Create a Case”
You have to be registered on Cypress web site first.