Live data from Hacker News

I got almost all of my wishes granted with RP2350

dmitry.gr

141–150 of 356 posts

Re: I got almost all of my wishes granted with RP2350

#141
post #71

You can pick either ARM cores or RISC-V cores on the same die? Never saw design like this before. Will this impact price and power consumption? "The Hazard3 cores are optional: Users can at boot time select a pair of included Arm Cortex-M33 cores to run, or the pair of Hazard3 cores. Both options run at 150 MHz. The more bold could try running one RV and one Arm core together rather than two RV or two Arm. Hazard3 is…

This seems like a great way to test the waters before a potential full-on transition to RISC-V. It allows to validate both technically and market reception, for a much lower cost than taping out a additional chip.

I do wonder if the unavailability of some of the security features and -- possibly a big deal for some applications -- the accelerated floating point on the RISC-V cores would skew that experiment, though.

Re: I got almost all of my wishes granted with RP2350

#142
Big day for my team (Pigweed)! Some of our work got mentioned in the main RP2350/Pico2 announcement [1] but for many months we've been working on a new end-to-end SDK [2] built on top of Bazel [3] with support for both RP2040 and RP2350, including upstreaming Bazel support to the Pico SDK. Our new "Tour of Pigweed" [4] shows a bunch of Pigweed features working together in a single codebase, e.g. hermetic builds, on-device unit tests, RPC-centric comms, factory-at-your-desk testing, etc. We're over in our Discord [5] if you've got any questions

[1] https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new...

[2] https://opensource.googleblog.com/2024/08/introducing-pigwee...

[3] https://blog.bazel.build/2024/08/08/bazel-for-embedded.html

[4] https://pigweed.dev/docs/showcases/sense/

[5] https://discord.gg/M9NSeTA

Re: I got almost all of my wishes granted with RP2350

#143

Big day for my team (Pigweed)! Some of our work got mentioned in the main RP2350/Pico2 announcement [1] but for many months we've been working on a new end-to-end SDK [2] built on top of Bazel [3] with support for both RP2040 and RP2350, including upstreaming Bazel support to the Pico SDK. Our new "Tour of Pigweed" [4] shows a bunch of Pigweed features working together in a single codebase, e.g. hermetic builds, on-d…

I hate Bazel. A build system for C/C++ should not require a Java JVM. Please keep Java out of microcontroller ecosystem please -__--

Re: I got almost all of my wishes granted with RP2350

#144

You can pick either ARM cores or RISC-V cores on the same die? Never saw design like this before. Will this impact price and power consumption? "The Hazard3 cores are optional: Users can at boot time select a pair of included Arm Cortex-M33 cores to run, or the pair of Hazard3 cores. Both options run at 150 MHz. The more bold could try running one RV and one Arm core together rather than two RV or two Arm. Hazard3 is…

Apparently (this is news to me), you can also choose to run 1+1 Arm/RISC-V, you don't have to switch both cores either/or. Eben Upton: "They're selectable at boot time: Each port into the bus fabric can be connected either to an M33 or a Hazard3 via a mux. You can even, if you're feeling obtuse, run with one of each." Source: https://www.theregister.com/2024/08/08/pi_pico_2_risc_v/

Would've been cool for safety applications if the second core could be run in lockstep mode.

Re: I got almost all of my wishes granted with RP2350

#145
post #143

Big day for my team (Pigweed)! Some of our work got mentioned in the main RP2350/Pico2 announcement [1] but for many months we've been working on a new end-to-end SDK [2] built on top of Bazel [3] with support for both RP2040 and RP2350, including upstreaming Bazel support to the Pico SDK. Our new "Tour of Pigweed" [4] shows a bunch of Pigweed features working together in a single codebase, e.g. hermetic builds, on-d…

I hate Bazel. A build system for C/C++ should not require a Java JVM. Please keep Java out of microcontroller ecosystem please -__--

And only discord on top, but maybe I'm simply not hip enough

Re: I got almost all of my wishes granted with RP2350

#146

RP2040 had Doom ported to it. https://kilograham.github.io/rp2040-doom/ RP2350 looks very much like it could potentially run Quake . Heck, some of the changes almost feel like they're designed for this purpose. FPU, two cores at 150 MHz, overclockable beyond 300 MHz and it supports up to 16 MB of PSRAM with hardware R/W paging support.

While outputting DVI! I wouldn't be surprised.

Re: I got almost all of my wishes granted with RP2350

#147
post #35

And still no USB C on the official devboard.

There's plenty of alternatives right out of the gate, at least: https://www.raspberrypi.com/for-industry/powered-by/product-... Pimoroni has a maxed-out pin-compatible version with 16MB flash, 8MB PSRAM, and USB-C: https://shop.pimoroni.com/products/pimoroni-pico-plus-2

Unless the USB-C connector costs $7-10, these are beyond ridiculously overpriced compared to the official dev board. At least throw in an IMU or something if you plan to sell low volumes at high prices jeez.

Re: I got almost all of my wishes granted with RP2350

#148
post #140

Earlier quoted context omitted.

How much tolerance does that have - can it run directly off a 3.7v lithium ion battery?

Yep, they explicitly call out that the onboard voltage regulator can work with a single lithium ion cell.

The regulator can take that, but as far as I can see it's only for DVDD, the core voltage of 1.1 V. You also need at least IOVDD, which should be between 1.8 V and 3.3 V. So you'll need to supply some lower voltage externally anyway.

I suppose the main draw of the regulator is that the DVDD rail will consume the most power. 1.1 V is also much more exotic than 3.3 V.

Re: I got almost all of my wishes granted with RP2350

#149
post #135

Earlier quoted context omitted.

To clarify: You can connect a 5V power source by connecting it to the VSYS pin which leads into the on-board voltage regulator. But the µC itself runs on 3.3V and is not totally 5V-capable. You'd need level converters to interface with 5V.

You're right, after re-reading the Power section on the datasheet it seems connecting 5V to the VREG_VIN should suffice to power the digital domains, but if you want to use the ADC, you still need a external 3.3V source.

Maybe not even that:

> A separate, nominally 3.3 V, low noise supply (VREG_AVDD) is required for the regulator’s analogue control circuits.

It seems it would be painful trying to run this without 3.3 V.

Post reply on HN