When updating a KFlop, must the version of the KMotion software match the version of firmware currently in the KFlop when updating to newer firmware? Realizing that the firmware coff file is specific in each installation of the KMotion software, for example:
If updating a KFlop that currently contains firmware shipped with KMotion 4.3, must the KMotion 4.3 be used to update to Firmware 5.3 (assuming you point it to the correct new firmware file)?
or
Can KMotion 5.3 be used to update the KFlop that currently is loaded with 4.3 to bring it up to 5.3 firmware?
KMotion versions vs. Firmware versions
Moderators: TomKerekes, dynomotion
Re: KMotion versions vs. Firmware versions
AFAIK the KMotion install, will always come packaged with the current firmware for that version of KMotion.
And any version of KMotion (or at least any version compatible with whatever board that you are using) can flash any version of compatible firmware to the board.
So in short, you can use 5.3.1 to update a KFlop that contains an older version.
And any version of KMotion (or at least any version compatible with whatever board that you are using) can flash any version of compatible firmware to the board.
So in short, you can use 5.3.1 to update a KFlop that contains an older version.
-
- Posts: 85
- Joined: Fri Apr 27, 2018 12:44 pm
Re: KMotion versions vs. Firmware versions
Understood, which is what I would have thought.
I was unable to use a newest 5.3 KMotion to apply it's included firmware to a previous versioned 4.3 firmware KFlop.
I was able to use the previous version of 4.3 KMotion to flash the newer 5.3 firmware to the KFlop with the older 4.3 version already on it.
I was unable to use a newest 5.3 KMotion to apply it's included firmware to a previous versioned 4.3 firmware KFlop.
I was able to use the previous version of 4.3 KMotion to flash the newer 5.3 firmware to the KFlop with the older 4.3 version already on it.
-
- Posts: 85
- Joined: Fri Apr 27, 2018 12:44 pm
Re: KMotion versions vs. Firmware versions
Just to close up this thread, it sounds like this is indeed an issue. Tom is aware of it (See Issue #1 in this forum thread):
viewtopic.php?f=12&t=1708&e=1&view=unread#p6929
viewtopic.php?f=12&t=1708&e=1&view=unread#p6929