We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on
Cloud Connected vs On-Premise Services. Your feedback can
help us shape the future of services. Learn more about the survey
or
Click here to Launch the survey Schneider Electric Services Innovation Team!
Modicon M580 - Integrity Verification of firmware files similar to EcoStruxure Control Expert
Modicon Ideas & new features
Have ideas on how to improve Modicon? Please share and get votes from Community to influence development efforts.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
We should release firmware file's checksum list or hash, so that customer could check the firmware file integrity before loading it into their CPU, Communication Modules etc. at least for Modicon M580.
firmware signing, and trust (likely through a standard certificate / CA system), this would prevent the bootloader/firmware loader from writing an untrusted firmware to the end device
checksum for user confirmation before/after shipping firmwares around, to avoid wasted time/effort in moving around corrupt firmware files.
For some safety systems I've even seen a second step of the firmware loading. Where the end device does a checksum run across the 'as deployed' image, and presents this to the user for confirmation before going into operation. Having such a step does make automated firmware deployments problematic however..