Here’s a fresh compile from ‘main’: "updating to address pip changes
now using the default cmake instead of the python one to align to the
operting system’s preferred directions. this shouldn’t really be an
issue as there’s nothing extremely fancy going on in cmake
also moving the docker compose to my personal repo for now, need to talk
with the bp team if they’re fine with me actually pushing a real org for
them."
Here’s a fresh compile from ‘main’: “new image to header script does all pre- and post processing to C header file. Flips image, resize, convert to 565, and reshuffel pixel byte order. New background image header, improved screen draw time and startup time.”
I’ve just installed this on my BP5 and when it reboots, I cannot connect to the UART interface. Well, it connects but it does not respond to any commands.
I had the same problem building from source on both my BP5 and BP6.
This version has an issue where I cannot connect to the serial interface (the text device I normally use with minicom). The storage volume mounts on Linux with no problems in read/write.
When I try minicom, it does connect, but never returns a prompt (I’m expecting the console Y/N prompt).
Here’s the kernel log from when I initially connect:
[266860.042809] usb 3-3.4.3: new full-speed USB device number 54 using xhci_hcd
[266860.136164] usb 3-3.4.3: New USB device found, idVendor=1209, idProduct=7332, bcdDevice= 1.01
[266860.136180] usb 3-3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[266860.136185] usb 3-3.4.3: Product: Bus Pirate 5
[266860.136189] usb 3-3.4.3: Manufacturer: Bus Pirate
[266860.136192] usb 3-3.4.3: SerialNumber: 264235D3012961E4
[266860.159227] cdc_acm 3-3.4.3:1.0: ttyACM0: USB ACM device
[266860.160165] cdc_acm 3-3.4.3:1.2: ttyACM1: USB ACM device
[266860.160809] usb-storage 3-3.4.3:1.4: USB Mass Storage device detected
[266860.161442] scsi host1: usb-storage 3-3.4.3:1.4
[266861.216982] scsi 1:0:0:0: Direct-Access BP5 Storage 1.0 PQ: 0 ANSI: 2
[266861.217938] sd 1:0:0:0: Attached scsi generic sg1 type 0
[266861.227417] sd 1:0:0:0: [sdb] 47824 2048-byte logical blocks: (97.9 MB/93.4 MiB)
[266861.228201] sd 1:0:0:0: [sdb] Write Protect is off
[266861.228210] sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
[266861.229191] sd 1:0:0:0: [sdb] No Caching mode page found
[266861.229204] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[266861.250824] sdb: sdb1
[266861.251034] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[266864.898960] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
There are no additional entries when I connect with minicom.
I did a little more experimenting. So, with build c6fb4a3:
Plug in USB cable to BP5
storage automounts on Linux host in read/write mode
Open serial terminal, in my case /dev/ttyACM0 in minicom
minicom opens, but BP5 does not accept any input
Volume does not remount and is still read/write
Manually unmount the BP storage from the host sudo umount /dev/sdb1
The serial interface now starts responding in minicom
The storage volume automatically remounts itself on the host in read-only mode
It seems we are very close, but on Linux systems (at least mine, a pretty standard Ubuntu 22.04.4) there is a missing something to force removal on serial connection.
Also, it is still remaining mounted read-only after leaving the serial connection.
Logging details
Kernel logs for Initial plug in of BP5:
[278668.115095] usb 3-3.4.3: USB disconnect, device number 59
[278668.137881] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
[278669.066838] usb 3-3.4.3: new full-speed USB device number 60 using xhci_hcd
[278669.159135] usb 3-3.4.3: New USB device found, idVendor=1209, idProduct=7332, bcdDevice= 1.01
[278669.159156] usb 3-3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[278669.159165] usb 3-3.4.3: Product: Bus Pirate 5
[278669.159170] usb 3-3.4.3: Manufacturer: Bus Pirate
[278669.159175] usb 3-3.4.3: SerialNumber: 264235D3012961E4
[278669.184715] cdc_acm 3-3.4.3:1.0: ttyACM0: USB ACM device
[278669.185943] cdc_acm 3-3.4.3:1.2: ttyACM1: USB ACM device
[278669.186594] usb-storage 3-3.4.3:1.4: USB Mass Storage device detected
[278669.187177] scsi host1: usb-storage 3-3.4.3:1.4
[278670.220897] scsi 1:0:0:0: Direct-Access BP5 Storage 1.0 PQ: 0 ANSI: 2
[278670.221823] sd 1:0:0:0: Attached scsi generic sg1 type 0
[278670.229914] sd 1:0:0:0: [sdb] 47824 2048-byte logical blocks: (97.9 MB/93.4 MiB)
[278670.230778] sd 1:0:0:0: [sdb] Write Protect is off
[278670.230782] sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
[278670.232506] sd 1:0:0:0: [sdb] No Caching mode page found
[278670.232515] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[278670.253154] sdb: sdb1
[278670.253397] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[278673.607231] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Connecting to serial with minicom did not product any new entries in kernel log.
Kernel logs for after manual unmount of storage from host:
[278773.331174] sdb: detected capacity change from 191296 to 0
[278775.386193] sd 1:0:0:0: [sdb] 47824 2048-byte logical blocks: (97.9 MB/93.4 MiB)
[278775.387303] sd 1:0:0:0: [sdb] Write Protect is on
[278775.387310] sd 1:0:0:0: [sdb] Mode Sense: 03 00 80 00
[278775.389396] sdb: detected capacity change from 0 to 191296
[278775.398037] sdb: sdb1