Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I got almost all of my wishes granted with RP2350

dmitry.gr

Post reply on HN
Print view View original

111–120 of 356 posts

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

#111

Post by giantg2 »

jayyhu wrote: post #102
blackkat wrote: post #10

Some specs here: https://www.digikey.ca/en/product-highlight/r/raspberry-pi/r... Based on the RP2350, designed by Raspberry Pi in the United Kingdom Dual Arm M33s at 150 MHz with FPU 520 KiB of SRAM Robust security features (signed boot, OTP, SHA-256, TRNG, glitch detectors and Arm TrustZone for Cortex®-M) Optional, dual RISC-V Hazard3 CPUs at 150 MHz Low-power operation PIO v2 with 3 × programmable I/O co-processors…

Edit: See comment below; The RP2350 can be powered by a 5V supply.

I'd rather have it run on the lower voltage - generally easier to step down than buck up. Either way, the modules are pretty cheap, small, and easy to find.

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

#112

Post by HeyLaughingBoy »

Daneel_ wrote: post #43
synergy20 wrote: post #13

Earlier quoted context omitted.

Wow, can't wait. Love the 5V GPIO and security features.

5V GPIO is a huge deal for me - this immediately opens up a huge range of integrations without having to worry about line level conversion. I can’t wait to use this!

Be careful with assumptions though. Being 5V tolerant doesn't mean that your 3V output can sufficiently drive an input that expects 0-5V levels correctly.

I ran into this problem using an ESP32 to drive a Broadcom 5V LED dot-matrix display. On paper everything looked fine; in reality it was unreliable until I inserted an LS245 between the ESP and the display.

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

#113

Post by HeyLaughingBoy »

tecleandor wrote: post #65
HeyLaughingBoy wrote: post #39

Earlier quoted context omitted.

If it's not an academic question and you have an actual need for the SRAM, what's the p/n? I have some old parts stock and may have what you need.

