Forum Discussion
BFair2
New Contributor
7 years agoYou didn't understand either of my questions so I'll attempt to explain better.
- In the Remote Update Intel FPGA IP UserGuide v18.0 on page 26 there is an asynchronous reset input that needs to be driven. The document states, "Asynchronous reset input to the IP core to initialize themachine to a valid state. The machine must be reset before first use, otherwise the state is not guaranteed to be valid." I can apply reset in the factory image on startup and not apply reset in the application image. My question is if due to a reconfig I leave the application image and go back to the factory image, do I have to be concerned about applying reset at startup the 2nd time in the factory image?
- Your answer was what occurs if there is a CRC not a logic error. Assume I have application code that triggers the watchdog timer properly and loads correctly but it is either the wrong code or I accidentally messed up the logic that detects a reconfig and will never go back to the factory image. It seems like you could brick the unit. My question is to prevent that, is it important to build a mechanism into the factory image whereby it checks a flag to see if it should load the application image rather than just blindly loading it. That way even if the application image has a logic error that prevents a reconfig, you could set a flag, recycle power, and the factory image would not load the application image and could perform another update of the application image. This would prevent bricking the unit. Does that make sense?