Klingt Spannend @adafruit denkt über einen #CircuitPyrate aka #BusPirate mit #RP2040 nach https://social.tchncs.de/@adafruit@mastodon.cloud/110324082924077930

Bon, ça semble compliqué à trouver un #BusPirate en stock sur les #zinternets... http://dangerousprototypes.com/docs/Bus_Pirate
Dis #masto, tu n'en aurais pas un à me vendre d'occaze ? #Hacking (c'est rigolo, ça m'a tout de suite fait penser à @dlb 😉 )

My #ESP32 + #SHT30 sensor combo did not work together. After a lot of time debugging, it turns out it was *my* shoddy soldering - everything works on the breadboard, but some of the pin headers don't work.

At least I got to play around with my old tinkering tools, like #Buspirate and #DSO138. But now I need to figure out how to unsolder those pin headers...

If you wish to flash your #USBasp programmer with a new firmware using #buspirate, you need to short both VCCINT AND Self prog.

I2C>[0xd0 0xe 0]

Blink!

#ds3231 #buspirate

[0xd0 0 [0xd1 r:19] #buspirate #ds3231

For people wondering, the tools im using is a #buspirate with a soic8 clip.

Software is flasrom.

I'm thinking to use it to flash coreboot on my x220 laptops

Current status: repairing NAS #debian #buspirate #serial #headless #powercuts

https://mamot.fr/media/PZIp-WWnxPjDOBkmWDc

Delivered. https://github.com/steelman/BME280_driver/ #buspirate #bme280

It was me this time. I used the bulk write command improperly (I suppose). Off-by-one-or-two bug. #buspirate #bme280

Again. #BusPirate's text mode works fine, registers are set to proper values, and the bin mode fails. #BME280 #WTF

Yet another bug in the #buspirate. Twenty "\0" switch to bin mode. "\0" resets the bin mode. "\17" resets BusPirate. "\0\0\0\0\0\0\0\17" resets the bin mode seven times and finally resets the BusPirate. but "\0\0\0\0\0\0\0\0\17" makes BP stop doing anything except the bin reset and printing "BBIO1" no matter what bytes it receives.

Using the lower level commands works, but I get only humidity. Temperature and pressure are fixed at 0x800… raw values. #bme280 #buspirate

Strange bug in the #buspirate firmware, makes it impossible to read byte at address 0x9f from the #BME280 with the "0x80 - Write then read" command.

Porting the original #BME280 driver[1] to #BusPirate binary scripting interface[2] is quite a fun. The results will be available.

[1] https://github.com/BoschSensortec/BME280_driver
[2] http://dangerousprototypes.com/docs/I2C_(binary)

#ds3231 #buspirate

Apparently reading anything more than ID from #BME280

I2C>[238 0xd0] [239 r]
I2C START BIT
WRITE: 0xEE ACK
WRITE: 0xD0 ACK
I2C STOP BIT
I2C START BIT
WRITE: 0xEF ACK
READ: 0x60
NACK
I2C STOP BIT

is going to take a bit more time. Not today. #buspirate

You may want to synchronize your system clock with an #NTP server beforehand. #ds3231 #buspirate

TZ=UTC date '+[208 0 0x%S 0x%M 0x%H 5 0x%d 0x%m 0x%y]' > /dev/ttyUSB0

Set current UTC date and time. "5" in the middle is because Arduino libraries assume Sunday is "1" and today is Thursday. Before running this command, set I²C mode on the #buspirate and exit the terminal emulator. #ds3231

Reading DS3231 with a #BusPirate
HiZ>m
…
4. I2C
…
(1)>4
…
3. ~100KHz
(1)>3
Ready
I2C>W
Power supplies ON
I2C>[208 0]
I2C START BIT
WRITE: 0xD0 ACK
WRITE: 0x00 ACK
I2C STOP BIT
I2C>[209 r:0x13]
I2C START BIT
WRITE: 0xD1 ACK
READ: 0x14 ACK 0x43 ACK 0x04 ACK 0x01 ACK 0x01 ACK 0x01 ACK 0x00 ACK 0x00 ACK 0x00 ACK 0x00 ACK 0x21 ACK 0x00 ACK 0x00 ACK 0x12 ACK 0x1C ACK 0x88 ACK 0x00 ACK 0x16 ACK 0x00
NACK
I2C STOP BIT
I2C>