Then I'd pack 16 of them, and build a tiny Connection Machine cube.
Not sure what I'd use a cluster of 512 very puny servers for though... I guess it'd be for learning how to manage clusters with unreasonable numbers of nodes.
181–190 of 207 posts
Then I'd pack 16 of them, and build a tiny Connection Machine cube.
Not sure what I'd use a cluster of 512 very puny servers for though... I guess it'd be for learning how to manage clusters with unreasonable numbers of nodes.
Earlier quoted context omitted.
I've been experimenting with more-or-less this on the existing ESP32-S3 (well, to a smartphone/PC rather than a 2nd ESP32). Practical bandwidth limits are in the ~72kb/s range with Bluetooth and a custom wire protocol, and Opus voice-mode encoding can't run in realtime beyond complexity 3; music encoding can't run at all. Maybe there's a more compute-friendly audio codec I'm not aware of, but as far as I know these c…
I was not aware that _any_ Espressif hardware even supported classic bluetooth other than the very first ESP32 (which I am not sure if they're even available). And I was getting around 50ms latency back then (with the original ESP32 and SBC!) What exactly did you try?
Earlier quoted context omitted.
I've been experimenting with more-or-less this on the existing ESP32-S3 (well, to a smartphone/PC rather than a 2nd ESP32). Practical bandwidth limits are in the ~72kb/s range with Bluetooth and a custom wire protocol, and Opus voice-mode encoding can't run in realtime beyond complexity 3; music encoding can't run at all. Maybe there's a more compute-friendly audio codec I'm not aware of, but as far as I know these c…
I haven't benchmarked Bluetooth on these devices but have you looked at your uncompressed audio rates over WiFi? OP was asking about Bluetooth at high quality and low latency, which I don't think is a possible combo, hence suggesting another ESP32 if wireless is necessary. If it isn't, a wire difficult to beat. ESP-NOW is another option to look at, which of course won't work to transmit to a phone directly but can do…
These little devices are extremely interesting. I have a side project I will one day get started - to place 32 SoCs (or fewer SoCs with more cores), connect them via PCB traces to an ethernet hub (I need to learn how to do that), and leave one or more "upstream" network ports for connecting multiple boards together. Each core would light up a red LED on the front-side of the board via 90-degree LED holders. Then I'd…
Meanwhile, Texas Instruments[0]... 0. https://news.ycombinator.com/item?id=48378136
These little devices are extremely interesting. I have a side project I will one day get started - to place 32 SoCs (or fewer SoCs with more cores), connect them via PCB traces to an ethernet hub (I need to learn how to do that), and leave one or more "upstream" network ports for connecting multiple boards together. Each core would light up a red LED on the front-side of the board via 90-degree LED holders. Then I'd…
And yes the main goal is to figure out how to program the thing in a way that balances ease of use with performance.
I also like the idea of a PSRAM junction, so that every core gets a PSRAM, but neighbours can swap ownership.
I had wondered what happens to the wireless spectrum if you tried it with ESP32. 512 devices in a small space yelling at each other.
These little devices are extremely interesting. I have a side project I will one day get started - to place 32 SoCs (or fewer SoCs with more cores), connect them via PCB traces to an ethernet hub (I need to learn how to do that), and leave one or more "upstream" network ports for connecting multiple boards together. Each core would light up a red LED on the front-side of the board via 90-degree LED holders. Then I'd…
little?
Earlier quoted context omitted.
I see you are unfamiliar with `rv64mafdcbvh_zicsr_zicntr_zihpm_ziccif_ziccrse_ziccrse_ziccamoa_zicclsm_za64rs_zihintpause_zic64b_zicbom_zicbop_zicboz_zfhmin_zkt_zihintntl_zicond_zimop_zcmop_zcb_zfa_zawrs_supm_svade_ssccptr_sstvecd_sstvala_sscounterenw_svpbmt_svinval_svnapot_sstc_sscofpmf_ssnpm_ssu64xl_sstateen_shcounterenw_shvstvala_shtvala_shvstvecd_shvsatpa_shgatpa` also known as `RVA23`
rva23 is pretty friendly. Needn't use the long thing.
Earlier quoted context omitted.
little?
Once I figure out how to join that many cores via ethernet on PCB, it's a little project. SMD soldering should not be that troublesome.
ESP32 RGMII (32x) -> PHY (32x RTL8211F) -> Slave switch (6x RTL8367) -> master switch (1x) -> magnetics (for the external port). You’ll probably want a better IC for the master switch so I can’t name one of the top of my head but this would be a relatively simple, if large, PCB.
The hard part I think is verifying that all the PHYs and switches will work correctly without magnetics on a board to board connection.
Earlier quoted context omitted.
Lots of assumptions off a comment that is mostly just me stating my preference for short and unique part numbers. Nothing would be wrong with ESP32xx ESP33xx, ESP34xx, etc. Espressif only have 312 SKUs [0]. You're telling me nobody could come up with a naming scheme where more than 2/3 of them don't have part numbers longer than 18 characters? Doesn't really matter either way, but short part numbers do fit nicely in…
You're going to really, really hate learning about STM32 MCUs. https://www.digikey.ca/short/2v4t0n5m