Hello - My issue is that using the Flash2808_API_V302.lib from RAM is producing Flash Erase issues - either it hangs or it jumps to the Flash_APIVersionHex() location.
Since the native bootloader only writes the uploaded hex file into RAM, I need to develop a flash bootloader to run from RAM so it can take the next hex file upload and write it to flash.
I have used as a base the f28335_can_flash_kernel and modified it for the F2808. I can run the new f2808_can_flash_kernel() in CC from ram until I get to the Flash_Erase function. The Flash_APIVersionHex() does return the correct revision.
I have tried both using and not using the following: #pragma CODE_SECTION(<functions>, ".TI.ramfunc");
I am using the 2808_RAM_lnk.cmd and I tried using different RAM areas for "ramfuncs : > RAML1 PAGE = 0"
My goal is so that production can ground GPIO18, have the F2808 come up in bootloader mode, load the f2808_can_flash_kernel.hex file to setup the F2808 to be able to write to Flash. Then after the f2808_can_flash_kernel.hex upload, the operational_code.hex will upload and burn to flash.
Any thoughts what is preventing Flash_Erase from completing?
