update firmware fail with piTest -f

Topics about the Hardware of Revolution Pi
Post Reply
imerledragon
Posts: 18
Joined: 30 Sep 2021, 02:39

update firmware fail with piTest -f

Post by imerledragon »

Hello Kunbus!

I have reset a Core 3+ by flashing it with the buster lite image available in the download area.
After setting a MIO in piCtory, saved and reset the driver, I am trying to update the firmware but all I get is "update firmware fail".

Here is the dmsg:

Code: Select all

[  736.865214] piControl: update 1 addr 31 ret 0
[  736.985073] piControl: start data exchange
[  737.225092] piControl: MIO Initializing...(devno:1, addr:31, conf-base:61)
[  737.225109] piControl: search mio conf(index:0, addr:31)
[  737.228258] piControl: headers of mio:aio conf request: 0x351f, response:0x209f
[  737.231185] piControl: headers of mio:aio_i conf request: 0x931f, response:0x809f
[  737.234111] piControl: headers of mio:aio_o conf request: 0x931f, response:0x809f
[  737.234117] piControl: MIO Initializing finished(devno:1, addr:31)
[  742.485256] piControl: stop data exchange
[  742.485595] piControl: piIoComm_gotoGateProtocol returned 0
[  742.555203] piControl:error: cannot open file /lib/firmware/revpi/fw_00095_001.fwu
[  742.555244] piControl: update 0 addr 0 ret -2
[  742.555279] piControl: firmware file length: 49472
[  742.555349] piControl: firmware is up to date: 1.0 >= 1.0
[  742.555359] piControl: update firmware fail
[  742.555363] piControl: update 1 addr 31 ret 0
[  742.675221] piControl: start data exchange
[  742.915213] piControl: MIO Initializing...(devno:1, addr:31, conf-base:61)
[  742.915227] piControl: search mio conf(index:0, addr:31)
[  742.918366] piControl: headers of mio:aio conf request: 0x351f, response:0x209f
[  742.921266] piControl: headers of mio:aio_i conf request: 0x931f, response:0x809f
[  742.924166] piControl: headers of mio:aio_o conf request: 0x931f, response:0x809f
[  742.924172] piControl: MIO Initializing finished(devno:1, addr:31)

It sounds like the error is related to a missing file
piControl:error: cannot open file /lib/firmware/revpi/fw_00095_001.fwu
This is the content of the revpi firmware directory:

Code: Select all

pi@RevPi57128:/lib/firmware/revpi $ ls
fw_00071_001.fwu  fw_00075_001.fwu  fw_00081_001.fwu  fw_00093_001.fwu  fw_00098_001.fwu  fw_00118_001.fwu
fw_00073_001.fwu  fw_00077_001.fwu  fw_00082_001.fwu  fw_00096_001.fwu  fw_00100_001.fwu
fw_00074_001.fwu  fw_00079_001.fwu  fw_00092_001.fwu  fw_00097_001.fwu  fw_00103_001.fw

The updater is already the latest version. I tried to uninstall, reboot, reinstall, reboot.

Code: Select all

pi@RevPi57128:/lib/firmware/revpi $ sudo apt install revpi-firmware
Reading package lists... Done
Building dependency tree       
Reading state information... Done
revpi-firmware is already the newest version (1:1.6).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The module is configured and present:

Code: Select all

pi@RevPi57128:/lib/firmware/revpi $ piTest -d
Found 2 devices:

Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present
     input offset: 117 length: 6
    output offset: 123 length: 5

Address: 31 module type: 118 (0x76) RevPi MIO V1.0
Module is present
     input offset: 0 length: 34
    output offset: 34 length: 27

At this point, I don't know what I am missing and what should be done next.
What has been done on the Core: flashing, update+upgrade (with apt), configuring the module in piCtory, then trying to update the firmware of the module.

Serial console is not enabled (I have checked, it was not after flashing the RevPi). The kern.log is attached to the message.

How can I get the missing file to get it work?

Thank you very much,
Torpi
Attachments
kern.log.zip
(46.36 KiB) Downloaded 293 times
User avatar
nicolaiB
KUNBUS
Posts: 931
Joined: 21 Jun 2018, 10:33
Location: Berlin
Contact:

Re: update firmware fail with piTest -f

Post by nicolaiB »

Hi,

Everything is fine with your system. The latest firmware for the Mio is version 1.0. The error message is a known "error" as the driver tries to find a firmware file for the base device (95 is core), which doesn't exist as the device is running an embedded firmware. This is not a real error and therefore can be ignored safely. We already have a task in our backlog for suppressing this error.

Nicolai
imerledragon
Posts: 18
Joined: 30 Sep 2021, 02:39

Re: update firmware fail with piTest -f

Post by imerledragon »

Thank you very much for your answer Nicolai!

Have a great day,
Torpi
Post Reply