The big thing for me is DSP instructions. With DMA, 150MHz (likely more if you overclock it), 520kB RAM, and I2S, this chip looks perfect for live audio and radio data processing.
my suspicion: you can't get the 4 cores to run in parallel because there are no 4 cores. they just have different instruction decoders that use the same ALU. that would mean you have two cores but inside a core you have different components, one being the instruction decoder. and you put two different instruction decoders inside the core. also adding more and more cores does not scale up that well because they have to share the same memory bus. with two cores it is easier, because while one core is calculating, the other core is accessing the memory bus. with more cores and DMAs running, you need separate cache blocks to optimize memory access. that is expensive.
Not likely. M33 is a full core from ARM (rpi didn't develop it, they just integrated it in their desing). Hazard 3 is a similar story - didn't know anything about this core, but google search lead me to a github page. It's more likely that RISC-V was an afterthought and quite possible it's a "let's prepare people (and the whole ecosystem) for a better RISC-V in Pico 3" situation.
There is absolutely nothing remotely ridiculous about the formula and it works out to an even number by design (leaving out any extra special purpose memory such as dual port USB buffers which I am guessing is how you get from 512K to 520K). Memory usually comes in powers of 2, 16K, 32K, 64K, 256K, 512K, etc. so log2 makes perfect sense, it is log2(2^x) = x. Thus by taking log2 you are just giving the exponent. And linear multiples would quickly blow through a one digit value:1,2,4,8,oops while log2() gives 10 different sizes you might actually use. And by dividing by 16K, they don't waste values on small sizes they would never make and leave more for big sizes. Besides, log2(16384) is already 14, which is more than one digit. Another way to express it is ram=2^(x+14). Or just start at 16K and double it the number of times specified in the digit.
I'll admit it is archaic knowledge, but I did rewind (lol more archaic knowledge) to make sure I didn't miss something making it ridiculous. It's just a super clean -h (human-readable) flag.
I wonder how much better the pico series will become. I personally use the pico in each of my projects. Imagine the pico 3 or pico 4 having quad core or even octa core with microcontroller level power consumption!!!!
ESP32 is designed, produced, and controlled by a hostile foreign power. Trying to eliminate Chinese processors (especially those with networking), networking chips with bus mastering, firmware, and application software from my life, not increase it. At the very least, it tends to be very insecure and there could be malicious hardware.
@@markwhitisFirst thing you do is the ESP32 Flash as a first step. Almost every laptop has Chinese components in it and was more than likely manufactured in China. Buying no name Chinese networking equipment is a different story. Considering that you get a dual core 240Mhz processor, 512K RAM, 8MB PSRAM which does wonders for video applications, especially when using LVLG, 16MB flash, WiFi and BT for 5 dollars I have no idea why you would opt for one of these over and ESP32-S3 or C6 which is only single core but has Zigbee and is Thread/Matter compatible. Add the fact that they are the basis for ESPHome for Home Assistant, it's RISC so hardware and software is open source (to some degree) and I'm pretty sure someone would have found something malicious considering Home Assistant is the 2nd largest open source project. The world and ESPHome is becoming more popular since Nabu Casa bought it. I made a voice assistant for under 10 dollars with one I would be more concerned about the devices with data exfil capabilities written right into the terms of service (e.g. Google, Apple, Amazon).
1:11 if they make a new RP chip with a small update (same no.of cores, same type of cores, ram is not at least double previous, non-volatile memory is not at least double previous), they can't release it as it will have the same name.
ADC does work properly, but number of channels is still limited. 4 on the 60-pin chip, 8 on 80-pin. For comparison STM32G431 has 11 channels on 32-pin and 18 on 48-pin.
I'd prefer more ADC pins too. Apparently they fixed the non-linearity problem (4 big spikes in the values) but there's still only 3 ADC pins wired to header pins, like on the original Pico.
yeah saying stuffs like "promising applications" at 2:15 is really an understatement when most manufacturers even westerners switched at least partially to RiscV cores. Being ARM based, this is probably just an integrated isa interpreter to make the chip compatible to RV code. probably better to use ARM assembler directly.
I wonder if the RISC-V cores were added due to the die area required for bumps (im assuming its flip-chip) meaning there was a load of free die space, so they just chucked a couple extra cores in Edit: looked at die shots of rp2040 and it seems to be bond wire, so probably same here.
the RP2040 is already way too powerful for this application. Some STM32F103 or even a good old ATmega32u4 can do the trick. Some people used a genuine Uno or even the bare Atmega16u2 alone… or an Atmega32 with v-usb bit banging.
@@PainterVierax it is too fancy with small screen for retro gaming, I am planning to tapout my own chip too with only risc-v cores and some custom instructions. I am not interested in any non-riscv chips anyways :p
as i see, this board based on 2350A, and not have huge GPIO pins as in 2350B chip. i waiting stamp-xl on 2350B, and all my future projects pcb has waiting 2350B chips.
Looks like another case where I'll wait for other implementers... even the CHINESE! to make a better version of the actual board. RPi can't design a useful carrier board to save themselves. Noisy switching PSU, micro-usb connector, no reset switch... geez.
There are still enough microUSB Cable laying around and compatibility with the pico1 is worth a lot. I like USB-C but i don‘t see any advantage here, solder yourself if you want to😅
@@Buchstabenkrahn well, you'll need to dedicate a cable for your devboards, and probably for most project you build with them so better get inexpensive older connector. Personally, I use USB-B full size for such microcontroller projects as it's sturdy and plenty enough current and bandwidth for such applications. Unfortunately Rpi Pico doesn't come with pins or pads to expose the USB lines. Though like most devboards, it's better to make our own PCB to get access to every available i/o.
What idiotic naming scheme, that will resault i fewer upgrades. 512kb RAM id a joke and now we gave to wait like 5 years for a new upgrade, thanks to the idiotic naming convention.
I don't get it. You can't buy the microcontroller by itself, just this dev board so how would it actually slot into a product development environment? It seems like it's just for hobbyists to make projects. And why would anyone use it over an STM32?
