I just updated the firmware on my BPs
I’m having trouble connection to them. I noticed than before if I did lsusb I would get
ATTRS{idVendor}=="1209", ATTRS{idProduct}=="7332"
Now it seems that my BP5 has id 7332 but my two BP5’s now have ID 7331
My udev rules now seem to be incorrect.
Yeah I also noticed that. Just changed that and lived happily on since then:
#Bus pirate v5
SUBSYSTEM=="tty", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="7331", ATTRS{serial}=="32420B0B33CC62E4", ENV{ID_USB_INTERFACE_NUM}=="00", TAG+="uaccess", SYMLINK+="buspirate-text", ENV{ID_SIGROK}+="1"
SUBSYSTEM=="tty", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="7331", ATTRS{serial}=="32420B0B33CC62E4", ENV{ID_USB_INTERFACE_NUM}=="02", TAG+="uaccess", SYMLINK+="buspirate-binary", ENV{ID_SIGROK}+="1"
This are mine now
I’m getting other new errors as well, like - unable to mount file system.
My syslog says
2024-10-14T12:55:03.819583-04:00 X270 udisksd[1080]: message repeated 19 times: [ Couldn't find existing drive object for device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.4/host0/target0:0:0/0:0:0:0/block/sda (uevent action 'change', VPD 'Bus_Pirate_5_Bus_Pirate_Bus_Pirate_5_251821CB83B062E4')]
I rebooted and it’s okay for now. but I think there are some unstability issues. I’m investigating some more.
I hate to report bugs I cannot replicate as I only saw them once, but I was testing the I2C mode and I scanned addresses and found 2 addresses (correct), and then wlthout changing the setup the BP reported that scan found 33 addresses, I tried to issue a bus command and it reported syntax error when I typed
[0b01110010 0b11100000]
and other strangeness.
I 'm suspicious of the si7021 command. I was experimenting with that and things became strange… Currently, the si7021 command returns nothing and half of the individual bus commands returned bus error. I was using
The device demo as a guide.