Boot Problem bei RevPi Connect - "Cannot open file fixup.dat"

Hm, no new device found ...

I stumbled over the lines with " libusb: error [udev_hotplug_event] ignoring udev action bind". Is the RevPi connected via any USB hub? A quick internet search found similar problems caused by usb hubs.

Nicolai

No, the RevPi was directly connected to the Notebooks or RaspberryPi 3.

Here the log when I try it from a RaspberryPi 3:

deviceadmin@HMI003:~/rpiboot/usbboot $ sudo ./rpiboot -v
[sudo] password for deviceadmin:
RPIBOOT: build-date Apr 21 2022 version 20220315~121405 445356e1
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 52456 bytes
libusb_bulk_transfer sent 52456 bytes; returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin
Device located successfully
Failed to open the requested device
Loading embedded: bootcode.bin
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file config.txt
Received message GetFileSize: recovery.elf
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file recovery.elf
Received message GetFileSize: start.elf
Loading embedded: start.elf
File size = 523192 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer sent 523192 bytes; returned 0
Received message GetFileSize: fixup.dat
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file fixup.dat
Second stage boot server done

It seems that USB disconnects right after the block device is created. Maybe this is an HW defect, but why 4 devices at the same time?

The RevPis consuming between 1.32 - 1.36W after power on.

Another RevPi which works ok, is always above 2.3W. But the 4 broken ones are 8GB devices and the other one is a 32GB device.

LED A3 lights red, regardless if USB cable is plugged in or not.

What do you suggest as next steps?

The RevPi Connect+ consists of 3 circuit boards. Does it make sense to substitute one board after the other to find the problem? If yes, with which board should I start to prevent demaging other components?

Hi,

I'll check with my colleagues from the hardware, if they might have an idea what else can be tested / can be the cause.

Could you please send me the following details about the 4 broken devices to support@kunbus.com (subject: SUP-4800 Cannot open file fixup.dat):

• serial (second line, next to data matrix code)
• revision (below serial)
• date of purchase / purchased where

Nicolai