331–340 of 356 posts
How easy is it to share memory between two of these processors?
Easiest would be to wire up two chips with bidirectional links and use a fault handler to transfer small blocks of memory across. You're reimplementing a poor man's MESIF https://stackoverflow.com/questions/31876808.
This is very exciting! For the last several years I have been developing a brushless motor driver based on the RP2040 [1]. The driver module can handle up to 53 volts at 30A continuous, 50A peak. I broke the driver out to a separate module recently which is helpful for our farm robot and is also important for driver testing as we improve the design. However this rev seems pretty solid, so I might build a single board…
Earlier quoted context omitted.
If it's in the gigabyte range it's just not an MCU by any stretch. And if it has a proper (LP)DDR controller it's not one either really
Yes and no. Plenty of such applications that use a µC + an FPGA. FPGA interfaces with some DDR memory and CMOS/CCD/whatever. Up to you what you call it.
How easy is it to share memory between two of these processors?
Hmm, a 4-core cluster? Easiest would be to wire up two chips with bidirectional links and use a fault handler to transfer small blocks of memory across. You're reimplementing a poor man's MESIF https://stackoverflow.com/questions/31876808 .
> 1 × USB 1.1 controller and PHY, with host and device support Sure, after integrating USB 2.0 HS or 1Gb-Ethernet the pico2-board will cost more than $5. So, integrated high-speed interfacing with PC was not a nice-to-have option (for special chip flavor)?
>USB 2.0 HS 480 Mbps SERDES > or 1Gb-Ethernet 1.25 Gbps SERDES
Earlier quoted context omitted.
Yes and no. Plenty of such applications that use a µC + an FPGA. FPGA interfaces with some DDR memory and CMOS/CCD/whatever. Up to you what you call it.
So you make hardware costing dozens of thousands of dollars and brag about memory on 5$ chip? That explains a lot why so many medical and industrial (I haven’t touch military hardware) are so badly designed, with some sad proprietary protocols and dead few months after warranty passes. Today I’ve learned!
When you make 1M thingies, $5 savings each means $5M CEO comp.
Earlier quoted context omitted.
> My hope is that they'll eventually provide a library of ready-made "soft peripherals" Perhaps they could be more ready-made, but there are loads of official PIO examples that are easy to get started with. https://github.com/raspberrypi/pico-examples/tree/master/pio
These examples are cute, but this isn't a comprehensive collection. Not even close. Given that PIO's most compelling use case is replacing legacy MCUs, I find it disappointing that they haven't provided PIO boilerplate for the peripherals that keep those archaic architectures relevant. Namely: Ethernet MII and CANbus. Also, if RP2xxx is ever going to play ball in the wireless space, then they need an out-of-box Bluet…
Earlier quoted context omitted.
As other more than 30% of English words [1]: [1] Is English just badly pronounced French [video]: https://news.ycombinator.com/item?id=40495393
No, French is badly pronounced French - the English (Norman) versions are often closer to the original pronunciation
> The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary.
(quote swiped from https://en.wikiquote.org/wiki/James_Nicoll)
Earlier quoted context omitted.
the price difference from usb to usb-c is less than 2 cents
devil's advocate: cables for an average user is a different story. also not to forget the vast range of cables already existing out there. also "proper" usb-c support is another can of worms, and maybe sticking to an older standard gives you freedom from all that.
USB3 and altmodes require extra signal lines and tolerances in the cable.
High-voltage/current requires PD negotiation (over the CC pins AFAIK)
Data and power role swaps require muxes and dual-role controllers.
That's all the stuff that makes USB-C a pain in the ass, and it's all the sort of thing RPi Nanos don't support.