VLI firmware v2.0 - powersaving features enabled

[trejan]

How to prevent VL805 from updating ?

Edit /etc/default/rpi-eeprom-update and add ENABLE_VL805_UPDATES=0

Other option is to disable ASPM in the USB controller using the setpci command mentioned by iEvgeny. You'll need to run it every boot though.

[jdb]

For people experiencing webcam issues, what happens if you use the 0137ab firmware and run the following commands?

Code: Select all

sudo apt install pciutils
sudo setpci -s 01:00.0 0xd4.B=0x40

This disables PCIe link power management on the VLI chip.

[Serveurperso]

For people experiencing webcam issues, what happens if you use the 0137ab firmware and run the following commands?

Code: Select all

sudo apt install pciutils
sudo setpci -s 01:00.0 0xd4.B=0x40

This disables PCIe link power management on the VLI chip.

Hi,

I returned to stock updated image and the last VL805 eeprom to check your command :
Do not work for me sorry:( same problem : video capture start but the stream look empty. ffmpeg debug trace don't see the problem !

Code: Select all

root@raspberrypi:~# rpi-eeprom-update
BOOTLOADER: up-to-date
CURRENT: Tue 10 Sep 10:41:50 UTC 2019 (1568112110)
 LATEST: Tue 10 Sep 10:41:50 UTC 2019 (1568112110)
VL805: up-to-date
CURRENT: 000137ab
 LATEST: 000137ab
root@raspberrypi:~# apt install pciutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  pciutils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 271 kB of archives.
After this operation, 1,222 kB of additional disk space will be used.
Get:1 http://mirrors.ircam.fr/pub/raspbian/raspbian buster/main armhf pciutils armhf 1:3.5.2-1 [271 kB]
Fetched 271 kB in 0s (603 kB/s)  
Selecting previously unselected package pciutils.
(Reading database ... 46850 files and directories currently installed.)
Preparing to unpack .../pciutils_1%3a3.5.2-1_armhf.deb ...
Unpacking pciutils (1:3.5.2-1) ...
Setting up pciutils (1:3.5.2-1) ...
Processing triggers for man-db (2.8.5-2) ...
root@raspberrypi:~# setpci -s 01:00.0 0xd4.B=0x40
root@raspberrypi:~#

The only way for me now is the rollback :
rpi-eeprom-update -u /lib/firmware/raspberrypi/bootloader/critical/vl805-00013701.bin
And
ENABLE_VL805_UPDATES=0
inside
/etc/default/rpi-eeprom-update
Work perfectly to prevent automatic updates. EDIT : NO:(

[Serveurperso]

How to prevent VL805 from updating ?

Edit /etc/default/rpi-eeprom-update and add ENABLE_VL805_UPDATES=0

Other option is to disable ASPM in the USB controller using the setpci command mentioned by iEvgeny. You'll need to run it every boot though.

There is a problem :
- I run the downgrade cmdline
- Reboot / Downgraded OK
- I do a second reboot
- VL805 is Upgraded ! The ENABLE_VL805_UPDATES=0 do not work.

The only way I found is to disable completly the eeprom upgrade service :

Code: Select all

systemctl disable rpi-eeprom-update

No more update on reboot...

[jdb]

For people experiencing webcam issues, what happens if you use the 0137ab firmware and run the following commands?

Code: Select all

sudo apt install pciutils
sudo setpci -s 01:00.0 0xd4.B=0x40

This disables PCIe link power management on the VLI chip.

Hi,

I returned to stock updated image and the last VL805 eeprom to check your command :
Do not work for me sorry:( same problem : video capture start but the stream look empty. ffmpeg debug trace don't see the problem !

From a basic Raspbian install, what commands to I need to run to replicate your ffmpeg video stream?

[Serveurperso]

From a basic Raspbian install, what commands to I need to run to replicate your ffmpeg video stream?

I remplaced all variable tocken with value inside my cmdline :

Code: Select all

 "CMDDIFFUSION": [
  "/usr/local/vigiclient/processdiffusion",   (it's ffmpeg)
  " -loglevel debug",
  " -f v4l2",
  " -i /dev/video0",
  " -vf hqdn3d=0:0:50:50",                     (same problem without this filter)
  " -pix_fmt yuv420p",
  " -c:v libx264",
  " -preset fast",
  " -tune zerolatency",
  " -profile:v baseline",
  " -b:v 1500000",
  " -maxrate 1500000",
  " -bufsize 1500000",
  " -g 25",
  " -f rawvideo",
  " tcp://127.0.0.1:8000"
 ],
 

implode :

Code: Select all

ffmpeg -loglevel debug -f v4l2 -i /dev/video0 -pix_fmt yuv420p -c:v libx264 -preset fast -tune zerolatency -profile:v baseline -b:v 1500000 -maxrate 1500000 -bufsize 1500000 -g 25 -f rawvideo tcp://127.0.0.1:8000

But if you want exactly the same configuration you need my USB video capture adapter and a raw H264 baseline decoder
The USB Video capture I use have a good hardware deinterlacing filter (like yadif).
I think the problem is the same with any basic USB video capture or webcam and transcode to any other output format ! But if I can help you...

If you want I can give you a root access on this Raspberry PI, there is a brand new ready to stream raspbian image.
You can do realtime test here : https://www.vigibot.com
Click on the small blue robot icon named "Astro" from "Pascal" user. The live video appear, (it's a sensitive analog astronomy camera for sky monitoring)

Pascal

[jdb]

Well that ffmpeg command works for me with the Logitech 4K Brio cam. No idea what transport it is using, though - could be either mjpeg, raw or encoded h264.

@pfavr - same question - what ffmpeg command are you using for 4k mjpeg output?

[pfavr]

Well that ffmpeg command works for me with the Logitech 4K Brio cam. No idea what transport it is using, though - could be either mjpeg, raw or encoded h264.

@pfavr - same question - what ffmpeg command are you using for 4k mjpeg output?

This is the command I'm using:

Code: Select all

ffmpeg -f v4l2 -input_format mjpeg -video_size 3840x2160 -framerate 30 -thread_queue_size 64 -i /dev/video0 -c:v copy -copyts -r 30 out.mov

When I was using the newest USB firmware, I had to change the -video_size option to 1920x1080 to make it work. Caused me quite some headache

Thanks for supporting us - really appreciate it!

Best regards,

Peter

[jdb]

OK. Weird stuff is happening.

First, the setpci command isn't sticking because the PCIe link control register is being reset to 0x43, i.e. ASPM enabled, despite writing 0x40 to it. Writing either 0x41 or 0x42 sticks, so I bet the VLI firmware has a task that's clobbering the register if ASPM is disabled.

With PCIe link ASPM enabled, I have two 640x480@30fps yuyv422 cameras that exhibit different behaviours. One camera will get about 2fps via ffmpeg, with many dropped isochronous packets. The other will work just fine at 30fps. The working camera has a video data endpoint alt setting of 3x820-byte packets per isochronous service interval, the broken camera has an alt setting of 3x1020.

On the analyzer with the broken camera attached, there are sporadic times where no isochronous transfers take place, i.e. the controller is not asking the camera for video data. Subsequent video packets have the "error" bit set in the UVC header which causes the driver to throw data away until the camera resets the bit on the start of a new frame. Immediately before the data stream stops, there is a very delayed IN transfer that does not transfer all 3 isochronous packets before the microframe expires. I would guess that the xhci controller is reporting an error at this point, and Linux is cancelling all the outstanding endpoint transfers.

With ASPM "a bit disabled" - 0x41 - the broken camera works.

Similar behaviour can be observed with the Logitech 4k webcam. With default ASPM, 4k streams are stuttery with an average of 11fps - with link control = 0x41 I get 30fps.

Can you repeat your webcam tests after running sudo setpci -s 01:00.0 0xd4.B=0x41?

[Serveurperso]

Hello,

- I just put on my Raspberry PI 4 the fresh Raspbian Image (+Vigibot software) from my CI/CD.

- First boot, USB Capture Work (because old EEPROM from previous image with EEPROM update disabled)
- Second boot (EEPROM auto update) - USB Capture NOT Work (It mimics good functioning but no video)

- I keep the "bad" ffmpeg capture process runing and I type your cmd " setpci -s 01:00.0 0xd4.B=0x41 "
- Video appear immediately on vigibot.com without other action.

Interesting :I don't need to restart ffmpeg process to repair it with setpci.
You are on the right way for the debug.

[neeto33]

As foot note,
This also affects streams for DVB-T USB receivers.
I have three DVB-T USB receivers plugged into a USB3 hub on one of the Pi 4's USB3 ports.
Without the setci -s 01:00.0 0xDB.B=0x41 there is continual breakup of the stream, like what others have reported from their webcam.
Been chasing this for a number of weeks - glad to get to the bottom of it.

[crnewton]

I had 2 issues that seem to be related to this firmware update.
the update didn't fix it for me, 'sudo setpci -s 01:00.0 0xD4.B=0x41' dit fix it (with our without this update).

my problems were:
- usb lagging & key sticking when using usb webcam:
https://www.raspberrypi.org/forums/view ... p?t=256681
https://www.raspberrypi.org/forums/view ... 8&t=246771
- pygame.getimage unable to get a high resolution from the usb camera:
https://bugs.launchpad.net/raspbian/+bug/1857438

I hope this info helps.

[KaraokeAmerica]

Hi,

Booting from a PNY SSD.....

I may have been in hibernation for the last 6 months so sorry if I missed this and revived this old thread, but are you saying you booted a Pi4 from USB? I thought that feature wasn't available yet?

[jamesh]

Hi,

Booting from a PNY SSD.....

I may have been in hibernation for the last 6 months so sorry if I missed this and revived this old thread, but are you saying you booted a Pi4 from USB? I thought that feature wasn't available yet?

It's not. They would need to be using an SD card for initial boot.

[tyjtyj]

Weird. Injecting current into the D+/D- lines has been known to stop the PMIC from starting up as it causes leakage into the 3.3V supply.
The only way that the firmware could be changing this behaviour is if Vbus isn't removed during device reset - worth investigating.

Do we have solution to this? the issue remain on latest stable firmware.

[Ratsima]

For people experiencing webcam issues, what happens if you use the 0137ab firmware and run the following commands?

Code: Select all

sudo apt install pciutils
sudo setpci -s 01:00.0 0xd4.B=0x40

This disables PCIe link power management on the VLI chip.

I am on the latest firmware as of now:

Code: Select all

VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

But was having trouble with a USB webcam dropping off the USB bus. I tried your setpci suggestion. So far, it seems to have worked. But, I have a question:

You use sudo setpci -s 01:00.0 0xd4.B=0x40, but elsewhere
.
<https://github.com/raspberrypi/firmware ... -560105610>
.
I've seen sudo setpci -s 01:00.0 0xd4.B=0x41.

Can you explain the difference? I'm not sure which one I should use.

[jdb]

The difference is disabling powersaving completely, (0x40) or leaving L0s sleep state enabled (0x41). In theory, 0x40 should remove any performance impact from the latency added by low-power modes. 0137ad has a bug where 0x40 ends up having no effect and 0x41 does, but this is fixed in later versions.

[Ratsima]

The difference is disabling powersaving completely, (0x40) or leaving L0s sleep state enabled (0x41). In theory, 0x40 should remove any performance impact from the latency added by low-power modes. 0137ad has a bug where 0x40 ends up having no effect and 0x41 does, but this is fixed in later versions.

Thank you. Perfectly clear and concise.