If I understand the documentation and programming files, the processor code has to be updated anytime the OSD is changed significantly. We take the resource files c and h file generated upon the blimp OSD compile and use that because those contain the memory entry point. Please correct me if I am wrong.
I was trying to use the existing the blackfin processor code with/on the EVAL ADV8003 module and create a new OSD image but upon programming the OSD only and rebooting, it will not load. I assume because of what I stated earlier. Is there anyway to force these memory entry points into the Blimp tool where the processor code never needs to be updated?