TilCreator 🦦

96 Followers
127 Following
1.3K Posts

I'm weird (and nsfw)!
Howdy!
18+

(Paw vectored by betalars)

active as🦦 Furry, Bronie, Nerd (official)
webhttps://tils.pw
languagesde, en
pronounstil, they/them, he/his
OH: Andere Events haben Aruba APs, dieses hat A Roomba APs
#dhcp24
always wear your ESD safety strap!
*vias at home*

@c3staub is on it again at #cccamp23 ! Here is a coaster wheel from my Transpotter Lily, the bearing disinitigrated almost completely! I do have a few replacements, let's hope those will last at least a bit longer...

(image taken by @LeoDJ)

Don't you just hate it as well when designers forget to extend out all the pins as well? ^^
This is an FlyingFolk F4 flight controller, it has a 1mb flash variant of the F4 so it can run Ardupilot. I already reverse engineered the fc (after FlyingFolk refused to provide the schematic) and ported Ardupilot. I just needed a second i2c interface and CAN and found some unused pins. I will be releasing the files soon, but feel free to ask for the WIP files!
Now traveling by train with my Transpotter. ETA 12:00 at #GPN21 !
Und wer hilft mir jetzt das ich mich nicht vergesse?!
Found a much "better" solution, just extend the USB connection! It works surprisingly well. I'm almost tempted to install a USB hub and USB uart as well or even a Raspberry Pi Zero. But the current plan still allows using the uart or gpios for other things.

*curses at SWD at a frequency that somehow fails to transmit over a wire longer than 3cm*

Does anyone have any hints on how to extend SWD? Maybe Dsub just fails or wire shielding is a must?
I have not jet looked at it with a scope (too tired), but that will be the first thing to try tomorrow.
I tried a lot already and the board is still alive, this is just the last photo while trying to get any signal ^^

So apparently I discovered another curse of mine. Boards with a esp32-pico-d4 seam to just not communicate with me or rather my laptop is often unable to send anything over the on board uart. Now it turns out that no one else seams to have this issue, but I just discovered that my beaglebone blue can reproduce the error. Communication seams to work when using an external different uart, but there is still further research needed ^^
I also have problems with tinypicos which also use the same uC