Jump to content
OMRON Forums

Trouble saving my code to flash


Recommended Posts

I am struggling to save my code to flash memory. Here are the steps I am taking:


From the terminal: "$$$***" to reset to factory defaults

Right-click on PPCNC_ProjectSource in the Solution Explorer and select "Build and Download All Programs"

From the terminal: "save" to save to flash


The results seem to indicate the save worked:


Successful: SaveConfiguration using /var/ftp/usrflash/Project/Configuration/pp_save.cfg


Successful: SaveCustomConfiguration using template /var/ftp/usrflash/Project/Configuration/pp_custom_save.tpl


SaveToFlash: Do NOT Power off until Finished!!!


availabe_space = 290912K 2524K

required_space = 2524K

SaveToFlash: cp


SaveToFlash: sync()


SaveToFlash: mount


SaveToFlash: Finish SAVING to Flash.


Save Complete


However if I reboot the machine my code is not loaded. Also if I factory reset and then normal reset ($$$*** then $$$) my code is not reloaded.


Can anyone point out what I am doing wrong? I thought this was the exact procedure I followed on my other PowerBrick and it seemed to work there.

Link to comment
Share on other sites

  • Replies 5
  • Created
  • Last Reply

Top Posters In This Topic

  • 2 weeks later...

Yes and no.


When you update the firmware via the IDE, it does instruct you to do that afterwards. Basically, after a firmware update, the PMAC may not run its script to auto-detect hardware. Because of this, it may believe you have hardware , when in reality, you are using hardware . When you then do a build and download and save, it actually does complete successfully, however when you power cycle, PMAC will compare what it believes you have with what is actually present, detect that they are different, and for safety reasons, it will factory reset itself. Manually issuing $$$*** forces PMAC to run this script, and then issuing the save command afterwards updates PMAC such that it saves the knowledge of what hardware was detected.


That said, I am not completely aware of the exact details why the user must issue these commands compared to the auto-detect being run or us just automatically issuing these commands after a firmware update.


If you have not updated your firmware recently, please email support at deltatau dot com referencing this thread, because I would be curious if something else might cause this condition--to my knowledge, every time I've seen it was after a recent firmware update.

Link to comment
Share on other sites

  • 2 months later...
This topic is now closed to further replies.

  • Create New...