Questions
is it possible to send firmware without a project file?
I recently ran into a scenario where I could not update the firmware on a module because my project file was IQAN 7.06 and the module was 7.04. The Module needed to be updated to 7.05 before it could be updated to 7.06.
This has never been an issue for me in the past. Usually the latest firmware would always load without having to load the intermediate firmwares. I simply created a blank project with the masters in the system at 7.05 and loaded it to 7.05, then loaded the project to 7.06. However this problem becomes much more difficult when issuing program changes to the field. I never released software to the field with 7.05, so the service technicians won't be able to update a system in this scenario.
I looked around in IQANRun and I didn't see any way to update the modules without a project file. Is there any way this can be done?
Customer support service by UserEcho
I dont believe so.
I usually do the same as you, create a blank project with nothing inside, no inputs, outputs or logic etc just a module with the correct address. This will send the firmware and get it updated the the required 7.05. Then its ready for the 7.06 application.
Best bet is to take your 7.04 application, open in 7.05 and save it as an 'intermediate' update, then load in the final 7.06 application file. Get the technicians to load in the intermediate update first then the final 7.06 file using IQAN Run. It means 2 separate updates which consumes a bit of time.
If you have no need to run 7.06, maybe implement the changes into 7.05 instead, then you wont have to worry about the intermediate step.
While your approach makes sense, and that's essentially what I did on the prototype, it's much harder to do in the field. The field service technicians do not have access to IQANDesign and I can't send unreleased code to the field. I'd have to have a separate release and a work instruction to load a shell project of 7.05 before loading the released 7.06.
Fortunately I believe this only applies to the MD5 which we are not widely using yet.
I likely glossed over this in the 7.06 release notes since these displays are not even in prototyping phase for us yet.
Maybe this question should be flipped to a feature request where IQANRun can upgrade firmware without a project file to avoid this situation entirely.
With the looming release of IQAN8, I fear that we will see the same issues when upgrading from 7 to 8. Given that we will be chasing compliance with the Cyber Resilience Act in the EU, we will likely need to update all projects to IQAN8.
Is there a need to update the system to version 7.06? Could you keep your project at 7.04 to avoid the problem altogether? Note that once a MD5 becomes updated to version 7.06 you cannot downgrade, i believe to do with cybersecurity.
The project does not typically include an MD5 so the upcoming release is not a concern. The MD5 was put into the project as a test for an upcoming prototype.
We upgraded the project to 7.06 in April and it has been under constant development.
I see the dilemma.
Maybe when you introduce your finished application version that includes an MD5 (after your prototyping) the units being manufactured may be pre installed with the newest firmware to save you the pain of updating. This would overcome the issue of updating to 7.05 first if the unit is delivered with 7.06 or later.
The 7.06 update is special and need to have the 7.05 loaded for it to work.
Do also note that you can not use a clone file to update from 7.05 to 7.06 on MD5.
The project file contains a intermediate part that gets downloaded, this is not included in the clone file.
The units that are produce now have the secure boot firmware loaded from factory.
The MD5 started from week 24 and the MC4x started from week 25.
My understanding is that this is a specific problem to the MD5 based on the release notes.
Are the MC4x impacted as well?
Will IQAN 8 have the same issue with upgrading firmware with any module?