Live data from Hacker News

EsPiFF: An ESP32 in the Raspberry Pi form factor

github.com

61–66 of 66 posts

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#61
post #43
post #40

Earlier quoted context omitted.

The ESP32 is stronk. I wasted a bunch of time implementing fixed point maths and lookup table trig functions because “of course” before testing it and finding that for our purposes just calling sin/cos wasn’t an issue. Edit: If you’re doing ‘real’ real-time stuff then make sure you get a dual core model and use core 2 for time sensitive things, though. The wifi stack uses up some solid chunks of time.

To be fair, back in the day most likely you have had to use fixed point math. :)

The problem is that today, a lot of programmers remember that and ignore the fact that you can often do floating point math on a modern real time system and meet all your deadlines.

Just last week I fixed a bug in such a system: in an effort to speed things up by avoiding floating point math, calculations were done with uint32_t's and the developer(s) didn't notice that in some cases there was an internal overflow before the final result was produced.

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#62
post #44

Earlier quoted context omitted.

Wish there was an ESP64 with just enough RAM to run a Debian distro, even slowly, so we could stop waiting for Zeros to get cheaper.

BeagleBone has always been an option. The cool kids just choose to ignore it.

I have a BBB in a drawer somewhere. It's a very nice platform, but I quickly realized that for the $50, I could use a $30 RasPi B+ (back when you could get them) talking to a $2 arduino clone and accomplish the same thing far more easily.

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#63

Earlier quoted context omitted.

They decided to design this whole thing instead of just going with a read only SD partition or one of the CM4 docks with eMMC? Don't get me wrong, the end result is really cool and if just an ESP can cover their entire use case then the Pi was definitely overkill, but it just seems like inventing a flying car because you once got a flat tire.

We also depend on RPys. Right now the supply chain problems RPys are so big,that they are reselling RP 4s for over 300 euros!! Imagine that over night the price of cars go 3x and you have to wait a long time for them. Different people are finding different alternatives. We also created a very convoluted solution.

That's understandable, but has nothing to do with what the poster was saying.

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#64
post #51

Earlier quoted context omitted.

rp2040 might be a good alternative nowadays, esp with its PIO blocks. esp32 might have some other political "risks" these days as it is made in china.

I am not sure why the Raspberry Pi Pico abandoned the 40 pin interface. It would be really cool to be able to develop C or Python code both under Linux, for ease of editing and debugging, and then run it on a microcontroller.

pico does have 40 pins, and yes I develop all c/python on it under x86 linux, you can also develop it on a Raspberry Pi.

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#65

"All I want for Christmas is SD-card reader on my ESP32." - Finds micropython library. Ok. - Finds schematics for physical connection. Ok "But where do I find that fiddly SD-card bracket?" - Opens a drawer, sees a mound of useless MicroSD-adaptors . Ok.

That was easy -- eventually. One only has to believe what the micropython manual says and not watch any instructables-videos. >>> os.mount(machine.SDCard(slot=2),"/sd") >>> os.listdir('/sd') ['DCIM', 'VIDEO', 'PHOTO']

Using SD-card on ESP8266 was more challenging.

upip.install('sdcard') did not work.

But ChatGPT truly helped and suggested I find it in Github.

https://github.com/micropython/micropython-lib/blob/master/m...

Re: EsPiFF: An ESP32 in the Raspberry Pi form factor

#66
post #51

Earlier quoted context omitted.

I am not sure why the Raspberry Pi Pico abandoned the 40 pin interface. It would be really cool to be able to develop C or Python code both under Linux, for ease of editing and debugging, and then run it on a microcontroller.

pico does have 40 pins, and yes I develop all c/python on it under x86 linux, you can also develop it on a Raspberry Pi.

I mean the 2x20 header. It's become a standard for Linux SBCs but not for microcontrollers.

The Pico doesn't let you use a Raspberry Pi with ssh to develop your code using the very same hardware modules that you will use on the microcontroller. You need to either make a mess of jumper cables, or cross compile and transfer the executable constantly over serial.

Post reply on HN