87 Followers
47 Following
967 Posts

I occasionally do some hobby electronics projects. 🇳🇱

29 years young

Homepagehttps://nekai.dev/
Favourite SMD package size0603 (1608 metric)
PronounsDon't care/ he,him
@pbog
Yup. Thankfully I can have other people do this for me, and I'm glad I don't need to take that responsibility
@AdalwinAmillion
@jannem
Its not as uncommon as you might think. Maybe its uncommon in programming, but it is quite common in electronics. Tri state buffers can output a 1, a 0, or 'nothing' which lets other components determine the logic level.
@mdiluz

Its a classic case of RTFM! The first 4k of flash memory needs to contain a magic block of information that describes the executable. This is handled automagically for you when using the SDK, but it isnt obvious when building without the SDK.

So i had an ELF file, and to load that ELF file to the pico i used picotool, and it executed without complaints or warnings. I assumed that, when loading an ELF file where E stands for 'executable', the program would actually be executable.

But without that magic pattern it isnt! And not a single warning message that says "hey, this probably wont work, you might want to add a magic block to your program!" not during the coversion to UF2, not during directly loading, not during uploading the UF2. That certainly caused me some gray hairs..

@aislerhq
I didnt know fabs did this! I would figure they would at least ask permission??

I got a strange issue with debugging a RISC-V program on a raspberry pi pico 2W. I can upload the program to the flash, but when i try to connect openocd it seems that the RISC-V cores are not active. I need to explicitly reboot into riscv mode to be able to use openocd and gdb.

Then when i connect to the program, the current instruction is way outside the program flash memory and when i examine the flash location, it just returns all zeroes, as if the program was never written. However, when i dump the program with picotool, then i _can_ see the program at the correct location. It just seems the riscv cores cannot access the flash memory.

I'm gonna try with a non-W pico 2 but if anyone can give some insights or hints i'd greatly appreciate it!

@furrfu
Running a >1GHz single board computer with multiple gigabytes of RAM, running an OS of several gigabytes just to... Emulate a 'call elevator' button.

And it doesnt even work properly. Not to mention the problematic accessibility.
@loganer @Ninji

@Flaky
I've also never had any real issues with it. I remember there were one or two times that windows switched the default bootloader, but that was easily repaired as the linux bootloader was never overwritten
@dogo
Man that is amazing! Vista really was the best looking OS from microsoft, by far

These adressable RGB leds are nice, but the brightness curve really bothers me: they get way too bright way too fast. The channels range from 0-255 but when driving them at 50 they are already pretty bright.

It also means that at low intensities, the quantization effect is _really_ noticable. When i slowly animate the brightness, you can bery obviously see the leds step in brightness.

It would be better if a) the response would be logarithmic or something, or b) more resolution

@TheMNWolf Yup, I saw it in my timeline before you posted about not seeing your own posts.