Oh! Thanks! I wanted to do a clone or two of said cartridges, that use, IIRC (I'm not in my workshop right now) a couple Hitachi HM6116FP each. I've also seen some clones from back in the day using a CXK5864PN-15L, that's 8 kilowords, and getting 4 switchable "memory banks" out of it...

Thought I had more than this, but it's been literally decades...

I found (1) HM6116, (4) HM65256's (1) HM6264 and wonder of wonders, a Dallas battery-backed DS1220, although after 20+ years the battery is certainly dead. All in DIP packages of course.

And a couple of 2114's with a 1980 date code! that I think are DRAM's.

If any of this is useful to you, PM me an address and I'll pop them in the mail.

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

#114

Post by skykooler »

jayyhu wrote: post #102
blackkat wrote: post #10

Some specs here: https://www.digikey.ca/en/product-highlight/r/raspberry-pi/r... Based on the RP2350, designed by Raspberry Pi in the United Kingdom Dual Arm M33s at 150 MHz with FPU 520 KiB of SRAM Robust security features (signed boot, OTP, SHA-256, TRNG, glitch detectors and Arm TrustZone for Cortex®-M) Optional, dual RISC-V Hazard3 CPUs at 150 MHz Low-power operation PIO v2 with 3 × programmable I/O co-processors…

Edit: See comment below; The RP2350 can be powered by a 5V supply.

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

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

#115

Post by mordae »

Archit3ch wrote: post #62
doe_eyes wrote: post #22

I think it's a good way to introduce these chips, and it's a great project, but the author's (frankly weird) beef with STM32H7 is detracting from the point they're trying to make: > So, in conclusion, go replan all your STM32H7 projects with RP2350, save money, headaches, and time. STM32H7 chips can run much faster and have a wider selection of peripherals than RP2350. RP2350 excels in some other dimensions, includin…

> STM32H7 chips can run much faster STM32H7 tops out at 600MHz. This has 2x 300MHz at 2-3 cycles/op FP64. So maybe your applications can fit into this?

It's 6 cycles for dadd/dsub, 16 for dmul, 51 for ddiv.

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

#116

Post by petra »

ryukoposting wrote: post #106

I can't imagine someone using an RP2040 in a real product, but the RP2350 fixes enough of my complaints that I'd be really excited to give it a shot. There's a lot going for the 2040, don't get me wrong. TBMAN is a really cool concept. It overclocks like crazy. PIO is truly innovative, and it's super valuable for boatloads of companies looking to replace their 8051s/whatever with a daughterboard-adapted ARM core. But…

For high volume products, given the low cost of this chip, it would make sense to bother with the PIO or it's open-source libraries.

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

#117

Post by HeyLaughingBoy »

limpbizkitfan wrote: post #64
doe_eyes wrote: post #22

I think it's a good way to introduce these chips, and it's a great project, but the author's (frankly weird) beef with STM32H7 is detracting from the point they're trying to make: > So, in conclusion, go replan all your STM32H7 projects with RP2350, save money, headaches, and time. STM32H7 chips can run much faster and have a wider selection of peripherals than RP2350. RP2350 excels in some other dimensions, includin…

ST is a zillion dollar company that should be hiring the talent capable of delivering product that match the features in their sales pamphlets. Integration is tricky but a company with STs deep pockets should be able to root cause or at least help troubleshoot an issue, not ask for a fix like some nepotism hire.

They should also be hiring people that can write clearly in their datasheets, but here we are, so...

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

#118

Post by [deleted] »

limpbizkitfan wrote: post #64
doe_eyes wrote: post #22

I think it's a good way to introduce these chips, and it's a great project, but the author's (frankly weird) beef with STM32H7 is detracting from the point they're trying to make: > So, in conclusion, go replan all your STM32H7 projects with RP2350, save money, headaches, and time. STM32H7 chips can run much faster and have a wider selection of peripherals than RP2350. RP2350 excels in some other dimensions, includin…

ST is a zillion dollar company that should be hiring the talent capable of delivering product that match the features in their sales pamphlets. Integration is tricky but a company with STs deep pockets should be able to root cause or at least help troubleshoot an issue, not ask for a fix like some nepotism hire.

[deleted]

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

#119

Post by hoherd »

nimish wrote: post #78

Gross, the dev board uses micro-USB. It's 2024! Otherwise amazing work. Exactly what's needed to compete with the existing giants.

FWIW the Pimoroni Tiny 2040 and Tiny 2350 use usb-c, but as mentioned by other commenters, the cost for these usb-c boards is higher.

I love having usb-c on all my modern products, but with so many micro-usb cords sitting around, I don't mind that the official Pico and Pico 2 are micro-usb. At least there are options for whichever port you prefer for the project you're using it in.

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

#120

Post by ewoodrich »

hypercube33 wrote: post #103
user_7832 wrote: post #99

Earlier quoted context omitted.

I wonder if it is more about simply shaving a few cents off. Full USB-C protocol implementation may be much more difficult.

USB-C doesn't require anything special USB wise as it's decoupled from the versioned standard. It just has more pins and works with all modern cables. Ideally the cables won't wear out like Mini and Micro and get loosey goosey in the ports.

Yep, a USB-C connector is more or less a drop in replacement for MicroUSB if you don’t need USB3 or USB-PD. With one aggravating exception: it requires adding two 5.1kΩ pulldown resistors to be compatible with C-C cables. Thus signaling to a charger that the sink is a legacy non-PD device requesting 5V.

Which is apparently an impossible ask for manufacturers of dev boards or cheap devices in general. It’s slightly more understandable for a tried and true dev board that’s just been connector swapped to USB-C (and I’ll happily take it over dealing with Micro) but inexcusable for a new design.

My hope is Apple going USB-C only on all their charging bricks and now even C-C cables for the iPhone will eventually force Chinese OEMs to build standard compliant designs. Or deal with a 50% Amazon return rate for “broken no power won’t charge”.

Post reply on HN