Hi @giuliomoro
Deleted the duplicate posts - Thanks!
giuliomoro maybe you already did it, but just checking: what do you get when you power from VBAT and you connect the USB and then you do lsusb ? And does that get updated when you disconnect/reconnect the USB device?
I did this before - but I just gave it another go to pull the log for it. Whether I boot it up from VBAT with the USB A cable plugged in or plug it in after boot the result is the same. The log comes out like this:
Debian GNU/Linux 9 bela ttyGS0
bela login: root
Last login: Wed Aug 7 04:48:05 UTC 2019 from 192.168.6.1 on pts/0
Linux bela 4.4.113-ti-xenomai-r149 #1 PREEMPT Wed Sep 26 15:40:33 BST 2018 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
____ _____ _ _
| __ )| ____| | / \
| _ \| _| | | / _ \
| |_) | |___| |___ / ___ \
|____/|_____|_____/_/ \_\
The platform for ultra-low latency audio and sensor processing
http://bela.io
Bela image, v0.3.6b, 23 October 2018
More info at https://github.com/BelaPlatform/bela-image-builder/releases
Built with bela-image-builder master@a4e9924154600e329889fe2564b6331575b25e37
on Tue 23 Oct 13:25:56 BST 2018
root@bela:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@bela:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@bela:~#
The second "lsusb" is after unplugging and re-plugging the USB A cable in. The output is the same.
Not really sure what to make of the VBUS_ERROR. I see that it takes place after the initial lines about the USB hub being detected and such - but Within that first second - I wasn't messing with the USB A Cable or anything. The pedal was just sitting on the table. Not sure what's going on...
I guess at this point I'll just have to wait to see if you can reproduce the issue on your side. If not, then I guess it has to be some kind of hardware failure. I'll stand by for any additional details on your side.