EFFS-AppUpdate example
Posted: Wed Aug 14, 2013 1:51 pm
FYI for everyone,
The EFFS-AppUpdate example does not work for the Nano54415, and it looks like it wouldn't work for the MOD54415 either. Note that in the supplied example under EFFS->EFFS-AppUpdate, the fileup.cpp file has a flash base address definition. This definition needs to be changed for either of the 54415 platforms (see the memory maps in the docs/Platform folder).
Also note that for the Nano, if you want the flash to not update if the .s19 file has the same code as what is already installed, further modifications to the file will be necessary because the code does a memcmp comparison of flash with RAM to compare the compressed applications. This does not work on the Nano because it has SPI flash. I would expect it to work on the MOD54415 platform, though.
Hopefully, Netburner will modify this file so that it will more easily support all of their modules.
The EFFS-AppUpdate example does not work for the Nano54415, and it looks like it wouldn't work for the MOD54415 either. Note that in the supplied example under EFFS->EFFS-AppUpdate, the fileup.cpp file has a flash base address definition. This definition needs to be changed for either of the 54415 platforms (see the memory maps in the docs/Platform folder).
Also note that for the Nano, if you want the flash to not update if the .s19 file has the same code as what is already installed, further modifications to the file will be necessary because the code does a memcmp comparison of flash with RAM to compare the compressed applications. This does not work on the Nano because it has SPI flash. I would expect it to work on the MOD54415 platform, though.
Hopefully, Netburner will modify this file so that it will more easily support all of their modules.