PEmicro Blog

PEcloud: The Magic of SAPOBJ

PEmicro Cyclone programmers are sophisticated production programming tools that are designed to operate in StandAlone mode.  PEmicro’s Image Creation Utility generates these StandAlone programming images. They might combine an algorithm, binaries, and a programming script which could include  erase, program and verify of their binaries, as well as more complicated scripts along with other features like serial numbers, dynamic data, or running test commands and saving data for programming.  

Users often save a configuration file (.CFG) so they can later regenerate a new SAP image from the same configuration and reference files.  However, if any of the files have changed or been lost, like the binary file or the serial file, then it is not possible to recreate and image the programs with exactly the same data. The latest version of Image Creation Utility addresses this by adding the ability to build a SAP object file (.SAPOBJ).

In Image Creation utility, by simply checking the ‘Build to SAPOBJ only’ checkbox,  a non-executable SAPOBJ object will be created that rolls up everything needed for the programming image, including the programming script, programming settings, algorithm, power and communications settings, binary file all into one place. Since all the original information is saved into one file,  if the user wants to start another production run and have the exact same programming data as a previous production, they can simply use the SAPOBJ to create an identical one.  It eliminates any issues if any of these original files are moved, deleted, or overwritten. They will load the desired SAPOBJ file, run the new Utility called the Deployment manager, add the desired restrictions and encryption and deploy a SAP image or programming job from it.


SAPOBJ In The Creation and Deployment Workflow

The latest version of Image Creation Utility adds the ability to build a SAP object file (.SAPOBJ) by simply checking the ‘Build to SAPOBJ only’ checkbox. A SAPOBJ is a non-executable object that rolls up everything needed for the programming image, including the programming script, programming settings, algorithm, power and communications settings, binary file all into one place. Since all the original information is saved into one file,  if the user wants to start another production run and have the exact same programming data as a previous production, they can simply use the SAPOBJ to create an identical one.  It eliminates any issues if any of these original files are moved, deleted, or overwritten. They will load the desired SAPOBJ file, run the new Utility called the Deployment manager, add the desired restrictions and encryption and deploy a SAP image or programming job from it.

So the user can either go right from the Image Creation Utility to the deployment manager and build a SAP Image or a cloud-connected Job, or they can build and archive a SAPOBJ. The biggest difference between saving a SAPOBJ and a configuration file is that a CFG file only saves the settings, but not the binary data itself. A SAPOBJ goes a step further to create an archived object that includes the device selection, algorithm, binaries, script and other dynamic data, as well as power and communication settings, but does not include image restrictions, encryption key file, or any PEcloud log settings.

As a final summary, a SAPOBJ: 

  • Is not an executable
  • Is not encrypted
  • Has no Restrictions like date and programming attempts

It is extremely useful to create an archive object that can later be loaded and turned into either a SAP image or a cloud-connected Job for PEcloud by using the Deploy Manager to add restrictions and an encryption key. 


Tags related to this Blog Post

Cyclone     Cyclone FX     ARM     NXP     Production Programming