Forum Discussion
Hi Dan,
sorry for late response to your previous post, I was on vacation.
A remote update design is comprised of these functions
- Remote Update FPGA IP, controlling boot of different configuration images, e.g. factory/application
- Flash programming IP, e.g. ASMI Parallel IP
- Remote update state machine in user logic
- Flash interface wrapper translating your transfer protocol and data format to flash IP interface
- Interface logic, e.g. UART, I2C, SPI or user specfic
Beside Remote Update and Flash IP, that can be imported from IP catalog, functions 3 - 5 have to be written by yourself or copied from design examples.
I don't see much use of Simulink for Test of remote update. First step is to decide about used communication interface and protocols.
We started 10 years ago with a RSU design that puts high level functions in the FPGA like decoding .hex files and CRC check of programmed flash image. Finally we stepped back to a lower level protocol transferring binary flash data and verifying it externally.
If you have more specific questions, we can hopefully help you.
Best regards
Frank