Automatic Mode with production file and command line [Beta]

[ArT]

Some of you asked us about command line interface for REVELPROG-IS. Unfortunately we can not add typical command line interface for read/write/erase operations at the moment. REVELPROG-IS is GUI based application and some functions requires windows forms to operate, so it will needs rewrite most of the code from scratch. REVELPROG-IS is developed since 2013, it had a lot of updates with supported new chips and new features. I hope that you will understand that rewriting whole code from scratch is not the solution - not at the moment. Maybe in future, step by step. REVELPROG-IS will be still improved and there will be still new updates in future. One of the improvement we are thinking is Automatic Mode Tool.

We have prepared beta version of automatic mode tool which supports production files.

Here is example movie how it works:
https://youtu.be/69MQlU2r9k0

In production file you can currently provide:

• device name
• voltage
• operation type (READ or WRITE or ERASE)
• file path (for write operation or for read operation)
• pre-script and post-script paths (for custom script tool)

It's still GUI based, but we hope that it can save your time and improve your production routine. You can also start REVELPROG-IS application from command line with -productionFile "path.txt" parameter, so it will run and load production file on start-up.

automatic-mode-log.jpg (81.89 KiB) Viewed 229291 times

automatic-mode-beta.jpg (160.24 KiB) Viewed 229291 times

It's still not official version. If you would like to test automatic mode please contact me via PM or via REVELTRONICS contact page, I'll share you beta version for test. At the moment it supports only write operation with pre-script and post-script execution. We will be making next improvements and adding new features if it will be demand on such tool. Beta version of this tool will be shared in v1.9.0 update. Hope you will like it. Please tell me what you think and share your requests here.

[ArT]

The automatic mode in version 1.9.2 includes several improvements.

When you enter device=93c66, the memory database will locate both the 93..66 (8-bit) and 93..66 (16-bit) variants. By default, automatic mode will typically select the first option (8-bit). To specifically select the 16-bit version, please provide a more precise name, such as IS93C66B which is always 16-bit variant. The same situation may be for other device types.

We recommend using the memory selection window to limit the results to a single choice and then use this signature for automatic mode script.

[KALLE]

Question about ongoing development / feature request (Automation & Scripts)

Hello,

I wanted to ask whether there is still active development planned in this area, or if further improvements to the automation features are being considered.

I am using REVELPROG-IS regularly and would really welcome a bit more flexibility in the Automatic Mode / Custom Script workflow, especially for reliability-critical flash operations.

Target workflow (conceptual)

1. []Read #1 → file (e.g. Backup_$v1_1.bin)
   []Read #2 → file (e.g. Backup_$v1_2.bin)
   []Run external script (e.g. PowerShell):
   • []Compare both reads (CRC / hash)
     []Return exit code
   []Only if comparison is OK:
   • []Run another external script that modifies the image
     []Script creates a new binary file
   []Write modified file to flash
   []Optional: read back and verify

Current limitations
While the Custom Script tool is very powerful for low-level SPI/I²C operations, it currently lacks:

• []Conditional logic (if / else)
  []Ability to evaluate return codes from external scripts
  []Tight integration with external tools in a controlled workflow
  []Flexible buffer/file handling using variables

Features that would be extremely helpful

• []Support for command-line variables, for example:
  -productionFile ABC.txt -v1 "Camera1"
  []Use of those variables inside production files and paths
  (e.g. Backup_$v1_1.bin)
  []Ability to execute external scripts synchronously and evaluate their exit codes
  []Basic control flow inside production files, e.g.:

Code: Select all

Read -> file
Read -> file
RunScript compare.ps1
if (errorlevel == 0) {
RunScript modify.ps1
Write modified.bin
} else {
Abort
}

This would significantly improve REVELPROG-IS for automated and safe flash workflows, where data integrity is more important than raw speed.

I would be very interested to know:

• []whether this area is still actively worked on
  []or if such extensions are technically feasible in the future

Thank you for the tool and the work done so far — this feedback is meant as a constructive request based on practical use cases.

Best regards

[ArT]

thank you very much for your detailed suggestion and for sharing your practical workflow. I really appreciate the time and thought you put into this feedback. At the moment, we are not actively working on extending this specific functionality. We had plans to introduce more advanced command-line based automation, but this would require a significant redesign of major parts of the application, and unfortunately we do not currently have the resources to proceed with this work.

If the situation changes in the future and we are able to move forward with such enhancements, I will make sure to come back to this topic and provide an update here.