WEBVTT

00:00:00.000 --> 00:00:01.440
<v Raspberry Pi>This is The Amp Hour Podcast.

00:00:03.000 --> 00:00:05.540
<v Raspberry Pi>Release February 7th, 2021.

00:00:08.060 --> 00:00:09.540
<v Raspberry Pi>Episode 529.

00:00:11.760 --> 00:00:13.800
<v Raspberry Pi>Embedded hardware with the Raspberry Pi team.

00:00:30.000 --> 00:00:33.480
<v Chris Gammell>Welcome to the Amp Hour. I'm Chris Gammell of Contextual Electronics.

00:00:34.140 --> 00:00:38.460
<v Chris Gammell>And I'm James Adams, COO and Hardware Lead at Raspberry Pi Trading.

00:00:38.860 --> 00:00:41.880
<v Liam Fraser>I'm Liam Fraser, an Engineer at Raspberry Pi Trading.

00:00:42.300 --> 00:00:45.060
<v Luke Renn>I'm Luke Renn. I'm a Hardware Engineer at Raspberry Pi Trading.

00:00:45.380 --> 00:00:48.760
<v Raspberry Pi>Welcome, guys. The Raspberry Pi Hardware Team, or some portion of it.

00:00:49.180 --> 00:00:51.420
<v Raspberry Pi>So let's first talk, what is Raspberry Pi Trading?

00:00:51.480 --> 00:00:53.480
<v Raspberry Pi>I've heard Raspberry Pi Foundation before.

00:00:53.660 --> 00:00:55.860
<v Raspberry Pi>What is Raspberry Pi Trading versus Foundation?

00:00:56.200 --> 00:00:57.620
<v Raspberry Pi>How does that all fit together?

00:00:57.620 --> 00:01:02.220
<v Chris Gammell>Okay, so the brief synopsis is that the Foundation is the charity,

00:01:02.560 --> 00:01:05.360
<v Chris Gammell>and we are basically a subsidiary of the charity.

00:01:05.680 --> 00:01:09.960
<v Chris Gammell>So we're the technical side, the technical team that designs all of the products,

00:01:10.120 --> 00:01:13.020
<v Chris Gammell>as opposed to the guys who do the outreach so much.

00:01:13.420 --> 00:01:14.900
<v Raspberry Pi>Great. Okay. Yeah, that's really cool.

00:01:15.460 --> 00:01:18.940
<v Chris Gammell>You can just imagine us like a typical kind of technology company.

00:01:19.300 --> 00:01:21.340
<v Chris Gammell>We're just owned by the Foundation.

00:01:22.300 --> 00:01:25.760
<v Raspberry Pi>Okay. Yeah, and I mean, I feel like sometimes even just

00:01:25.760 --> 00:01:30.040
<v Raspberry Pi>knowing like non-US corporations, I get confused.

00:01:30.220 --> 00:01:33.220
<v Raspberry Pi>So it's good to understand that kind of how that's all set up.

00:01:33.300 --> 00:01:34.340
<v Raspberry Pi>That's really cool.

00:01:34.420 --> 00:01:37.480
<v Raspberry Pi>Well, first off, I'm very excited to have you guys here.

00:01:37.660 --> 00:01:40.920
<v Raspberry Pi>I'm very excited about the new Compute Module 4.

00:01:41.480 --> 00:01:44.420
<v Raspberry Pi>I am excited about the RP2040 and the Pico board.

00:01:44.540 --> 00:01:46.660
<v Raspberry Pi>So I'm generally very excited here.

00:01:46.660 --> 00:01:50.520
<v Raspberry Pi>So let's get started with the RP2040.

00:01:50.720 --> 00:01:54.140
<v Raspberry Pi>So this is the new microcontroller, microprocessor.

00:01:54.400 --> 00:01:56.340
<v Raspberry Pi>Well, that's what Dave was all on about last time.

00:01:56.380 --> 00:01:57.320
<v Raspberry Pi>I'll ask about that in a bit here.

00:01:57.380 --> 00:02:00.100
<v Raspberry Pi>But this is the new custom silicon from Raspberry Pi.

00:02:01.100 --> 00:02:02.220
<v Raspberry Pi>I'm just going to say generally.

00:02:02.560 --> 00:02:05.480
<v Raspberry Pi>What is the genesis of the RP2040?

00:02:06.340 --> 00:02:07.260
<v Chris Gammell>Who's going to answer that one?

00:02:08.960 --> 00:02:10.020
<v Chris Gammell>Perhaps that one's for me.

00:02:10.020 --> 00:02:16.820
<v Chris Gammell>So genesis, it's difficult to put a finger on when exactly we decided to do it.

00:02:17.100 --> 00:02:18.060
<v Raspberry Pi>I think it's been a...

00:02:18.060 --> 00:02:18.420
<v Raspberry Pi>Right, right.

00:02:18.800 --> 00:02:24.320
<v Raspberry Pi>Is it like when you cut the check to the fab or is it like when you dream it up or like what happened?

00:02:24.380 --> 00:02:28.780
<v Chris Gammell>Well, I think for a long time, we have been interested in the microcontroller space.

00:02:29.300 --> 00:02:31.700
<v Chris Gammell>And we've always wanted to do something in that space.

00:02:32.340 --> 00:02:34.540
<v Chris Gammell>It's kind of a natural fit for what we do.

00:02:34.540 --> 00:02:40.880
<v Chris Gammell>But we also are very aware that there are other people in the space doing good things.

00:02:41.500 --> 00:02:45.960
<v Chris Gammell>And if we were ever going to enter that space, we need to come up with something that was quite differentiated.

00:02:46.460 --> 00:02:48.920
<v Chris Gammell>And of course, we also wanted to build something that was low cost.

00:02:49.140 --> 00:02:54.000
<v Chris Gammell>So in everything we do, we try and make things low cost so that it's accessible for people.

00:02:54.520 --> 00:03:01.460
<v Chris Gammell>And these days, we also build stuff for industry and sort of real work, if you like, as well as for education.

00:03:01.460 --> 00:03:06.060
<v Chris Gammell>So, you know, there was an idea there for quite some time, I think.

00:03:06.460 --> 00:03:11.620
<v Chris Gammell>And I guess at the end of 2016, we sort of started kicking it off.

00:03:12.120 --> 00:03:21.160
<v Chris Gammell>And we worked through various iterations of sort of design and test to come up with what we have today.

00:03:21.280 --> 00:03:23.220
<v Chris Gammell>So, you know, it wasn't a fully formed thing at the beginning.

00:03:23.380 --> 00:03:25.120
<v Chris Gammell>It was, hey, let's try this out.

00:03:25.200 --> 00:03:25.960
<v Chris Gammell>Let's see what we can do.

00:03:26.040 --> 00:03:29.860
<v Chris Gammell>And we've evolved it as we've gone along into what we've ended up with today.

00:03:29.860 --> 00:03:31.620
<v Raspberry Pi>Yeah, that's great.

00:03:31.740 --> 00:03:35.360
<v Raspberry Pi>I mean, that's a longer timeline that I expect, but it's also shorter.

00:03:35.520 --> 00:03:35.800
<v Raspberry Pi>You know what I mean?

00:03:35.860 --> 00:03:40.760
<v Raspberry Pi>Like 2016 feels like, I don't actually know how long a chip kind of takes, you know.

00:03:41.160 --> 00:03:42.260
<v Raspberry Pi>Like, I don't actually know.

00:03:42.360 --> 00:03:45.300
<v Raspberry Pi>Like, when does the meaty kind of development actually start then?

00:03:45.880 --> 00:03:46.100
<v Chris Gammell>Yeah.

00:03:46.240 --> 00:03:50.320
<v Chris Gammell>I mean, I'll let Luke and Liam talk a bit more about the development side of it.

00:03:50.320 --> 00:03:54.680
<v Chris Gammell>But I guess back at the end of 2016, we were just starting to talk about it.

00:03:54.760 --> 00:04:00.360
<v Chris Gammell>And it probably took a good six months before we even started doing any real kind of solid engineering on it, if you like.

00:04:00.600 --> 00:04:04.560
<v Chris Gammell>So at the beginning, you have to go out and say, well, hey, what processor call do we want?

00:04:04.640 --> 00:04:07.340
<v Chris Gammell>What's the sort of what kind of architecture do we think we're going to have?

00:04:07.340 --> 00:04:08.740
<v Chris Gammell>And where do we get the IP from?

00:04:09.080 --> 00:04:10.540
<v Chris Gammell>Which bits are we going to develop ourselves?

00:04:10.540 --> 00:04:15.940
<v Chris Gammell>And, you know, you've got to sign a bunch of NDAs and you've got to get a bunch of contracts for IP and, you know, look over all this stuff.

00:04:16.040 --> 00:04:24.000
<v Chris Gammell>So there was a lot of that going on for a good while before we actually sat down and did anything engineering-y, if you like, apart from the kind of top level.

00:04:24.920 --> 00:04:24.960
<v Raspberry Pi>Right.

00:04:25.040 --> 00:04:30.760
<v Raspberry Pi>I think the big thing is that, like, from the outsider perspective, right, you know, one day I don't know anything about it.

00:04:30.760 --> 00:04:33.960
<v Raspberry Pi>And then the next day we hear about the, you know, the chip being out there.

00:04:34.080 --> 00:04:35.860
<v Raspberry Pi>And obviously you guys launched everything all at once.

00:04:35.980 --> 00:04:37.900
<v Raspberry Pi>And so it was just like, oh, wow, this thing popped out of nowhere.

00:04:37.900 --> 00:04:41.660
<v Raspberry Pi>But very obviously that is not how chip development works.

00:04:41.780 --> 00:04:43.400
<v Raspberry Pi>So, yeah, there's a lot going into it.

00:04:44.380 --> 00:04:47.160
<v Raspberry Pi>What was the, I mean, so we have the RP2040.

00:04:47.360 --> 00:04:49.740
<v Raspberry Pi>We talked about it a little bit on the last episode.

00:04:50.340 --> 00:04:53.220
<v Raspberry Pi>But thinking about, like, actually implementing it on a board then.

00:04:53.300 --> 00:04:55.480
<v Raspberry Pi>I mean, that's what you guys have been working towards as well.

00:04:56.280 --> 00:04:58.500
<v Raspberry Pi>The Pico is the main offering there.

00:04:58.660 --> 00:05:02.640
<v Raspberry Pi>Like, what is the thought process around what you expect that to do?

00:05:02.720 --> 00:05:04.080
<v Raspberry Pi>Like, why the Pico?

00:05:04.180 --> 00:05:04.980
<v Raspberry Pi>Why that form factor?

00:05:05.440 --> 00:05:06.380
<v Chris Gammell>Okay, I guess that's me again.

00:05:06.380 --> 00:05:09.060
<v Chris Gammell>So it's cost engineered.

00:05:09.480 --> 00:05:14.600
<v Chris Gammell>I mean, the principal kind of driver, I guess, for this has always been cost.

00:05:14.720 --> 00:05:19.700
<v Chris Gammell>What we can do in a very, very low, few dollar kind of envelope, if you like.

00:05:20.780 --> 00:05:22.980
<v Chris Gammell>And dip form factor.

00:05:23.200 --> 00:05:24.120
<v Chris Gammell>That was a big thing.

00:05:24.520 --> 00:05:26.720
<v Chris Gammell>I think that, well, I was pretty keen on it.

00:05:26.720 --> 00:05:31.080
<v Chris Gammell>And I also wanted it to be kind of modular usable.

00:05:31.340 --> 00:05:33.520
<v Chris Gammell>So it's kind of a component in itself.

00:05:33.520 --> 00:05:40.600
<v Chris Gammell>So you could take it, build it into products and projects, even into serious ones that you want to go sell somewhere.

00:05:40.600 --> 00:05:44.080
<v Chris Gammell>Because, hey, people build Raspberry Pi into a lot of things.

00:05:44.080 --> 00:05:45.920
<v Chris Gammell>We've seen this happen a lot.

00:05:46.420 --> 00:05:50.400
<v Chris Gammell>So building something that's actually able to, you know, to be used in that way is good.

00:05:50.400 --> 00:05:55.920
<v Chris Gammell>And so the kind of the form factor, there was always a sort of idea to do a dip-like form factor.

00:05:55.920 --> 00:06:00.880
<v Chris Gammell>And it kind of evolved from the work we did on the pinout of the chip.

00:06:01.640 --> 00:06:05.640
<v Chris Gammell>Because, you know, it takes a lot of iteration to make sure the pins are all in a sensible order.

00:06:05.820 --> 00:06:15.680
<v Chris Gammell>And having a board to do that with, we sort of co-designed the board layout and the chip pinout to make sure it's both easy to do for everybody else, but also for our own product.

00:06:15.680 --> 00:06:19.340
<v Chris Gammell>And that's where the pinouts kind of come from, I guess.

00:06:19.560 --> 00:06:22.620
<v Chris Gammell>And really the rest of it's just like, how small can we make the PCB?

00:06:23.080 --> 00:06:24.020
<v Chris Gammell>How many pins do we need?

00:06:24.060 --> 00:06:25.220
<v Chris Gammell>Because we've got this many IOs.

00:06:25.420 --> 00:06:27.380
<v Chris Gammell>We want a really simple power chain, but flexible.

00:06:27.780 --> 00:06:30.840
<v Chris Gammell>And so all of that came together into the Pico, right?

00:06:30.900 --> 00:06:31.780
<v Chris Gammell>So it's a two-layer board.

00:06:31.980 --> 00:06:34.320
<v Chris Gammell>It's got a simple yet very flexible power chain.

00:06:35.040 --> 00:06:38.280
<v Chris Gammell>And it's single, you know, single side surface mount.

00:06:38.860 --> 00:06:40.060
<v Chris Gammell>Easy to automate.

00:06:40.240 --> 00:06:41.000
<v Chris Gammell>It's easy to package.

00:06:41.180 --> 00:06:43.520
<v Chris Gammell>So therefore, you know, as low cost as we can make it.

00:06:44.260 --> 00:06:44.800
<v Raspberry Pi>That's great.

00:06:44.800 --> 00:06:46.500
<v Raspberry Pi>And so maybe we can dive right in then.

00:06:46.640 --> 00:06:50.340
<v Raspberry Pi>So the PIO is something that's been called out as a very interesting feature.

00:06:50.440 --> 00:06:52.320
<v Raspberry Pi>Can you guys kind of talk through what that is up front?

00:06:52.860 --> 00:06:53.040
<v Luke Renn>Yeah.

00:06:53.300 --> 00:06:58.820
<v Luke Renn>So PIO started in summer 17 during my internship.

00:06:59.180 --> 00:07:09.280
<v Luke Renn>There's been an idea kicking around since the 60s of having something that is programmable, like a processor, but is very stripped down and specialized to IO.

00:07:09.280 --> 00:07:15.400
<v Luke Renn>So you can have things like FPGAs on board your microcontroller, but they have a high area and power overhead.

00:07:15.400 --> 00:07:19.660
<v Luke Renn>And they tend to be quite a steep learning curve to program for software engineers.

00:07:19.660 --> 00:07:27.100
<v Luke Renn>One of the big things we wanted to do with this chip was make it as low cost as possible whilst having as much memory as possible.

00:07:27.540 --> 00:07:30.500
<v Luke Renn>And that forces you to outboard a lot of your analog hardware.

00:07:31.300 --> 00:07:34.780
<v Luke Renn>It forces you to have as few pads as you can get away with.

00:07:35.040 --> 00:07:39.720
<v Luke Renn>And that means you need to be as good as possible at serial IO with things on your board.

00:07:39.720 --> 00:07:48.500
<v Luke Renn>So we set out to make something that you talk to, like a regular serial peripheral, like an SPI, UART and I2C, but you can program to do other things as well.

00:07:48.840 --> 00:07:55.040
<v Luke Renn>We've posted some demos online of doing things like VGA, I2S, SD cards, even DVI.

00:07:55.520 --> 00:08:02.080
<v Luke Renn>And it's quite flexible, but it has around the same area and power overhead as a regular serial peripheral.

00:08:02.080 --> 00:08:12.740
<v Raspberry Pi>Great. Yeah. So the thinking is just that it's really, again, for that optimization for the super low cost because you're offloading a bunch of the processing.

00:08:13.480 --> 00:08:28.160
<v Luke Renn>Right. So it is programmable in the sense of a processor, but it's much more of a focus on being very deterministic, being very good at toggling pins, but not for doing arithmetic because that's the job of the processors in the system.

00:08:28.160 --> 00:08:43.060
<v Raspberry Pi>And then, I mean, so people can go check out the demos and things like that. I mean, how extensible do you expect this to be? I mean, so you've shown the DVI, the VGA, things like that. What do you think the limits are of using a peripheral like that?

00:08:43.480 --> 00:08:49.840
<v Luke Renn>The limits come in when you have very complex protocols with very tight timing turnarounds that you need to offload onto software.

00:08:49.840 --> 00:09:03.240
<v Luke Renn>So if you have some really complex and unusual checksum or something like USB where you have very tight bounds on the responses, then because PIO is meant to do just the bit banging part and you're meant to offload the rest onto software, at that point you do hit some limitations.

00:09:04.040 --> 00:09:13.560
<v Luke Renn>But for any strange serial line format or something like that, it should be pretty flexible. We've got examples for, you know, your classic Manchester serial, differential Manchester, all those kinds of things.

00:09:13.560 --> 00:09:30.380
<v Raspberry Pi>Cool. Okay. Yeah, that's great. That's great. I mean, more broadly too, I mean, so Raspberry Pi always has like a educational bent. One thing that I was trying to verbalize when we were talking about this last week was like thinking about how this might impact the educational side of things.

00:09:30.380 --> 00:09:37.820
<v Raspberry Pi>Do you see that like, are you expecting that people will be using this in an educational context or how do you think it will be?

00:09:38.680 --> 00:09:45.980
<v Luke Renn>Yeah, I mean, we did set out to build a useful general purpose microcontroller, but I think there is a lot of educational benefit in the platform.

00:09:46.400 --> 00:09:51.360
<v Luke Renn>I mean, we've worked really hard on making the documentation as thorough and easy to read and as transparent as possible.

00:09:52.100 --> 00:09:57.340
<v Luke Renn>I think that there's a lot of educational value in having a dual core system that fits onto one lecture slide.

00:09:57.340 --> 00:10:03.720
<v Luke Renn>And I think PIO lets people explore IO in quite an interesting and tactile way as well.

00:10:04.600 --> 00:10:13.780
<v Raspberry Pi>Yeah, I mean, the other interesting thing, I've seen a lot of people kind of like raving over the, you know, the MicroPython integration there and just like the easy boot side of things.

00:10:13.940 --> 00:10:19.940
<v Raspberry Pi>What is then the software firmware integration side of things as well?

00:10:20.020 --> 00:10:23.580
<v Raspberry Pi>I mean, like, what are your expectations for how people will start using this thing?

00:10:23.580 --> 00:10:32.760
<v Luke Renn>Sure. I mean, I think we all believe at Py that MicroPython and things like it, like CircuitPython, like NodeMCU, are serious tools for embedded software.

00:10:33.260 --> 00:10:36.920
<v Luke Renn>They're more accessible than, you know, bare metal C.

00:10:37.100 --> 00:10:38.720
<v Luke Renn>They do have some higher runtime requirements.

00:10:39.080 --> 00:10:44.740
<v Luke Renn>And that's one of the reasons we set out to build a system that offers as much SRAM as possible at the lowest possible cost.

00:10:44.740 --> 00:10:54.300
<v Luke Renn>It's because we think part of the reason things like MicroPython aren't used in, let's say, more serious embedded contexts is because of the cost that comes with those runtime requirements.

00:10:55.420 --> 00:11:03.340
<v Luke Renn>So we think that MicroPython is a much better entryway into embedded programming than things based on embedded C and C++.

00:11:03.340 --> 00:11:10.740
<v Luke Renn>And we've really tried to push that and get that entry as slick as possible with the drag and drop programming and the boot rom and things like that.

00:11:11.740 --> 00:11:12.180
<v Raspberry Pi>Yeah.

00:11:12.580 --> 00:11:13.000
<v Raspberry Pi>Yeah.

00:11:13.000 --> 00:11:29.760
<v Raspberry Pi>One thing that's exciting about it all for me is just like, so assuming that there's an accessible programming interface like that, I mean, it feels like the processing side is, if you ignore battery, you know, battery type applications, it's very obvious now.

00:11:29.760 --> 00:11:32.980
<v Raspberry Pi>You know, you have 133 megahertz dual core processor on here.

00:11:33.820 --> 00:11:38.540
<v Raspberry Pi>Like the computing is just so cheap compared to what it has been historically.

00:11:38.540 --> 00:11:46.540
<v Raspberry Pi>So like that then enables things that are maybe not super efficient, not super timing, tight, tight timing, like a, like a MicroPython.

00:11:46.660 --> 00:11:47.820
<v Raspberry Pi>But who cares at that point?

00:11:47.860 --> 00:11:50.040
<v Raspberry Pi>You know, like it's just, we have such a computing surplus.

00:11:50.160 --> 00:11:55.840
<v Luke Renn>A lot of people will come in and say things like, well, in this benchmark, I found that MicroPython is a hundred times slower than C.

00:11:55.840 --> 00:11:59.440
<v Luke Renn>But if you'll see codes a hundred times faster than you need, it doesn't matter.

00:12:00.180 --> 00:12:01.440
<v Luke Renn>You know, you just write the code that you need.

00:12:01.520 --> 00:12:05.080
<v Luke Renn>You focus on the parts that add value to your project and then you move on to the next project.

00:12:05.980 --> 00:12:06.100
<v Raspberry Pi>Yeah.

00:12:06.340 --> 00:12:06.500
<v Raspberry Pi>Yeah.

00:12:06.520 --> 00:12:09.920
<v Raspberry Pi>I feel like, especially like, okay, so it's a hundred times faster.

00:12:10.140 --> 00:12:11.940
<v Raspberry Pi>Does a school kid care about that?

00:12:12.220 --> 00:12:14.900
<v Raspberry Pi>I don't really, yeah.

00:12:15.020 --> 00:12:16.380
<v Raspberry Pi>I don't think that there's a ton of.

00:12:16.440 --> 00:12:16.540
<v Raspberry Pi>Yeah.

00:12:16.580 --> 00:12:20.020
<v Luke Renn>Like you can blink an LED at 30 megahertz and see, but it's not actually that useful.

00:12:21.140 --> 00:12:21.680
<v Raspberry Pi>That's right.

00:12:21.860 --> 00:12:22.280
<v Raspberry Pi>That's right.

00:12:22.980 --> 00:12:24.140
<v Raspberry Pi>Well, let's, let's take a step back.

00:12:24.140 --> 00:12:30.720
<v Raspberry Pi>I mean, so, so we've talked about Raspberry Pi trading, like, and you guys have mentioned your titles as well, but like, how are things split up there?

00:12:30.780 --> 00:12:34.040
<v Raspberry Pi>Like what, so, so James is, is the boss man.

00:12:35.340 --> 00:12:36.880
<v Raspberry Pi>Luke and Liam, you're both engineers.

00:12:36.880 --> 00:12:38.760
<v Raspberry Pi>Like how do, you know, what are your days to days look like?

00:12:39.320 --> 00:12:40.460
<v Liam Fraser>Maybe I can answer this.

00:12:41.000 --> 00:12:48.140
<v Liam Fraser>So at Pi, because we've got quite a small team, everyone tends to like not stay within one discipline.

00:12:48.140 --> 00:12:58.360
<v Liam Fraser>So probably me, especially compared to Luke, I joined with no, you know, hardware Verilog or like chip design knowledge at all.

00:12:58.580 --> 00:13:06.180
<v Liam Fraser>And I've sort of learned through, you know, the process of chip designs being going on and I've gone, oh, that's interesting.

00:13:06.320 --> 00:13:07.340
<v Liam Fraser>Can I do some of that?

00:13:07.340 --> 00:13:12.480
<v Liam Fraser>And now I'm sort of, you know, doing a lot of the like chip architecture work.

00:13:12.680 --> 00:13:19.720
<v Liam Fraser>So I would say sort of, it's, it's sort of split 50, 50 between hardware and software for me.

00:13:19.720 --> 00:13:34.000
<v Liam Fraser>And the nice thing about chip design is you can design some hardware and then write some software, run a simulation and it, and you can see your C code that you've just written running on the hardware that you've just designed, you know, as a way to verify it.

00:13:34.120 --> 00:13:38.020
<v Liam Fraser>So it's really nice to be able to like work from both sides.

00:13:38.560 --> 00:13:39.040
<v Liam Fraser>Yeah.

00:13:39.980 --> 00:13:40.420
<v Luke Renn>Yeah.

00:13:40.480 --> 00:13:44.020
<v Luke Renn>We, we tend not to silo engineers in one discipline so much.

00:13:44.020 --> 00:13:46.860
<v Luke Renn>And there are, we do have some really experienced ASIC folks.

00:13:46.860 --> 00:13:49.740
<v Luke Renn>So it was a great environment to learn and to learn that kind of thing.

00:13:50.280 --> 00:13:53.860
<v Luke Renn>I think there's a lot of value in owning both sides of an interface.

00:13:54.200 --> 00:14:03.220
<v Luke Renn>So whilst you're designing hardware, also thinking about the software interface to it and pushing complexity back and forth over that barrier to try and make something that was actually ergonomic to use.

00:14:04.540 --> 00:14:10.040
<v Chris Gammell>I mean, that's one thing that Raspberry Pi is very good at is doing that whole stack thing, right?

00:14:10.040 --> 00:14:16.680
<v Chris Gammell>So you can see it with the Pico where, you know, Luke and Liam have both been doing hardware and software.

00:14:17.460 --> 00:14:21.700
<v Chris Gammell>And, you know, I did the Pico board design and we can optimize the pinout.

00:14:21.820 --> 00:14:23.740
<v Chris Gammell>We can go backwards and forwards across the whole stack.

00:14:23.840 --> 00:14:24.080
<v Chris Gammell>Right.

00:14:24.240 --> 00:14:25.740
<v Chris Gammell>And including the documentation.

00:14:25.900 --> 00:14:26.840
<v Chris Gammell>I mean, look at the documentation.

00:14:26.840 --> 00:14:29.780
<v Chris Gammell>It's absolutely, you know, fantastic.

00:14:29.780 --> 00:14:37.200
<v Chris Gammell>You know, when we set out to do documentation, we didn't think it would be this good, although we obviously wanted it to be great.

00:14:37.740 --> 00:14:49.240
<v Chris Gammell>But that just shows, you know, a small team, a small team of really good people working on everything in a very flat structure, usually sitting next to each other in the office, although not so much now, at least not for the moment.

00:14:49.240 --> 00:14:52.560
<v Chris Gammell>And it can really, you know, really knock it out of the park, right?

00:14:52.840 --> 00:14:59.600
<v Chris Gammell>And people are, you know, we employ really good people and they're all conscientious and they're technically very good.

00:14:59.680 --> 00:15:05.220
<v Chris Gammell>And they all want to, they're all aligned to the same goal of producing, you know, something really good.

00:15:05.640 --> 00:15:06.880
<v Chris Gammell>And everyone has fun doing it.

00:15:07.840 --> 00:15:10.140
<v Chris Gammell>And so, yeah, so Pi is very, very flat structured.

00:15:10.140 --> 00:15:17.360
<v Chris Gammell>You know, it's basically sort of Ebon at the top of trading and then me and Gordon and a couple of other guys and then the engineers.

00:15:17.360 --> 00:15:28.880
<v Chris Gammell>And largely my job these days, at least, although I do still do quite a lot of engineering, is to make the engineers' lives easier and sort of get out of the way and let them do their thing, right?

00:15:29.000 --> 00:15:30.420
<v Chris Gammell>So, yeah.

00:15:31.640 --> 00:15:32.240
<v Raspberry Pi>That's great.

00:15:32.520 --> 00:15:43.300
<v Raspberry Pi>Yeah, I mean, that push and pull like from software and like that full stack idea, it feels like that's almost required at the volumes and the cost targets you guys are shooting towards.

00:15:43.300 --> 00:15:47.480
<v Raspberry Pi>I mean, how does the super low cost focus end up impacting things?

00:15:48.320 --> 00:15:53.660
<v Chris Gammell>So, do you mean how do we make it low cost or what challenges does that present?

00:15:54.300 --> 00:15:54.880
<v Chris Gammell>Or both, I guess.

00:15:55.080 --> 00:15:56.980
<v Raspberry Pi>Yeah, I think probably the latter.

00:15:57.160 --> 00:15:59.940
<v Raspberry Pi>But I mean, yeah, I mean, then how do you do it?

00:16:00.000 --> 00:16:05.700
<v Raspberry Pi>I mean, some of it is like I would feel like on the marketing side, like people are interested in it enough that they're buying it.

00:16:05.700 --> 00:16:10.180
<v Raspberry Pi>And there's enough of a price incentive for people to be very interested and obviously it's good products.

00:16:10.180 --> 00:16:16.480
<v Raspberry Pi>Like all those things end up driving towards a highly available, you know, thing that drives down the cost.

00:16:16.620 --> 00:16:18.660
<v Raspberry Pi>So, that's one thing that I kind of take as a given.

00:16:19.160 --> 00:16:26.960
<v Raspberry Pi>But really, I think about the decision-making process that you have to go through then in order to then maintain that super low cost focus.

00:16:26.960 --> 00:16:31.980
<v Raspberry Pi>It's like how does – and some of it even being the long-term focus, right?

00:16:32.000 --> 00:16:38.340
<v Raspberry Pi>Because if I go and say – so, I start a board tomorrow and I say, hey, look, I'm going to sell 10 million of these units.

00:16:38.640 --> 00:16:43.380
<v Raspberry Pi>I go and engage Broadcom and try and encourage them that I'm going to sell 10 million units.

00:16:43.500 --> 00:16:44.780
<v Raspberry Pi>They should give me a chip at this price.

00:16:44.840 --> 00:16:51.740
<v Raspberry Pi>All of these different things that had to happen in order for the original Raspberry Pi to happen and now these other additional products.

00:16:51.740 --> 00:16:54.680
<v Raspberry Pi>It just – it feels like – it feels insane to me.

00:16:54.920 --> 00:16:58.220
<v Raspberry Pi>But you guys have navigated that and done it and executed on it.

00:16:58.300 --> 00:17:00.640
<v Raspberry Pi>So, how does that end up impacting things internally?

00:17:01.040 --> 00:17:01.100
<v Chris Gammell>Okay.

00:17:01.460 --> 00:17:05.620
<v Chris Gammell>I guess we are now in a pretty lucky position that we have this really strong brand.

00:17:06.060 --> 00:17:14.460
<v Chris Gammell>And we've learned as a company, as a team, how to build, you know, high-quality products at scale.

00:17:14.980 --> 00:17:18.160
<v Chris Gammell>So, something like the Pico is actually ignoring the chip side, right?

00:17:18.200 --> 00:17:20.540
<v Chris Gammell>Because that is difficult and that costs a lot of money for the development.

00:17:20.540 --> 00:17:28.560
<v Chris Gammell>But on the rest of it, the sort of board build and test, we know the guys who can do this stuff at scale.

00:17:29.020 --> 00:17:32.040
<v Chris Gammell>We know how to build test systems, automated test systems.

00:17:32.160 --> 00:17:33.500
<v Chris Gammell>So, the Pico is fully automated.

00:17:33.960 --> 00:17:37.240
<v Chris Gammell>Well, right now we've actually got people putting stuff in test sockets still.

00:17:37.360 --> 00:17:39.340
<v Chris Gammell>But very soon it's going to be robots only, right?

00:17:39.460 --> 00:17:41.380
<v Chris Gammell>So, you saw all components at one end.

00:17:41.380 --> 00:17:51.860
<v Chris Gammell>It all gets automatically built, surface-mounted, depaneled by robots, put in a jig by robots, tested by robots, packaged by robots.

00:17:52.000 --> 00:17:53.800
<v Chris Gammell>And then reels come out the other side.

00:17:54.660 --> 00:17:56.060
<v Raspberry Pi>Man, we're living in the future, guys.

00:17:56.220 --> 00:17:56.520
<v Raspberry Pi>I don't know.

00:17:56.660 --> 00:18:03.320
<v Chris Gammell>When you take the humans out, the cost goes right down in terms of that kind of build and test side of it.

00:18:03.320 --> 00:18:09.120
<v Chris Gammell>But we also have good relationships with a lot of electronic suppliers, a lot of the development work for Pico.

00:18:09.260 --> 00:18:15.920
<v Chris Gammell>I spent a lot of time talking to different guys to pick the right, even though there's only about 40 components on it, like find the right switcher.

00:18:16.680 --> 00:18:20.780
<v Chris Gammell>We went around the loop with various companies, tried to find the right price.

00:18:21.440 --> 00:18:22.100
<v Chris Gammell>Everything's priced.

00:18:22.260 --> 00:18:23.420
<v Chris Gammell>We care about the cents.

00:18:23.420 --> 00:18:28.340
<v Chris Gammell>We even have metrics for how many placements, what's the cost of a placement, right?

00:18:28.420 --> 00:18:30.360
<v Chris Gammell>So, actually reducing placements even saves you money.

00:18:30.500 --> 00:18:32.080
<v Chris Gammell>So, we're kind of at that level, right?

00:18:32.340 --> 00:18:35.740
<v Chris Gammell>And this is what we do day in, day out for all of the products because we have to.

00:18:36.160 --> 00:18:37.320
<v Chris Gammell>And we're just very good at it.

00:18:37.660 --> 00:18:39.400
<v Chris Gammell>So, we're very sort of diligent.

00:18:39.760 --> 00:18:44.240
<v Chris Gammell>We like to come up with simple yet effective hardware.

00:18:45.060 --> 00:18:46.720
<v Chris Gammell>And that's kind of the challenge, right?

00:18:46.760 --> 00:18:47.120
<v Chris Gammell>It's fun.

00:18:48.140 --> 00:18:48.540
<v Chris Gammell>Yeah.

00:18:48.540 --> 00:18:48.620
<v Chris Gammell>Yeah.

00:18:48.900 --> 00:18:55.800
<v Raspberry Pi>And I'd imagine now, too, that, I mean, does that same cost basis then push itself back into the silicon now that you're making custom silicon as well?

00:18:56.680 --> 00:18:57.540
<v Chris Gammell>It will do.

00:18:58.020 --> 00:19:01.060
<v Chris Gammell>I mean, we're kind of just getting started in this space.

00:19:01.060 --> 00:19:05.280
<v Chris Gammell>So, we won't be getting the best prices for things, for sure.

00:19:05.720 --> 00:19:08.120
<v Chris Gammell>I mean, we have a good brand, so people are keen to work with us.

00:19:08.900 --> 00:19:18.440
<v Chris Gammell>So, it's about, you know, over time, doing the same thing we've done in the electronics board space, in the silicon space, learning where the fat is, learning how to make things more efficient.

00:19:18.540 --> 00:19:19.320
<v Chris Gammell>To take cost out.

00:19:19.900 --> 00:19:23.920
<v Chris Gammell>So, I think the cost for the devices we've got at the moment is pretty good.

00:19:24.200 --> 00:19:25.860
<v Chris Gammell>It's certainly completely sustainable.

00:19:26.320 --> 00:19:30.840
<v Chris Gammell>The only reason supply is limited at the moment is just because we're sort of ramping, right?

00:19:30.960 --> 00:19:37.460
<v Chris Gammell>So, but the automated build system and all the rest of this stuff is all built so that we can run at extremely high run rates.

00:19:37.460 --> 00:19:39.640
<v Chris Gammell>So, everyone who wants a Pico can buy a Pico, right?

00:19:39.760 --> 00:19:46.020
<v Chris Gammell>And hopefully, they'll be fully available at the $4 cost everywhere, you know, fairly soon.

00:19:46.800 --> 00:19:47.520
<v Raspberry Pi>Yeah, right.

00:19:47.700 --> 00:19:47.880
<v Raspberry Pi>Right.

00:19:47.880 --> 00:19:48.440
<v Raspberry Pi>And that's tough, too.

00:19:48.520 --> 00:19:49.040
<v Raspberry Pi>Like, setting that.

00:19:49.240 --> 00:19:53.520
<v Raspberry Pi>That's one thing that's always been interesting with Raspberry Pi of, like, setting a price first.

00:19:54.060 --> 00:20:02.140
<v Raspberry Pi>And then it's like, everything else works around that versus being like, well, we're going to offer it at our two distributors at, you know, X price.

00:20:02.140 --> 00:20:08.560
<v Raspberry Pi>And they're probably going to offer it at 1.5 X price or some multiple of X in order to make their own margins work.

00:20:08.560 --> 00:20:19.480
<v Raspberry Pi>But it's like, that isn't necessarily what happens because of the branding around, you know, $35 Linux computer, $4 Pico, those sort of things.

00:20:20.000 --> 00:20:20.060
<v Chris Gammell>Yeah.

00:20:20.060 --> 00:20:22.440
<v Chris Gammell>I mean, we have sustainable margins, right?

00:20:22.500 --> 00:20:24.500
<v Chris Gammell>But they're lower than most people.

00:20:25.300 --> 00:20:33.040
<v Chris Gammell>And our network of resellers and our, you know, RS and Farnell and the guys who sell our product know the deal now, right?

00:20:33.040 --> 00:20:37.380
<v Chris Gammell>And actually, it's part of the brand, as you say, to keep these prices low.

00:20:37.440 --> 00:20:38.060
<v Chris Gammell>It's what we do.

00:20:38.460 --> 00:20:39.940
<v Chris Gammell>It actually helps with the scale, right?

00:20:39.980 --> 00:20:40.980
<v Chris Gammell>Because these things are cheaper.

00:20:41.060 --> 00:20:41.900
<v Chris Gammell>We can make more of them.

00:20:42.040 --> 00:20:45.320
<v Chris Gammell>Because we make more of them, we can get better pricing.

00:20:45.320 --> 00:20:47.840
<v Chris Gammell>And, you know, we can implement all this automated.

00:20:48.260 --> 00:20:48.460
<v Chris Gammell>Yeah, it feeds back on itself, right?

00:20:48.460 --> 00:20:51.240
<v Chris Gammell>Yeah, it's just a big feedback loop and actually improves the quality, right?

00:20:51.340 --> 00:21:03.400
<v Chris Gammell>So the products we have, you know, we know because we build millions of most of them that they are, you know, they're good quality and have, you know, good sort of error rates or defect rates, right?

00:21:03.540 --> 00:21:05.280
<v Raspberry Pi>So what about the pricing then?

00:21:05.460 --> 00:21:07.260
<v Raspberry Pi>So Dave and I kind of talked about this last week as well.

00:21:07.260 --> 00:21:10.780
<v Raspberry Pi>Like the pricing then, okay, now I buy a $4 Pico.

00:21:10.900 --> 00:21:11.580
<v Raspberry Pi>I'm like, this is great.

00:21:11.640 --> 00:21:14.060
<v Raspberry Pi>I'm going to just solder this down with the castellated edges to my board.

00:21:14.060 --> 00:21:16.240
<v Raspberry Pi>There's going to be a higher cost there.

00:21:16.340 --> 00:21:17.520
<v Raspberry Pi>How is that cost determined?

00:21:17.680 --> 00:21:20.900
<v Raspberry Pi>I mean, is that now kind of at the will of the distributors?

00:21:21.120 --> 00:21:26.300
<v Raspberry Pi>Or what determines that price when I say, oh, Pico works fine for my production?

00:21:27.280 --> 00:21:31.420
<v Chris Gammell>Oh, do you mean do we control the price of a widget that someone's built that uses a Pico?

00:21:33.080 --> 00:21:41.900
<v Raspberry Pi>No, more on the, there's like a promotional educational price, low volumes, single volume type price where it's held down and you can't necessarily buy.

00:21:41.900 --> 00:21:45.640
<v Raspberry Pi>You can't buy 10,000 of something at the distributor price.

00:21:46.060 --> 00:21:47.640
<v Raspberry Pi>Maybe the distributors are holding that down.

00:21:47.720 --> 00:21:54.840
<v Raspberry Pi>But like what then determines the volume pricing of a CM4 or a Pico or RP2040?

00:21:56.020 --> 00:22:00.100
<v Chris Gammell>So the volume price, so the price we set for CM4 and Pico is the price that you'll pay.

00:22:00.560 --> 00:22:01.340
<v Chris Gammell>So that's the idea.

00:22:01.440 --> 00:22:07.240
<v Chris Gammell>We want to make it the same price for the guy who wants to buy 10 as the guy who wants to buy, you know, 10,000.

00:22:07.240 --> 00:22:10.100
<v Chris Gammell>And there should be no difference there, right?

00:22:10.600 --> 00:22:10.740
<v Raspberry Pi>Okay.

00:22:11.240 --> 00:22:16.240
<v Raspberry Pi>So, yeah, it's the one of the assertions that Dave thought was the, was that you would pay a higher price.

00:22:16.240 --> 00:22:19.900
<v Raspberry Pi>So like the first 10 or 20 were at the, you know, $4.

00:22:20.180 --> 00:22:24.580
<v Raspberry Pi>I'm just going to use a Pico here as an example, but you're going to pay that $4 price for the low volume stuff.

00:22:24.580 --> 00:22:28.840
<v Raspberry Pi>But then there's some step function, higher cost past that.

00:22:28.840 --> 00:22:32.260
<v Raspberry Pi>And then it goes into like distributor pricing where volume starts to kick in.

00:22:32.420 --> 00:22:34.600
<v Raspberry Pi>So that doesn't sound like that's actually the case.

00:22:34.600 --> 00:22:39.420
<v Chris Gammell>Note that the highest ever price you should pay for a Pico is $4, right?

00:22:39.520 --> 00:22:41.320
<v Chris Gammell>Plus tax, plus shipping, of course.

00:22:41.600 --> 00:22:53.080
<v Chris Gammell>But, you know, you should be able to buy, once we've got the production ramped up, you should be able to buy reels of 480 Pico boards, as many as you want, you know, for $4 a piece, you know, for $4 for each unit.

00:22:53.180 --> 00:22:53.300
<v Chris Gammell>Got it.

00:22:53.600 --> 00:22:54.140
<v Chris Gammell>That's the idea.

00:22:54.300 --> 00:22:56.600
<v Raspberry Pi>Same thing on the compute modules as well.

00:22:56.840 --> 00:22:59.360
<v Raspberry Pi>I mean, I know that there are different prices with different feature sets.

00:22:59.540 --> 00:23:00.240
<v Chris Gammell>That's the idea.

00:23:00.240 --> 00:23:00.280
<v Chris Gammell>Yeah.

00:23:00.360 --> 00:23:05.300
<v Chris Gammell>And I mean, if distributors want to give a volume discount, then they can.

00:23:06.660 --> 00:23:10.120
<v Chris Gammell>Some of them might do, but we kind of cap the maximum price, right?

00:23:10.600 --> 00:23:10.920
<v Chris Gammell>Got it.

00:23:10.980 --> 00:23:11.160
<v Raspberry Pi>Okay.

00:23:11.500 --> 00:23:11.920
<v Raspberry Pi>That's great.

00:23:11.980 --> 00:23:12.080
<v Raspberry Pi>Yeah.

00:23:12.160 --> 00:23:12.560
<v Raspberry Pi>No, that's great.

00:23:12.640 --> 00:23:15.780
<v Raspberry Pi>I think that we had a fundamental misunderstanding about that then.

00:23:15.780 --> 00:23:20.960
<v Raspberry Pi>I had thought that there was, you know, because there's limitations on how many you can buy at certain distributors.

00:23:21.120 --> 00:23:31.280
<v Raspberry Pi>I think some of that is just to hold down their own stock so that it's not like one person comes, swoops in, and buys out an entire run, and then that distributor gets stuck with like zero stock.

00:23:31.480 --> 00:23:35.580
<v Raspberry Pi>So they limit it more from a volume basis than a pricing basis.

00:23:35.780 --> 00:23:36.720
<v Raspberry Pi>And I misconstrued that.

00:23:36.720 --> 00:23:37.900
<v Raspberry Pi>Yeah, no, that's exactly right.

00:23:37.900 --> 00:23:44.080
<v Chris Gammell>At the moment, the distributors have turned their units per customer down just because they won't get enough stock.

00:23:44.180 --> 00:23:45.420
<v Chris Gammell>They'll just go out of stock in five minutes.

00:23:46.640 --> 00:23:47.380
<v Raspberry Pi>Yeah, yeah, yeah.

00:23:48.500 --> 00:23:49.120
<v Raspberry Pi>One question.

00:23:49.180 --> 00:23:52.340
<v Raspberry Pi>So I've been taking Twitter questions as well throughout the day.

00:23:52.640 --> 00:24:01.400
<v Raspberry Pi>One question someone, Chris, asks is, and this might apply to the Pico and the low cost, but why isn't there not a reset button on board?

00:24:01.820 --> 00:24:03.640
<v Raspberry Pi>So it has to be done via a pin?

00:24:03.980 --> 00:24:04.160
<v Chris Gammell>Is that right?

00:24:04.440 --> 00:24:04.660
<v Chris Gammell>Okay.

00:24:05.200 --> 00:24:06.260
<v Chris Gammell>Why isn't there a reset button?

00:24:06.580 --> 00:24:07.420
<v Chris Gammell>Because it costs money.

00:24:07.900 --> 00:24:10.060
<v Chris Gammell>There we are.

00:24:10.660 --> 00:24:10.920
<v Chris Gammell>Okay.

00:24:11.340 --> 00:24:11.460
<v Chris Gammell>Yeah.

00:24:11.460 --> 00:24:13.120
<v Chris Gammell>I mean, really, that's the short answer, right?

00:24:13.300 --> 00:24:15.480
<v Chris Gammell>Which one's more valuable, boot sell or reset?

00:24:15.620 --> 00:24:16.220
<v Chris Gammell>Well, boot sell.

00:24:16.640 --> 00:24:29.040
<v Chris Gammell>And I think we kind of think that if anyone's doing any long-term sort of more serious iteration of development, you should really learn how to use the serial Y debug port and get that all set up.

00:24:29.220 --> 00:24:31.580
<v Chris Gammell>And then you don't have to worry about your reset button.

00:24:31.620 --> 00:24:32.860
<v Chris Gammell>But it's easy enough to add one, right?

00:24:32.860 --> 00:24:42.680
<v Chris Gammell>I think there's been various videos and people posting stuff on Twitter about, you know, just basically get a button and short your 3v3 enable to ground or your run pin to ground.

00:24:42.680 --> 00:24:44.100
<v Chris Gammell>And that will do it for you.

00:24:44.460 --> 00:24:44.780
<v Luke Renn>That's great.

00:24:44.780 --> 00:24:45.220
<v Luke Renn>Yeah.

00:24:45.260 --> 00:24:49.140
<v Luke Renn>I mean, once you've got the debug set up, you can reset the cores, load code and all that stuff.

00:24:49.200 --> 00:24:49.840
<v Luke Renn>It's all very slick.

00:24:49.960 --> 00:24:56.020
<v Luke Renn>I think people will see the four pages of instructions to get the debug set up and they kind of just go to use the USB bootloader.

00:24:56.200 --> 00:24:58.040
<v Luke Renn>Once you've got the debug set up, it's pretty slick.

00:24:58.680 --> 00:25:03.100
<v Luke Renn>We are looking at options to make it easier for people who want to just stay with the USB bootloader.

00:25:03.100 --> 00:25:07.480
<v Luke Renn>One of them is the ability to reset the board over USB when the USB serial is attached.

00:25:07.760 --> 00:25:08.940
<v Luke Renn>So you don't have to have a button.

00:25:09.080 --> 00:25:11.620
<v Luke Renn>You can just type a console command in, reset the board.

00:25:12.380 --> 00:25:14.000
<v Luke Renn>But currently, you need a separate button.

00:25:14.800 --> 00:25:22.040
<v Raspberry Pi>And then the single-wire debug, rather, the SWD, is the thinking there that that's doing OpenOCD over a Pi?

00:25:22.200 --> 00:25:28.100
<v Raspberry Pi>Or what is the suggested method for actually doing that debug on Opico?

00:25:28.340 --> 00:25:32.140
<v Luke Renn>Well, it's fairly agnostic as to which debug probe you're actually using.

00:25:32.140 --> 00:25:34.980
<v Luke Renn>You can bitbang it from the GPIOs on a Pi.

00:25:35.160 --> 00:25:39.680
<v Luke Renn>You can use another Pico as a debug probe, which is just about the cheapest way to do it.

00:25:40.260 --> 00:25:43.080
<v Luke Renn>And we are adding support for other probes as we go.

00:25:44.300 --> 00:25:48.520
<v Luke Renn>OpenOCD puts quite a lot of protocol in the probe-specific drivers, so they are coming in one by one.

00:25:48.980 --> 00:25:51.540
<v Luke Renn>And also SEGA are adding J-Link support.

00:25:52.200 --> 00:25:53.760
<v Luke Renn>PiOCD are adding upstream support.

00:25:54.080 --> 00:25:57.600
<v Luke Renn>So you will be able to use whatever probe you have and just debug and load code that way.

00:25:57.920 --> 00:25:58.020
<v Raspberry Pi>Great.

00:25:58.460 --> 00:26:00.100
<v Raspberry Pi>Yeah, I feel like some of that is...

00:26:00.100 --> 00:26:01.960
<v Raspberry Pi>I mean, some of these things are...

00:26:01.960 --> 00:26:05.520
<v Raspberry Pi>You know, it seems like at the top level, most people are going to use it over USB, right?

00:26:05.540 --> 00:26:07.020
<v Raspberry Pi>So they'll use MicroPython.

00:26:07.180 --> 00:26:08.040
<v Raspberry Pi>They get started.

00:26:08.120 --> 00:26:08.720
<v Raspberry Pi>They drag and drop.

00:26:08.860 --> 00:26:09.880
<v Raspberry Pi>Like, that's just...

00:26:09.880 --> 00:26:13.200
<v Raspberry Pi>I feel like that is just so important to get that first blinky, to get that dopamine rush.

00:26:13.240 --> 00:26:16.780
<v Luke Renn>Yeah, it's the energy barrier to get that first dopamine rush of, I did the thing with the board.

00:26:16.880 --> 00:26:18.600
<v Luke Renn>And then you get hooked and drawn in, yeah.

00:26:18.600 --> 00:26:20.520
<v Raspberry Pi>Yeah, exactly.

00:26:21.260 --> 00:26:22.980
<v Raspberry Pi>I mean, do you guys see the...

00:26:22.980 --> 00:26:29.100
<v Raspberry Pi>On the education side, do you expect, like, school-age kids to be doing debug, things like that?

00:26:29.160 --> 00:26:33.920
<v Raspberry Pi>I mean, is that kind of the hope in the future or kind of just wait and see?

00:26:34.720 --> 00:26:38.020
<v Luke Renn>I was going to say, I don't see why they shouldn't, but I'll see what Luke thinks.

00:26:38.580 --> 00:26:43.180
<v Luke Renn>The USB bootloader is definitely the quickest, absolute lowest friction way to get started.

00:26:43.540 --> 00:26:47.600
<v Luke Renn>I think if you have a classroom full of Pies already, then you just run our setup script

00:26:47.600 --> 00:26:52.080
<v Luke Renn>and the debug is just a question of running a script, pressing enter, getting a cup of tea

00:26:52.080 --> 00:26:53.060
<v Luke Renn>and connecting up three wires.

00:26:53.740 --> 00:26:57.440
<v Luke Renn>If you have your own debug probe that you want to use with our board, you might have to do

00:26:57.440 --> 00:26:59.140
<v Luke Renn>some extra setup to use your probe.

00:26:59.540 --> 00:27:03.200
<v Luke Renn>But if you already have Pies installed in your classroom and you want to use Pico's, it's

00:27:03.200 --> 00:27:04.800
<v Luke Renn>pretty low friction to use the debug as well.

00:27:04.800 --> 00:27:08.720
<v Luke Renn>And that's all integrated into the IDE that we ship.

00:27:09.160 --> 00:27:13.860
<v Luke Renn>The other thing is, I expect that MicroPython will be quite popular in an educational context,

00:27:13.980 --> 00:27:16.140
<v Luke Renn>in which case it's all USB anyway.

00:27:16.260 --> 00:27:20.900
<v Luke Renn>As soon as you have the firmware installed on your board, you just open up Thonny or whatever

00:27:20.900 --> 00:27:22.480
<v Luke Renn>IDE you choose and you start typing.

00:27:22.880 --> 00:27:23.980
<v Luke Renn>And that's just a USB connection.

00:27:24.180 --> 00:27:24.200
<v Luke Renn>Yeah.

00:27:24.780 --> 00:27:25.020
<v Raspberry Pi>Yeah.

00:27:25.040 --> 00:27:27.000
<v Raspberry Pi>I mean, for people who haven't done that yet, it's just...

00:27:27.000 --> 00:27:31.160
<v Raspberry Pi>Actually, I remember seeing that at a meetup when I was in the UK.

00:27:31.700 --> 00:27:34.560
<v Raspberry Pi>Someone, I think it was Tom someone, I forget who it was.

00:27:34.800 --> 00:27:39.940
<v Raspberry Pi>Someone had shown me basically a USB bootloader, just simple code manipulation.

00:27:40.240 --> 00:27:42.640
<v Raspberry Pi>And it just felt so, so magical.

00:27:42.880 --> 00:27:45.820
<v Raspberry Pi>Because it's literally just hitting save in a text editor.

00:27:46.220 --> 00:27:48.280
<v Raspberry Pi>And then, oh, hey, it rebooted.

00:27:48.620 --> 00:27:49.780
<v Raspberry Pi>It knows there's something here.

00:27:50.120 --> 00:27:50.980
<v Raspberry Pi>The LED changes.

00:27:51.380 --> 00:27:55.600
<v Raspberry Pi>And that's just like, that's so radically different from how I had operated in the past.

00:27:55.600 --> 00:27:56.080
<v Raspberry Pi>Sure.

00:27:56.080 --> 00:27:56.400
<v Luke Renn>Sure.

00:27:56.540 --> 00:28:00.960
<v Luke Renn>And I think you can get a lot of mileage and a lot of new understanding in embedded software

00:28:00.960 --> 00:28:02.740
<v Luke Renn>without having to understand how C works.

00:28:03.320 --> 00:28:04.360
<v Luke Renn>And that might annoy some people.

00:28:04.680 --> 00:28:07.440
<v Luke Renn>But, you know, MicroPython lets you talk to a lot of sensors.

00:28:07.440 --> 00:28:11.240
<v Luke Renn>It lets you embed software into a lot of devices.

00:28:11.240 --> 00:28:16.120
<v Luke Renn>And making MicroPython as slick as possible and minimizing the hardware requirements there

00:28:16.120 --> 00:28:17.860
<v Luke Renn>is what we really optimized for.

00:28:18.480 --> 00:28:18.580
<v Raspberry Pi>Yeah.

00:28:18.700 --> 00:28:22.660
<v Raspberry Pi>I think it's that, again, it comes down to that first experience that, you know,

00:28:22.680 --> 00:28:26.940
<v Raspberry Pi>there's really no reason to scare people away with just being like, well, let's talk about

00:28:26.940 --> 00:28:29.620
<v Raspberry Pi>assigning memory.

00:28:29.840 --> 00:28:32.960
<v Raspberry Pi>You know, like, let's talk about pointers.

00:28:32.960 --> 00:28:35.840
<v Raspberry Pi>It's like, nah, let's maybe not do that right away.

00:28:35.840 --> 00:28:40.600
<v Raspberry Pi>We can do that once people are excited about the thing that they're doing with the hardware first.

00:28:41.380 --> 00:28:41.480
<v Luke Renn>Yeah.

00:28:41.560 --> 00:28:47.100
<v Luke Renn>I mean, I don't think C is going away really ever or other much lower level languages like

00:28:47.100 --> 00:28:49.380
<v Luke Renn>Rust, which some people are also playing with on RP2040.

00:28:49.840 --> 00:28:54.640
<v Luke Renn>But the real value add is in blinking your light, not in allocating your memory.

00:28:55.440 --> 00:28:55.880
<v Raspberry Pi>Yeah.

00:28:56.160 --> 00:28:56.320
<v Raspberry Pi>Yeah.

00:28:57.120 --> 00:28:57.520
<v Raspberry Pi>Yeah.

00:28:57.520 --> 00:29:00.800
<v Raspberry Pi>I mean, so let's talk a little bit more about the RP2040 core as well.

00:29:00.800 --> 00:29:05.680
<v Raspberry Pi>I mean, so obviously people can go and check out more about the deep dive into it,

00:29:05.680 --> 00:29:07.260
<v Raspberry Pi>the documentation you mentioned is really great.

00:29:07.760 --> 00:29:12.580
<v Raspberry Pi>But like, do you have like a benchmark or similar processor that you kind of point to

00:29:12.580 --> 00:29:13.800
<v Raspberry Pi>and say, oh, it's kind of like that.

00:29:13.820 --> 00:29:16.020
<v Raspberry Pi>It's maybe at the same level.

00:29:17.240 --> 00:29:18.940
<v Luke Renn>It really does depend on workload.

00:29:19.060 --> 00:29:21.140
<v Luke Renn>A lot of people have also asked us to compare it to a Pi.

00:29:21.260 --> 00:29:23.420
<v Luke Renn>And the answer is, well, they kind of do different things.

00:29:23.800 --> 00:29:26.980
<v Luke Renn>I mean, an Emzera Plus gets a surprising amount done per cycle.

00:29:27.160 --> 00:29:32.540
<v Luke Renn>If you want Drystone, if you think that's a good benchmark, it's about 0.9, 0.93 D-mix megahertz.

00:29:32.540 --> 00:29:36.840
<v Luke Renn>So if you clock them hard, which you can do on 40 nanometer, we get a lot of integer throughput.

00:29:37.620 --> 00:29:41.820
<v Luke Renn>I mean, any core running at 133 that isn't messing about spending 10 cycles doing something,

00:29:41.940 --> 00:29:42.680
<v Luke Renn>you're going to get a lot done.

00:29:43.520 --> 00:29:47.680
<v Luke Renn>And the other thing we focused on is, well, we have a two core system because we think

00:29:47.680 --> 00:29:52.060
<v Luke Renn>that is a great way of getting a lot of instructions and data through the system

00:29:52.060 --> 00:29:54.320
<v Luke Renn>when you have a lot of memory parallelism available.

00:29:54.320 --> 00:29:59.900
<v Luke Renn>And we've made sure that those two cores can genuinely execute at full throttle all the

00:29:59.900 --> 00:30:01.060
<v Luke Renn>time and not getting each other's way.

00:30:01.780 --> 00:30:05.680
<v Luke Renn>So actually, in terms of shoveling data around and doing simple DSP type things, we're pretty

00:30:05.680 --> 00:30:05.960
<v Luke Renn>fast.

00:30:06.600 --> 00:30:06.700
<v Raspberry Pi>Yeah.

00:30:06.900 --> 00:30:07.160
<v Raspberry Pi>Okay.

00:30:07.380 --> 00:30:07.920
<v Raspberry Pi>Okay, great.

00:30:08.180 --> 00:30:11.640
<v Raspberry Pi>And the dual core, so you mentioned like doing that.

00:30:11.740 --> 00:30:16.900
<v Raspberry Pi>I mean, are there other expectations from like the future proofing side of things?

00:30:16.940 --> 00:30:21.720
<v Raspberry Pi>I mean, I've seen some people asking about, obviously, there's no comms on the Pico to keep

00:30:21.720 --> 00:30:26.740
<v Raspberry Pi>cost down, but is the thinking there that maybe at one point the second processor will

00:30:26.740 --> 00:30:32.620
<v Raspberry Pi>interface to like a simple Wi-Fi modem or something like that?

00:30:33.600 --> 00:30:35.400
<v Luke Renn>The two cores aren't to do with Wi-Fi.

00:30:35.520 --> 00:30:38.100
<v Luke Renn>They are two symmetric cores for doing more processing.

00:30:38.860 --> 00:30:43.500
<v Luke Renn>And that can really simplify your firmware sometimes if you have trouble with, you know,

00:30:43.520 --> 00:30:47.540
<v Luke Renn>if you've got some complex single core app where it all runs fine for an hour and then

00:30:47.540 --> 00:30:50.940
<v Luke Renn>you have all of your interrupts lined up just right, they all preempt each other and you

00:30:50.940 --> 00:30:51.640
<v Luke Renn>blow a timing budget.

00:30:52.040 --> 00:30:55.820
<v Luke Renn>The ability to just take some real hard real-time interrupts and pump them onto a different core

00:30:55.820 --> 00:30:59.120
<v Luke Renn>can really make your firmware more robust and actually simpler.

00:30:59.580 --> 00:31:01.320
<v Luke Renn>We also have the option in hardware.

00:31:01.500 --> 00:31:05.540
<v Raspberry Pi>So it sounds like it's almost more like, why wouldn't we have a dual core?

00:31:05.720 --> 00:31:08.400
<v Raspberry Pi>You know, it's almost like at that point, if we're going to make a thing, it's going

00:31:08.400 --> 00:31:08.760
<v Raspberry Pi>to be new.

00:31:08.940 --> 00:31:10.700
<v Raspberry Pi>Why not make a dual core to make it more robust?

00:31:10.760 --> 00:31:10.900
<v Raspberry Pi>Yeah.

00:31:11.020 --> 00:31:12.780
<v Luke Renn>I mean, I think there are a lot of benefits to it.

00:31:12.780 --> 00:31:17.680
<v Luke Renn>If you compare two M0 pluses to an M4 connected to the same system, you get a lot more execution

00:31:17.680 --> 00:31:20.940
<v Luke Renn>throughput from two M0 pluses because they make better use of their bus ports.

00:31:21.540 --> 00:31:25.540
<v Luke Renn>We also have the option, although we haven't got the software in place for it yet, of using

00:31:25.540 --> 00:31:28.140
<v Luke Renn>the second core as a debugger for the first one.

00:31:28.600 --> 00:31:31.640
<v Luke Renn>So you lose your USB and your second core.

00:31:31.860 --> 00:31:36.640
<v Luke Renn>And what you get is a very cheap single core microcontroller with an integrated debugger.

00:31:36.780 --> 00:31:40.040
<v Luke Renn>And the second core can take control of the resets and load code and all that stuff.

00:31:40.260 --> 00:31:42.320
<v Luke Renn>There's a little bit of software engineering to do that.

00:31:42.320 --> 00:31:46.620
<v Luke Renn>But I think that not having to have a second device on the board to debug is going to be

00:31:46.620 --> 00:31:47.120
<v Luke Renn>quite interesting.

00:31:48.060 --> 00:31:50.140
<v Raspberry Pi>That's on the roadmap or what's the thinking there?

00:31:50.160 --> 00:31:50.940
<v Luke Renn>It is on the roadmap.

00:31:51.100 --> 00:31:52.480
<v Luke Renn>It's purely a software problem at this point.

00:31:52.680 --> 00:31:52.760
<v Luke Renn>Yeah.

00:31:52.800 --> 00:31:56.480
<v Luke Renn>There is an ARM guy who's hacking on that with CMSysDAP, but the problem is squeezing all

00:31:56.480 --> 00:31:58.120
<v Luke Renn>the USB code into the USB data RAM.

00:31:58.720 --> 00:31:58.980
<v Raspberry Pi>Huh.

00:31:59.720 --> 00:32:00.720
<v Raspberry Pi>That's really cool though.

00:32:01.060 --> 00:32:02.320
<v Raspberry Pi>I mean, that would be...

00:32:03.120 --> 00:32:03.960
<v Raspberry Pi>I mean, I've seen that.

00:32:04.020 --> 00:32:07.440
<v Raspberry Pi>Obviously, dev boards are like that now, but there's literally two chips on board, right?

00:32:07.480 --> 00:32:08.280
<v Raspberry Pi>I mean, that's...

00:32:08.280 --> 00:32:13.660
<v Luke Renn>Yeah, it's normally a second microcontroller with a USB interface that's bit banging the

00:32:13.660 --> 00:32:15.660
<v Luke Renn>SWD port on the first microcontroller.

00:32:15.980 --> 00:32:20.140
<v Luke Renn>And actually, if you do that all internally, it costs you almost nothing to do that and

00:32:20.140 --> 00:32:21.540
<v Luke Renn>have integrated debug over USB.

00:32:22.900 --> 00:32:23.500
<v Raspberry Pi>All right.

00:32:23.560 --> 00:32:25.200
<v Raspberry Pi>So you mentioned microcontroller.

00:32:25.400 --> 00:32:27.060
<v Raspberry Pi>I have to ask because Dave asked me to.

00:32:28.080 --> 00:32:31.160
<v Raspberry Pi>Microcontroller or microprocessor, what are we working with here, guys?

00:32:31.160 --> 00:32:37.420
<v Luke Renn>I would say this is a flashless microcontroller, which I think is pretty common already and

00:32:37.420 --> 00:32:38.460
<v Luke Renn>is going to become more common.

00:32:39.340 --> 00:32:42.880
<v Luke Renn>When I think of a microcontroller, I think of something that is highly integrated, very

00:32:42.880 --> 00:32:49.180
<v Luke Renn>low cost, very low cross-system latency, and more of a focus on IO and hard real time

00:32:49.180 --> 00:32:50.660
<v Luke Renn>as opposed to processing throughput.

00:32:51.160 --> 00:32:55.000
<v Luke Renn>You try and integrate as much as possible, but the reason you do that is really about cost.

00:32:55.540 --> 00:32:59.540
<v Luke Renn>And the question is, is it cheaper to have the flash on board than it is to have it out

00:32:59.540 --> 00:32:59.720
<v Luke Renn>board?

00:32:59.720 --> 00:33:02.260
<v Raspberry Pi>So, yes, I mean, you mentioned 40 nanometers.

00:33:02.420 --> 00:33:03.920
<v Raspberry Pi>So that's the process this thing's on?

00:33:04.380 --> 00:33:04.640
<v Luke Renn>Yes.

00:33:05.840 --> 00:33:11.040
<v Raspberry Pi>So could you give us a rough estimate for like the, I feel like this is maybe touchy because

00:33:11.040 --> 00:33:15.480
<v Raspberry Pi>it's asking about cost numbers, but like, obviously it was a cost-driven decision, but

00:33:15.480 --> 00:33:19.760
<v Raspberry Pi>like, was it enough of a, that seems like this is a decision that was made like right at the

00:33:19.760 --> 00:33:20.000
<v Raspberry Pi>beginning.

00:33:20.000 --> 00:33:23.700
<v Raspberry Pi>So like, how did this decision-making process go to put flash external?

00:33:23.900 --> 00:33:27.900
<v Luke Renn>It's definitely been one of our main design briefs to make it as low cost as possible and

00:33:27.900 --> 00:33:31.160
<v Luke Renn>also to offer as much memory as possible at the lowest possible cost.

00:33:31.320 --> 00:33:35.500
<v Luke Renn>So we are roughly a two square millimeter device on 14 nanometer.

00:33:35.640 --> 00:33:37.480
<v Luke Renn>We get about 20,000 diaper wafer.

00:33:38.020 --> 00:33:38.720
<v Luke Renn>Oh, wow.

00:33:38.720 --> 00:33:40.400
<v Luke Renn>It's crazy.

00:33:40.400 --> 00:33:40.600
<v Luke Renn>Yeah.

00:33:41.240 --> 00:33:44.920
<v Luke Renn>We actually, so this is the second iteration of this device.

00:33:45.100 --> 00:33:47.620
<v Luke Renn>The first one was more of a test bed for the analog hardware.

00:33:48.200 --> 00:33:49.080
<v Luke Renn>This is B0.

00:33:49.200 --> 00:33:49.820
<v Luke Renn>That was A0.

00:33:50.020 --> 00:33:52.120
<v Luke Renn>On A0, we did actually have the flash on die.

00:33:52.240 --> 00:33:55.240
<v Luke Renn>We completely bottoms out on that development possibility.

00:33:55.560 --> 00:33:57.640
<v Luke Renn>And we think that economically it's the wrong thing to do.

00:33:57.640 --> 00:34:03.720
<v Luke Renn>So that device had 256k of onboard flash and 32k of onboard SRAM.

00:34:04.280 --> 00:34:08.940
<v Luke Renn>And because flash is more dense than SRAM, that was a smaller device to produce.

00:34:09.500 --> 00:34:14.140
<v Luke Renn>But actually because of the extra passing steps involved in building the flash, it was the

00:34:14.140 --> 00:34:16.700
<v Luke Renn>same cost as B0, which is a larger device.

00:34:17.400 --> 00:34:21.540
<v Luke Renn>So I think if you asked your average software engineer, would you like to trade all of your

00:34:21.540 --> 00:34:26.560
<v Luke Renn>flash for SRAM at constant cost and then spend a few cents if you need to initialize it or

00:34:26.560 --> 00:34:27.640
<v Luke Renn>execute from an external device?

00:34:27.960 --> 00:34:32.820
<v Luke Renn>They'd probably say yes, because bumping up against limited memory is one of the constant

00:34:32.820 --> 00:34:34.560
<v Luke Renn>frustrations in embedded software.

00:34:35.220 --> 00:34:40.760
<v Luke Renn>And actually, SRAM can be as cheap as flash if you make some hard-nosed decisions about

00:34:40.760 --> 00:34:41.680
<v Luke Renn>what else you have on die.

00:34:43.360 --> 00:34:46.840
<v Raspberry Pi>Well, that's a really interesting insight into that decision-making.

00:34:46.840 --> 00:34:52.980
<v Raspberry Pi>I was just looking, when I first heard about this, I was just thinking like flash is going

00:34:52.980 --> 00:34:54.220
<v Raspberry Pi>to be on an advanced node anyways.

00:34:54.340 --> 00:35:01.200
<v Raspberry Pi>I mean, it chases the bleeding edge anyways, just so that flash makers can keep up, it feels

00:35:01.200 --> 00:35:01.460
<v Raspberry Pi>like.

00:35:01.520 --> 00:35:02.960
<v Raspberry Pi>I mean, having worked for one of them.

00:35:03.280 --> 00:35:06.900
<v Luke Renn>Yeah, but there are already people who are making silicon that's really highly optimized

00:35:06.900 --> 00:35:08.600
<v Luke Renn>to make flash at a low cost.

00:35:09.420 --> 00:35:13.220
<v Luke Renn>And the 40 nanometer process we've used with the metal stack we've used is great at making

00:35:13.220 --> 00:35:15.440
<v Luke Renn>logic and SRAM at a low cost.

00:35:15.440 --> 00:35:19.420
<v Luke Renn>And actually, if you try and put those both on the same die, you might expect that integrating

00:35:19.420 --> 00:35:20.140
<v Luke Renn>it makes it cheaper.

00:35:20.220 --> 00:35:21.320
<v Luke Renn>It actually makes it more expensive.

00:35:22.080 --> 00:35:27.140
<v Chris Gammell>I was going to say the net cost is probably slightly in favor of the external flash.

00:35:27.560 --> 00:35:32.640
<v Chris Gammell>As Luke says, this stuff isn't completely obvious, right?

00:35:32.680 --> 00:35:37.540
<v Chris Gammell>I think it was about 35% cost up to add flash to 40 nanometers, something like that.

00:35:37.800 --> 00:35:39.720
<v Chris Gammell>Don't quote me on it exactly, but significant.

00:35:40.420 --> 00:35:43.660
<v Chris Gammell>And then you've added the flash on your die, and then you've taken away all the space where

00:35:43.660 --> 00:35:44.580
<v Chris Gammell>you can put your SRAM, right?

00:35:44.580 --> 00:35:50.420
<v Chris Gammell>And it's a slightly more funky process than a standard 40 process that everyone knows

00:35:50.420 --> 00:35:51.960
<v Chris Gammell>and loves and all the IP is developed for.

00:35:52.380 --> 00:35:56.460
<v Chris Gammell>So you also have to sign a bit of a waiver on your IP saying, hey, we're using this slightly

00:35:56.460 --> 00:35:57.440
<v Chris Gammell>funky flash process.

00:35:58.380 --> 00:35:59.360
<v Chris Gammell>Maybe your IP isn't going to work.

00:35:59.940 --> 00:36:06.500
<v Chris Gammell>So we kind of, after having the first initial test silicon and looking at the whole thing

00:36:06.500 --> 00:36:09.240
<v Chris Gammell>in the round, it just made a lot of sense to put the flash external.

00:36:09.460 --> 00:36:12.580
<v Chris Gammell>And then also, of course, then it gives you the flexibility to have as much or as little

00:36:12.580 --> 00:36:13.020
<v Chris Gammell>as you want.

00:36:13.020 --> 00:36:14.520
<v Chris Gammell>So that worked out very nicely.

00:36:16.140 --> 00:36:17.660
<v Raspberry Pi>Yeah, I would think in the future too.

00:36:17.780 --> 00:36:22.840
<v Raspberry Pi>I mean, like if you guys are setting a cost target at $4 now, like in two years from now,

00:36:22.880 --> 00:36:25.060
<v Raspberry Pi>if it's still $4, flash is getting cheaper.

00:36:25.320 --> 00:36:27.520
<v Raspberry Pi>I assume that your process is going to get cheaper too.

00:36:27.620 --> 00:36:30.220
<v Raspberry Pi>You'll be able to get process efficiencies, things like that.

00:36:30.220 --> 00:36:36.100
<v Raspberry Pi>So yeah, I'd imagine that in all cases, this actually probably, it's probably a lot cheaper

00:36:36.100 --> 00:36:39.700
<v Raspberry Pi>to go and switch out a, you know, the engineering cost to go switch out a external flash chip

00:36:39.700 --> 00:36:45.100
<v Raspberry Pi>in the future is probably a lot lower than a cost down or a size down, whatever they call

00:36:45.100 --> 00:36:48.280
<v Raspberry Pi>it for silicon for your own die design, I would imagine.

00:36:48.280 --> 00:36:51.040
<v Chris Gammell>So that's sort of true, but not completely.

00:36:51.180 --> 00:36:55.560
<v Chris Gammell>I think on the flash side of it, the sizes of flash we're using, we're at the bottom, right?

00:36:55.620 --> 00:36:59.080
<v Chris Gammell>Of the trough of flash pricing, right?

00:36:59.100 --> 00:37:00.000
<v Chris Gammell>It's a very small flash.

00:37:00.080 --> 00:37:01.900
<v Chris Gammell>It's on a quite old process, very cheap.

00:37:02.480 --> 00:37:04.640
<v Chris Gammell>You know, we can't squeeze much cost out of that really.

00:37:05.220 --> 00:37:06.180
<v Raspberry Pi>Likewise, 40 nanometer.

00:37:06.180 --> 00:37:08.300
<v Raspberry Pi>I just meant like at the same cost.

00:37:08.380 --> 00:37:08.480
<v Raspberry Pi>Yeah.

00:37:08.480 --> 00:37:09.240
<v Raspberry Pi>You're at the bottom of the trough.

00:37:09.320 --> 00:37:13.780
<v Raspberry Pi>I just meant that the other entrance into that trough would then be bigger.

00:37:13.980 --> 00:37:16.560
<v Raspberry Pi>So maybe for the same cost, you'd get bigger flash in the future.

00:37:16.620 --> 00:37:17.660
<v Raspberry Pi>That's all I was thinking there.

00:37:17.920 --> 00:37:18.840
<v Raspberry Pi>Yes, that's probably true.

00:37:18.980 --> 00:37:19.100
<v Raspberry Pi>Yeah.

00:37:19.440 --> 00:37:19.620
<v Raspberry Pi>Cool.

00:37:19.940 --> 00:37:20.080
<v Raspberry Pi>Yeah.

00:37:20.200 --> 00:37:22.140
<v Raspberry Pi>That's a very, it's an interesting insight.

00:37:22.220 --> 00:37:27.140
<v Raspberry Pi>I mean, like, again, these are volumes that I'm just not privy to, you know, like I just

00:37:27.140 --> 00:37:31.200
<v Raspberry Pi>don't, I don't, I don't get to have these kinds of conversations ever.

00:37:31.200 --> 00:37:37.320
<v Luke Renn>So, I mean, speaking of volume flash is going to be a lot higher volume than any microcontroller,

00:37:37.640 --> 00:37:41.440
<v Luke Renn>you know, serial flashes in everything and microcontrollers never going to approach that

00:37:41.440 --> 00:37:41.740
<v Luke Renn>volume.

00:37:42.280 --> 00:37:42.400
<v Chris Gammell>Yeah.

00:37:42.820 --> 00:37:43.100
<v Chris Gammell>Right.

00:37:43.320 --> 00:37:47.140
<v Chris Gammell>I mean, the cost of the, another interesting fact is the cost of the packaging of these

00:37:47.140 --> 00:37:53.620
<v Chris Gammell>silicon devices, the flash and our, our microcontroller is a very significant fraction of the cost

00:37:53.620 --> 00:37:54.400
<v Chris Gammell>of the device.

00:37:54.460 --> 00:37:54.640
<v Chris Gammell>Right.

00:37:54.720 --> 00:37:58.160
<v Chris Gammell>So it's interesting to look at it from that, from that point of view as well.

00:37:58.160 --> 00:37:58.340
<v Chris Gammell>Right.

00:37:58.400 --> 00:38:02.300
<v Chris Gammell>The flash, the package of the flash is put in is, it is probably more expensive than the

00:38:02.300 --> 00:38:03.460
<v Chris Gammell>actual silicon that's going in it.

00:38:03.640 --> 00:38:07.320
<v Chris Gammell>And that's also pretty much true of, of our, uh, our microcontroller.

00:38:08.160 --> 00:38:11.480
<v Raspberry Pi>So this stuff has been very interesting on the Pico and the RP2040.

00:38:11.480 --> 00:38:16.400
<v Raspberry Pi>I think I will get strangled by our audience if I don't start talking about the traditional

00:38:16.400 --> 00:38:19.300
<v Raspberry Pi>Raspberry Pi or Raspberry Pi 4 and the CM4.

00:38:20.000 --> 00:38:23.640
<v Raspberry Pi>So I guess the first question I have about, about just kind of switching a little bit to

00:38:23.640 --> 00:38:27.500
<v Raspberry Pi>that is what is the, what's the division?

00:38:27.620 --> 00:38:32.780
<v Raspberry Pi>I mean, how much focus is there on the, the large Linux stuff versus this new kind of lower

00:38:32.780 --> 00:38:34.240
<v Raspberry Pi>level microcontroller stuff?

00:38:35.260 --> 00:38:36.800
<v Liam Fraser>Maybe I can speak about that.

00:38:37.340 --> 00:38:45.780
<v Liam Fraser>So the, the Pico team, especially from a software and documentation point of view is really tiny.

00:38:45.780 --> 00:38:51.660
<v Liam Fraser>There's probably, you know, three or four people at most working on the SDK, but it, you know,

00:38:51.700 --> 00:38:55.860
<v Liam Fraser>rarely it's been mostly done by me, Luke and a guy called Graham Sanderson.

00:38:56.200 --> 00:39:00.700
<v Liam Fraser>And then there's a couple of extra people who've sort of wrangled us to write documentation,

00:39:00.700 --> 00:39:04.340
<v Liam Fraser>but we've been writing documentation for the last nine months.

00:39:04.340 --> 00:39:09.360
<v Liam Fraser>And to sort of go back to what we were talking about before about tool chain and stuff.

00:39:09.980 --> 00:39:18.300
<v Liam Fraser>Even though the C and sort of C++ tool chain is more difficult to get going with than MicroPython.

00:39:18.560 --> 00:39:24.500
<v Liam Fraser>It's still very easy compared to a lot of other microcontrollers, particularly if you're on Linux

00:39:24.500 --> 00:39:29.220
<v Liam Fraser>or a Pi, because, you know, I wrote a setup script that just installs everything you need.

00:39:29.220 --> 00:39:34.320
<v Liam Fraser>You can open VS code, wire up your two wire and press play and you're debugging.

00:39:34.960 --> 00:39:40.100
<v Liam Fraser>So the, the sort of barrier to getting debug on a microcontroller is, is something that,

00:39:40.420 --> 00:39:42.220
<v Liam Fraser>that we wanted to focus on.

00:39:42.340 --> 00:39:45.900
<v Liam Fraser>But the other thing is that the SDK is really clean.

00:39:46.000 --> 00:39:47.000
<v Liam Fraser>It's really nice.

00:39:47.060 --> 00:39:48.420
<v Liam Fraser>It's, it's quite state of the art.

00:39:48.540 --> 00:39:53.860
<v Liam Fraser>And like I say, cause we've, cause we're a small team, that's why we sort of focused on

00:39:53.860 --> 00:39:57.920
<v Liam Fraser>making a decent SDK that other people can then build their own stuff on.

00:39:57.920 --> 00:40:02.220
<v Liam Fraser>You know, Arduino have got a product coming out, so I'm sure they'll port the Arduino IDE,

00:40:02.820 --> 00:40:05.120
<v Liam Fraser>which will just use our SDK underneath.

00:40:05.680 --> 00:40:05.760
<v Raspberry Pi>Yeah.

00:40:06.520 --> 00:40:12.020
<v Liam Fraser>And then it's, it's really a sort of whole other set of people that do the, the Pi 4 software

00:40:12.020 --> 00:40:12.460
<v Liam Fraser>side.

00:40:12.560 --> 00:40:18.240
<v Liam Fraser>There's, there's a really long tail of like software, you know, always like porting the

00:40:18.240 --> 00:40:22.740
<v Liam Fraser>next Chrome version over and there's always firmware and kernel updates and all that kind

00:40:22.740 --> 00:40:23.100
<v Liam Fraser>of stuff.

00:40:23.100 --> 00:40:26.220
<v Raspberry Pi>So you guys are like the team within the team within the team.

00:40:26.220 --> 00:40:31.060
<v Raspberry Pi>It sounds like, cause it's like a hardware within the Raspberry Pi hardware software ecosystem

00:40:31.060 --> 00:40:34.440
<v Raspberry Pi>within the Raspberry Pi trading within the Raspberry Pi foundation.

00:40:34.440 --> 00:40:37.420
<v Raspberry Pi>So it's, we're, we're deep here, folks.

00:40:37.420 --> 00:40:42.800
<v Raspberry Pi>We are, we are talking to the people, you know, that's great.

00:40:42.900 --> 00:40:43.360
<v Raspberry Pi>That's great.

00:40:43.540 --> 00:40:48.720
<v Luke Renn>We all wear a lot of different hats at work and we tend to group people by topic instead

00:40:48.720 --> 00:40:49.460
<v Luke Renn>of by discipline.

00:40:49.460 --> 00:40:53.500
<v Luke Renn>So I've worked on hardware and software, but it's all been on RP 2040.

00:40:54.380 --> 00:40:54.740
<v Raspberry Pi>Cool.

00:40:54.940 --> 00:40:55.100
<v Raspberry Pi>Yeah.

00:40:55.260 --> 00:40:55.740
<v Raspberry Pi>That's great.

00:40:56.780 --> 00:41:00.800
<v Raspberry Pi>Well, maybe a good transitional thing to talk about too, is like, do you see these things

00:41:00.800 --> 00:41:02.160
<v Raspberry Pi>merging, merging in the future?

00:41:02.260 --> 00:41:09.320
<v Raspberry Pi>I mean, like one, one thing I've seen prognosticated, but not, uh, not confirmed is just like, how is

00:41:09.320 --> 00:41:13.480
<v Raspberry Pi>the RP 2040 going to interplay with a large Linux system in the future?

00:41:13.480 --> 00:41:18.480
<v Raspberry Pi>I mean, like, is it like, are you thinking like pairing them together, having, you know,

00:41:18.560 --> 00:41:23.820
<v Raspberry Pi>co-processing style things done the Raspberry Pi four, you know, there's discussions about

00:41:23.820 --> 00:41:25.720
<v Raspberry Pi>that sort of thing or five rather.

00:41:25.880 --> 00:41:25.980
<v Raspberry Pi>Sorry.

00:41:26.540 --> 00:41:30.880
<v Chris Gammell>I think there's a, you know, there's a natural synergy there, whether we're going to pair

00:41:30.880 --> 00:41:32.760
<v Chris Gammell>them in products.

00:41:32.800 --> 00:41:35.520
<v Chris Gammell>I'm not sure because we're so cost focused.

00:41:35.600 --> 00:41:39.900
<v Chris Gammell>I, I doubt that something like the Raspberry Pi five will have an RP 2040 on it.

00:41:39.900 --> 00:41:45.100
<v Chris Gammell>If that's what you're asking, especially, especially when we, you know, I think it's

00:41:45.100 --> 00:41:45.920
<v Chris Gammell>completely conceivable.

00:41:46.140 --> 00:41:48.280
<v Chris Gammell>We will use this in our own products going forward.

00:41:48.560 --> 00:41:51.860
<v Chris Gammell>If we need microcontrollers in those products, that would make a lot of sense.

00:41:52.720 --> 00:41:53.200
<v Raspberry Pi>Got it.

00:41:53.240 --> 00:41:56.080
<v Raspberry Pi>So like, you're not going to add it just to have it because of the cost focus.

00:41:56.420 --> 00:42:00.140
<v Raspberry Pi>Like, yeah, but it's so, it is cheap enough that you would choose this if you were reaching

00:42:00.140 --> 00:42:02.940
<v Raspberry Pi>out for a microcontroller, but you would not, you're not just going to throw a micro

00:42:02.940 --> 00:42:03.980
<v Raspberry Pi>on there just for funsies.

00:42:03.980 --> 00:42:08.460
<v Raspberry Pi>You're going to, you're going to cost down and optimize the bare minimum of what's needed.

00:42:08.740 --> 00:42:09.140
<v Chris Gammell>Yeah, absolutely.

00:42:09.140 --> 00:42:15.360
<v Chris Gammell>I think, you know, there, there are definitely areas where it would probably make sense to

00:42:15.360 --> 00:42:19.020
<v Chris Gammell>use our own microcontroller from a cost point of view versus other silicon.

00:42:19.460 --> 00:42:24.180
<v Chris Gammell>And we're quite good at that kind of sort of slightly innovative use of things.

00:42:24.180 --> 00:42:29.340
<v Chris Gammell>So if we can do something on a micro in software, then we'd choose that over a slightly more expensive,

00:42:29.500 --> 00:42:30.900
<v Chris Gammell>dedicated chip for doing something else.

00:42:30.960 --> 00:42:31.140
<v Chris Gammell>Right.

00:42:31.220 --> 00:42:38.700
<v Chris Gammell>I mean, we always like to find those little hacks to, to, to make the products cheaper if

00:42:38.700 --> 00:42:39.120
<v Chris Gammell>we can.

00:42:39.600 --> 00:42:39.960
<v Raspberry Pi>Yeah.

00:42:40.060 --> 00:42:44.860
<v Raspberry Pi>I mean, so like if I could, if I could make a pitch, I mean, uh, one thing that I'm doing

00:42:44.860 --> 00:42:48.920
<v Raspberry Pi>with, uh, with Raspberry Pi stuff right now is, uh, is I have a kind of a co-processing

00:42:48.920 --> 00:42:54.180
<v Raspberry Pi>model where I throw commands down to an embedded thing and then it goes and shuts off the Pi.

00:42:54.640 --> 00:42:57.380
<v Raspberry Pi>And, you know, that's common just for battery saving techniques.

00:42:57.380 --> 00:43:01.660
<v Raspberry Pi>And people are just seem to be putting Raspberry Pis and CM4s into everything anyways.

00:43:01.940 --> 00:43:05.680
<v Raspberry Pi>So that's one thing where I was like, I was looking at the RP2040 and being like, oh, well,

00:43:05.880 --> 00:43:09.960
<v Raspberry Pi>it would probably be on the software side because you could use a wide range of other micros that

00:43:09.960 --> 00:43:10.460
<v Raspberry Pi>are out there.

00:43:10.700 --> 00:43:16.260
<v Raspberry Pi>But, you know, just throw commands down to the micro side, have it shut down the Linux system

00:43:16.260 --> 00:43:18.580
<v Raspberry Pi>and then have it gracefully come back up as needed.

00:43:18.720 --> 00:43:22.060
<v Raspberry Pi>That, that's, that was my first thought, but probably because I'm already working on

00:43:22.060 --> 00:43:23.480
<v Raspberry Pi>that sort of thing for myself.

00:43:24.100 --> 00:43:24.560
<v Chris Gammell>I can imagine.

00:43:25.180 --> 00:43:29.660
<v Chris Gammell>I mean, my hope is that it would be relatively straightforward for someone to build a hat

00:43:29.660 --> 00:43:32.300
<v Chris Gammell>or similar for the Raspberry Pi to do that, I guess, as you're doing, right?

00:43:32.680 --> 00:43:33.840
<v Chris Gammell>Yeah, exactly.

00:43:34.040 --> 00:43:34.280
<v Chris Gammell>Exactly.

00:43:34.500 --> 00:43:35.140
<v Raspberry Pi>I think it just, yeah.

00:43:35.380 --> 00:43:35.520
<v Raspberry Pi>Yeah.

00:43:35.520 --> 00:43:38.660
<v Raspberry Pi>And I guess there's not a need from a, you know, a product perspective too.

00:43:38.720 --> 00:43:42.720
<v Raspberry Pi>It's not like people who are building home media systems are like Jones and for like

00:43:42.720 --> 00:43:43.660
<v Raspberry Pi>battery savings, right?

00:43:43.680 --> 00:43:45.300
<v Raspberry Pi>They're like, no, I'll take more power.

00:43:45.300 --> 00:43:45.660
<v Raspberry Pi>Yeah.

00:43:45.660 --> 00:43:46.000
<v Raspberry Pi>More.

00:43:46.160 --> 00:43:49.280
<v Raspberry Pi>I'll just take all, all of the graphics processing you can do.

00:43:49.400 --> 00:43:50.080
<v Raspberry Pi>Thank you very much.

00:43:50.200 --> 00:43:50.360
<v Raspberry Pi>Yeah.

00:43:50.440 --> 00:43:52.000
<v Chris Gammell>I mean, it is so cost driven.

00:43:52.300 --> 00:43:57.780
<v Chris Gammell>You know, to, to, to add, add something like a RP2040 is difficult to justify.

00:43:58.200 --> 00:44:00.400
<v Chris Gammell>We try and get the kind of 80% model, right?

00:44:00.460 --> 00:44:06.400
<v Chris Gammell>We want to add, if we add a feature, it's got to be good for about 80% of people who might

00:44:06.400 --> 00:44:07.020
<v Chris Gammell>buy the thing.

00:44:07.380 --> 00:44:08.820
<v Chris Gammell>And we're always very cost constrained.

00:44:09.000 --> 00:44:09.780
<v Chris Gammell>We really, really are.

00:44:09.840 --> 00:44:13.440
<v Chris Gammell>And every generation we, we pack more stuff into the same price point.

00:44:13.440 --> 00:44:18.620
<v Chris Gammell>So we get bigger, we get better pricing and we get better systems and techniques, but

00:44:18.620 --> 00:44:20.860
<v Chris Gammell>you know, we get more stuff to put on the board as well.

00:44:20.860 --> 00:44:23.800
<v Chris Gammell>So it's, it's, it's always a big, big challenge every, every generation.

00:44:24.580 --> 00:44:25.460
<v Chris Gammell>Yeah, totally.

00:44:25.880 --> 00:44:26.100
<v Chris Gammell>Totally.

00:44:27.260 --> 00:44:29.640
<v Raspberry Pi>I mean, so you guys have talked a little bit about future stuff.

00:44:29.700 --> 00:44:33.200
<v Raspberry Pi>I mean, so more custom silicon in your future?

00:44:34.040 --> 00:44:34.620
<v Raspberry Pi>Good question.

00:44:34.780 --> 00:44:35.700
<v Raspberry Pi>We have a chip team now.

00:44:36.020 --> 00:44:36.180
<v Raspberry Pi>Yeah.

00:44:36.200 --> 00:44:37.320
<v Raspberry Pi>I mean, yeah, you got to use it, right?

00:44:37.400 --> 00:44:40.500
<v Raspberry Pi>So, uh, so I think, yes, you know, you don't put your best players on the bench.

00:44:40.580 --> 00:44:40.920
<v Raspberry Pi>Come on.

00:44:40.920 --> 00:44:47.640
<v Chris Gammell>So, um, we've, you know, we've, we've got a team, we've developed some nice, you know,

00:44:47.900 --> 00:44:52.240
<v Chris Gammell>part of the thing we're doing this kind of chip design is it takes a long time to get,

00:44:52.380 --> 00:44:55.680
<v Chris Gammell>get, get kind of all the flows and all the tools set up and all the rest of it and get

00:44:55.680 --> 00:44:57.460
<v Chris Gammell>people happily working, working together.

00:44:57.520 --> 00:44:57.700
<v Chris Gammell>Right.

00:44:57.740 --> 00:44:58.640
<v Chris Gammell>So we've got all that now.

00:44:58.920 --> 00:45:00.920
<v Chris Gammell>So yeah, there will be future stuff.

00:45:00.920 --> 00:45:08.180
<v Chris Gammell>If, uh, if everything goes smoothly, what that is, uh, I think I can't say we're not

00:45:08.180 --> 00:45:11.460
<v Chris Gammell>quite sure perhaps ourselves anyway, there's obviously some options.

00:45:11.940 --> 00:45:12.060
<v Raspberry Pi>Yeah.

00:45:12.180 --> 00:45:16.640
<v Chris Gammell>Someone asked me on Twitter, if we do a big, a big, you know, will we do a Raspberry Pi

00:45:16.640 --> 00:45:18.060
<v Chris Gammell>processor for the main Raspberry Pi board?

00:45:18.140 --> 00:45:19.960
<v Chris Gammell>You know, one of these big, big silicon SOCs.

00:45:20.340 --> 00:45:22.320
<v Chris Gammell>And the answer to that is definitely not.

00:45:22.320 --> 00:45:27.240
<v Chris Gammell>I think because that's kind of like a couple of orders of magnitude more difficult than doing,

00:45:27.380 --> 00:45:28.760
<v Chris Gammell>uh, doing, doing a microcontroller.

00:45:28.760 --> 00:45:31.980
<v Chris Gammell>But yeah, we'll see, you know?

00:45:32.360 --> 00:45:32.800
<v Raspberry Pi>Yeah.

00:45:32.820 --> 00:45:36.960
<v Raspberry Pi>I feel like at the cost basis you're at and because, so like the Broadcom chip that you

00:45:36.960 --> 00:45:42.340
<v Raspberry Pi>guys use and have been working with, I mean, it's just like, that's already so cost optimized

00:45:42.340 --> 00:45:46.120
<v Raspberry Pi>that it's, you know, you're, you're basically leaning into that in the first place.

00:45:46.120 --> 00:45:50.440
<v Raspberry Pi>It feels like, you know, basically pulling in all of the feature capabilities that Broadcom

00:45:50.440 --> 00:45:51.820
<v Raspberry Pi>does like, okay.

00:45:51.820 --> 00:45:56.600
<v Raspberry Pi>And especially on the graphic side, there's just, you have to be bare bones cost otherwise.

00:45:56.600 --> 00:46:01.840
<v Raspberry Pi>So you'd have to basically be planning to build millions of units and all of the cost stuff

00:46:01.840 --> 00:46:05.460
<v Raspberry Pi>to, to go and build a high powered graphics chip at the same level.

00:46:05.460 --> 00:46:07.640
<v Raspberry Pi>It would just be very difficult money, money-wise I would imagine.

00:46:08.100 --> 00:46:08.220
<v Chris Gammell>Yeah.

00:46:08.340 --> 00:46:08.560
<v Chris Gammell>Yeah.

00:46:08.560 --> 00:46:09.100
<v Chris Gammell>Pretty much that.

00:46:09.160 --> 00:46:11.100
<v Chris Gammell>I mean, the teams are much, much bigger.

00:46:11.360 --> 00:46:12.320
<v Chris Gammell>The silicon's bigger.

00:46:12.720 --> 00:46:13.840
<v Chris Gammell>You need more tool licenses.

00:46:13.840 --> 00:46:19.380
<v Chris Gammell>It takes a lot more time, you know, the, you know, the, all of the, everything just gets

00:46:19.380 --> 00:46:20.060
<v Chris Gammell>much, much harder.

00:46:20.180 --> 00:46:24.400
<v Chris Gammell>And then verification is, you know, sort of almost scales exponentially with, with the

00:46:24.400 --> 00:46:25.260
<v Chris Gammell>size of the system.

00:46:25.260 --> 00:46:29.420
<v Chris Gammell>So, uh, yeah, it's not something we're going to be thinking about anytime soon, but, um,

00:46:29.840 --> 00:46:31.860
<v Chris Gammell>but we will be, we will be definitely doing something.

00:46:32.300 --> 00:46:33.360
<v Chris Gammell>Uh, just what that is.

00:46:33.500 --> 00:46:35.640
<v Chris Gammell>I, we, I'm not really sure.

00:46:36.280 --> 00:46:37.680
<v Chris Gammell>Probably in a similar space, right?

00:46:37.980 --> 00:46:38.700
<v Chris Gammell>You'll figure it out.

00:46:38.700 --> 00:46:39.340
<v Chris Gammell>We'll figure it out, right?

00:46:39.360 --> 00:46:39.840
<v Chris Gammell>It's fine.

00:46:39.840 --> 00:46:44.260
<v Chris Gammell>I was going to say the challenge right now is just, you know, getting, getting the Pico

00:46:44.260 --> 00:46:47.880
<v Chris Gammell>out, getting the production ramped, getting the documentation, tidied up as people come

00:46:47.880 --> 00:46:49.080
<v Chris Gammell>up with bug requests in the SDK.

00:46:49.360 --> 00:46:51.460
<v Chris Gammell>So we're quite focused on that, on that right now.

00:46:51.820 --> 00:46:52.140
<v Raspberry Pi>Yeah.

00:46:52.180 --> 00:46:54.440
<v Raspberry Pi>Those, those robots aren't going to program themselves guys.

00:46:54.440 --> 00:46:57.640
<v Raspberry Pi>I mean, you know, someone's got to set them robots up for now, you know, until the robots

00:46:57.640 --> 00:46:59.620
<v Raspberry Pi>figure out robots and then we're in big trouble.

00:47:02.960 --> 00:47:07.800
<v Raspberry Pi>Uh, one thing that was surprising to me is, you know, 2021 on the amp hour, especially

00:47:07.800 --> 00:47:09.780
<v Raspberry Pi>we talk about risk five all the time.

00:47:10.460 --> 00:47:14.180
<v Raspberry Pi>And I think you've answered this question already, you know, having started in 2016, but I was

00:47:14.180 --> 00:47:18.180
<v Raspberry Pi>surprised that it wasn't risk five, but then again, like 2016, it's like risk five wasn't

00:47:18.180 --> 00:47:19.420
<v Raspberry Pi>a thing in, in 2016.

00:47:19.720 --> 00:47:21.580
<v Raspberry Pi>Is there thoughts about that in the future?

00:47:21.780 --> 00:47:24.820
<v Raspberry Pi>Looking, looking at, you know, more the open ISA type stuff.

00:47:25.220 --> 00:47:27.460
<v Luke Renn>Risk five was definitely around in, in 16.

00:47:27.920 --> 00:47:30.240
<v Luke Renn>Uh, I I'm personally a huge fan of risk five.

00:47:30.240 --> 00:47:33.780
<v Luke Renn>I mean, if you look at my GitHub, you can see risk five implementations I've worked on.

00:47:33.780 --> 00:47:38.660
<v Luke Renn>One of the things that really pushed us into QualixM is that at the point we had to freeze

00:47:38.660 --> 00:47:43.540
<v Luke Renn>this design at, you know, the block diagram level, the, I think the debug specification

00:47:43.540 --> 00:47:46.020
<v Luke Renn>for risk five was still in draft status.

00:47:46.320 --> 00:47:48.960
<v Luke Renn>So like risk five is a brilliant architecture.

00:47:49.080 --> 00:47:50.280
<v Luke Renn>It's a really beautiful piece of engineering.

00:47:50.480 --> 00:47:53.780
<v Luke Renn>There's a lot of, uh, great implementations out there already.

00:47:53.780 --> 00:47:57.960
<v Luke Renn>And even at that point, there were some great implementations, but the, the debug specification,

00:47:58.200 --> 00:47:59.540
<v Luke Renn>you know, that's not just JTAG.

00:47:59.540 --> 00:48:04.260
<v Luke Renn>That's things like new CSRs for the core, that's an entirely privileged mode.

00:48:04.260 --> 00:48:08.340
<v Luke Renn>So that's core semantics of your processor that are still subject to change whilst you're

00:48:08.340 --> 00:48:13.260
<v Luke Renn>trying to design a JTAG and debug really is everything in embedded because you can't

00:48:13.260 --> 00:48:14.880
<v Luke Renn>see inside the system any other way.

00:48:14.940 --> 00:48:17.060
<v Luke Renn>So we wanted something where the debug would just work.

00:48:17.180 --> 00:48:19.700
<v Luke Renn>There was existing open source infrastructure to build off a debug.

00:48:19.880 --> 00:48:21.300
<v Luke Renn>And that pushed us towards CortexM.

00:48:21.700 --> 00:48:24.540
<v Luke Renn>And we think the M0 plus is the best CortexM for this system.

00:48:25.420 --> 00:48:25.600
<v Raspberry Pi>Yeah.

00:48:25.820 --> 00:48:26.020
<v Raspberry Pi>Yeah.

00:48:26.020 --> 00:48:26.480
<v Raspberry Pi>That's interesting.

00:48:26.480 --> 00:48:26.660
<v Raspberry Pi>Yeah.

00:48:26.700 --> 00:48:31.720
<v Raspberry Pi>I, I kind of, I mean, in my own development too, like I'm not ever bleeding edge anything,

00:48:31.720 --> 00:48:36.400
<v Raspberry Pi>but I will, I will lean into like what's most popular and what is known to work as well.

00:48:36.400 --> 00:48:39.700
<v Raspberry Pi>Just because like, I don't, I don't have time to do that other stuff.

00:48:39.740 --> 00:48:43.720
<v Raspberry Pi>I'm not good enough, honestly, like as a, as a sole engineer, I'm not good enough to go

00:48:43.720 --> 00:48:44.160
<v Raspberry Pi>do that stuff.

00:48:44.340 --> 00:48:47.360
<v Raspberry Pi>You guys are good enough to go do that stuff, but you're trying to maintain low cost.

00:48:47.380 --> 00:48:49.740
<v Raspberry Pi>You're trying to maintain a huge user base.

00:48:49.760 --> 00:48:54.280
<v Raspberry Pi>I just imagine that would potentially be a big deal to, if it, if it didn't work at any

00:48:54.280 --> 00:48:56.160
<v Raspberry Pi>point, it would be just detrimental.

00:48:56.160 --> 00:48:59.540
<v Luke Renn>A processor is a huge, a huge project in its own right.

00:48:59.960 --> 00:49:03.440
<v Luke Renn>And it's not just designing it, you know, by the time you've got to, to running print

00:49:03.440 --> 00:49:06.080
<v Luke Renn>F on your processor, you're maybe five, 10% of the way there.

00:49:06.540 --> 00:49:07.640
<v Luke Renn>The rest of it is verification.

00:49:08.340 --> 00:49:12.060
<v Luke Renn>And that is a long multi-year project with a lot of people involved.

00:49:12.360 --> 00:49:17.700
<v Luke Renn>And in terms of getting a cheap microcontroller on the market, we weren't in a position to

00:49:17.700 --> 00:49:18.760
<v Luke Renn>start developing our own processor.

00:49:19.000 --> 00:49:22.680
<v Luke Renn>And we didn't feel like any of the existing implementations were the right fit at that

00:49:22.680 --> 00:49:22.860
<v Luke Renn>point.

00:49:22.860 --> 00:49:23.300
<v Luke Renn>Yeah.

00:49:23.300 --> 00:49:23.660
<v Raspberry Pi>Yeah.

00:49:23.860 --> 00:49:24.520
<v Raspberry Pi>That's interesting.

00:49:25.320 --> 00:49:30.340
<v Raspberry Pi>I mean, the, so you'd, you'd mentioned as well, Luke, like the M0 plus was the best fit.

00:49:30.420 --> 00:49:32.480
<v Raspberry Pi>Could you, could you explain that a little bit deeper?

00:49:33.140 --> 00:49:33.480
<v Luke Renn>Sure.

00:49:33.640 --> 00:49:39.640
<v Luke Renn>So on, on, on 40 nanometer, you can push M class cores up to higher frequencies than you

00:49:39.640 --> 00:49:42.180
<v Luke Renn>might traditionally expect to see that particular core.

00:49:42.180 --> 00:49:48.100
<v Luke Renn>So, you know, M0 plus, you may normally expect that to see clocked around 48 and M3 or an M4,

00:49:48.180 --> 00:49:49.520
<v Luke Renn>you might expect to see a little bit faster.

00:49:50.240 --> 00:49:52.480
<v Luke Renn>It's physically a very compact little core.

00:49:53.280 --> 00:49:55.480
<v Luke Renn>And on 40 nanometer, you can get it fast enough.

00:49:55.860 --> 00:50:00.220
<v Luke Renn>I mean, 133 for an M0 plus where pretty much every instruction is a single cycle.

00:50:00.920 --> 00:50:02.220
<v Luke Renn>It gets a lot done per clock.

00:50:02.320 --> 00:50:03.040
<v Luke Renn>You get a lot of clocks.

00:50:03.460 --> 00:50:05.460
<v Luke Renn>So actually you get a lot of throughput from M0 plus.

00:50:05.820 --> 00:50:09.660
<v Luke Renn>And the other thing is because we have a huge amount of, you know, have a lot of top,

00:50:09.840 --> 00:50:11.180
<v Luke Renn>top level bus fabric ports.

00:50:11.240 --> 00:50:12.320
<v Luke Renn>We have a lot of memory ports.

00:50:12.380 --> 00:50:13.760
<v Luke Renn>We get a lot of memory parallels.

00:50:13.920 --> 00:50:16.460
<v Luke Renn>And you want something that can just suck a lot of data through the system.

00:50:16.460 --> 00:50:22.780
<v Luke Renn>And again, two M0 pluses is a lot more throughput for random integer throughput than let's say

00:50:22.780 --> 00:50:25.360
<v Luke Renn>one M4, which takes up the same number of bus fabric ports.

00:50:26.140 --> 00:50:26.900
<v Raspberry Pi>Yeah, that's really interesting.

00:50:27.020 --> 00:50:28.520
<v Raspberry Pi>I had no idea about that.

00:50:28.580 --> 00:50:31.900
<v Raspberry Pi>That's really interesting from an optimization standpoint.

00:50:32.480 --> 00:50:33.460
<v Raspberry Pi>So that's really cool.

00:50:34.760 --> 00:50:38.420
<v Raspberry Pi>What about on the, so one thing that we, I think we mentioned last time, and I've definitely

00:50:38.420 --> 00:50:43.360
<v Raspberry Pi>talked to other people about, like you guys have chips out to other maker companies,

00:50:43.580 --> 00:50:45.200
<v Raspberry Pi>SparkFun, Adafruit, Arduino.

00:50:45.200 --> 00:50:49.400
<v Raspberry Pi>What about more broadly available RP2040s?

00:50:49.580 --> 00:50:52.500
<v Raspberry Pi>Like when can I buy one on a distributor website?

00:50:52.780 --> 00:50:55.340
<v Raspberry Pi>Is that coming or is that already there and I didn't look hard enough?

00:50:56.080 --> 00:50:56.840
<v Chris Gammell>So that's coming.

00:50:57.420 --> 00:51:04.020
<v Chris Gammell>We've publicly stated Q2 this year is when we're going to try and make that happen.

00:51:04.300 --> 00:51:10.980
<v Chris Gammell>It's obviously subject to fulfilling our internal pipeline of just building Picos.

00:51:10.980 --> 00:51:18.440
<v Chris Gammell>And yeah, we work with SparkFun, Adafruit, Pimeroni, and those guys gave them engineering

00:51:18.440 --> 00:51:21.780
<v Chris Gammell>silicon and made them sign a waiver saying, hey, we don't even think this is going to

00:51:21.780 --> 00:51:21.960
<v Chris Gammell>work.

00:51:22.020 --> 00:51:23.380
<v Chris Gammell>But if you want to go build a board, off you go.

00:51:23.960 --> 00:51:24.780
<v Chris Gammell>They're pretty happy with that.

00:51:24.780 --> 00:51:24.940
<v Chris Gammell>Yeah.

00:51:25.940 --> 00:51:28.400
<v Chris Gammell>And they produce some really great stuff.

00:51:29.520 --> 00:51:29.640
<v Raspberry Pi>Yeah.

00:51:29.640 --> 00:51:33.200
<v Raspberry Pi>I think I was watching Lemur's feed and she's mentioned like she only got 10 of them and

00:51:33.200 --> 00:51:34.880
<v Raspberry Pi>she was just like tried to build as many as she could with 10.

00:51:34.940 --> 00:51:35.980
<v Raspberry Pi>I was like, that is, that's awesome.

00:51:36.080 --> 00:51:37.200
<v Raspberry Pi>You know, like that's really cool.

00:51:37.200 --> 00:51:39.420
<v Raspberry Pi>Like that you guys were just spreading around like that.

00:51:39.560 --> 00:51:40.640
<v Raspberry Pi>I like, I like that methodology.

00:51:40.640 --> 00:51:46.400
<v Chris Gammell>Those guys have provided really good feedback on the device and the SDK and we've, you know,

00:51:46.540 --> 00:51:51.940
<v Chris Gammell>so, you know, it's been super helpful to have them on board and building products, right?

00:51:52.700 --> 00:51:54.460
<v Chris Gammell>It's very valuable for us to do that.

00:51:54.640 --> 00:51:56.860
<v Chris Gammell>And obviously we want people to go and build with this chip.

00:51:57.200 --> 00:52:02.660
<v Chris Gammell>So, you know, the intent is to make it available as a standalone device and hopefully we'll get

00:52:02.660 --> 00:52:03.620
<v Chris Gammell>there sooner than later.

00:52:03.980 --> 00:52:04.120
<v Raspberry Pi>Yeah.

00:52:04.260 --> 00:52:04.460
<v Raspberry Pi>Okay.

00:52:04.800 --> 00:52:08.620
<v Raspberry Pi>And then, and do you have, I mean, you're setting the Pico price at four bucks.

00:52:08.620 --> 00:52:15.080
<v Raspberry Pi>Are you doing the same for the RP2040 or is it more just normal chip kind of distributor stuff?

00:52:15.480 --> 00:52:17.160
<v Chris Gammell>So it won't be four bucks.

00:52:17.320 --> 00:52:19.860
<v Chris Gammell>It'll be significantly cheaper than that.

00:52:19.920 --> 00:52:25.200
<v Chris Gammell>We haven't decided on the final price yet, but we think a lot of people will probably just take the chip.

00:52:25.840 --> 00:52:26.180
<v Chris Gammell>But we'll see.

00:52:26.300 --> 00:52:31.940
<v Chris Gammell>I mean, Pico's got a bunch of other stuff integrated and it's very easy to solder into, you know, into projects.

00:52:32.280 --> 00:52:33.720
<v Chris Gammell>So, yeah, you'll get the choice.

00:52:34.480 --> 00:52:35.100
<v Raspberry Pi>Yeah, that's cool.

00:52:35.160 --> 00:52:36.960
<v Raspberry Pi>And I like the idea of on tape too.

00:52:36.960 --> 00:52:38.200
<v Raspberry Pi>That's interesting.

00:52:38.440 --> 00:52:42.040
<v Raspberry Pi>And I think that's going to fit a lot of, you know, a lot of projects type things.

00:52:42.200 --> 00:52:47.000
<v Raspberry Pi>I'm guessing we're going to see a Pico outline on a lot of boards in the near future here.

00:52:47.500 --> 00:52:48.120
<v Chris Gammell>I certainly hope so.

00:52:48.420 --> 00:52:48.540
<v Chris Gammell>Yeah.

00:52:48.540 --> 00:52:50.160
<v Chris Gammell>It was nice to get it in tape and reel, actually.

00:52:50.940 --> 00:52:55.080
<v Chris Gammell>Initially, we had a few ideas of maybe we could actually sell them as multiple.

00:52:55.460 --> 00:52:58.440
<v Chris Gammell>Because the problem here is trying to get the packaging cost low, right?

00:52:58.440 --> 00:53:05.820
<v Chris Gammell>So, it's some initial ideas where maybe you have like a, you sell a couple or three of them for some fixed cost and then you break them apart yourself.

00:53:05.820 --> 00:53:09.140
<v Chris Gammell>So, you're trying to aggregate the packaging cost across multiple modules.

00:53:09.140 --> 00:53:13.140
<v Chris Gammell>But in the end, I talked to some tape and reel guys.

00:53:13.960 --> 00:53:18.600
<v Chris Gammell>We weren't sure if that size of, you know, board would actually fit in the tape and reel.

00:53:18.680 --> 00:53:19.660
<v Chris Gammell>But it turned out, yeah, it did.

00:53:19.840 --> 00:53:24.420
<v Chris Gammell>So, it kind of seemed like a very obvious way to package and ship these things nice and easily.

00:53:24.420 --> 00:53:28.580
<v Chris Gammell>Especially as people might end up picking and placing them onto their own products.

00:53:28.680 --> 00:53:30.760
<v Chris Gammell>So, therefore, in tape and reel, it's kind of perfect.

00:53:31.080 --> 00:53:32.240
<v Chris Gammell>So, that works out very well.

00:53:33.580 --> 00:53:38.900
<v Raspberry Pi>I'm looking through other questions and a lot of them on the Twitter thing I asked for.

00:53:39.020 --> 00:53:41.980
<v Raspberry Pi>A lot of them are related to the Linux side of the house.

00:53:42.080 --> 00:53:44.040
<v Raspberry Pi>And I think we can maybe end with that.

00:53:44.620 --> 00:53:50.000
<v Raspberry Pi>But I guess before we switch to that, and I realize as well that you guys are the micro team.

00:53:50.000 --> 00:53:53.400
<v Raspberry Pi>So, it's like that's also just kind of a broad questioning set.

00:53:53.400 --> 00:53:55.520
<v Raspberry Pi>But what am I missing on the 2040?

00:53:55.620 --> 00:53:56.900
<v Raspberry Pi>Like, what are you guys most excited about?

00:53:57.060 --> 00:54:01.420
<v Raspberry Pi>What should people be digging under the hood for that they might not have heard about yet?

00:54:01.960 --> 00:54:08.300
<v Liam Fraser>One thing I would say that exists but needs a lot of software work is USB host.

00:54:08.980 --> 00:54:13.160
<v Liam Fraser>So, you know, most examples for microcontrollers have it as a USB device.

00:54:13.700 --> 00:54:15.900
<v Liam Fraser>But we can actually do USB host as well.

00:54:15.980 --> 00:54:22.780
<v Liam Fraser>But the problem with that is that the tiny USB stack that we use, the device side of it is very well supported.

00:54:22.780 --> 00:54:24.260
<v Liam Fraser>But the host side is very basic.

00:54:24.260 --> 00:54:26.920
<v Liam Fraser>So, you can basically plug in a keyboard and mouse.

00:54:27.640 --> 00:54:30.320
<v Liam Fraser>But, you know, I've had like USB sound cards working.

00:54:30.920 --> 00:54:31.200
<v Liam Fraser>Oh, wow.

00:54:31.500 --> 00:54:36.700
<v Liam Fraser>It would be really nice to get like a USB Ethernet device, you know, all that kind of stuff.

00:54:36.940 --> 00:54:43.200
<v Liam Fraser>But the problem is, is you don't, you know, if you plug a USB device into Linux, you've got the driver there.

00:54:43.200 --> 00:54:49.580
<v Liam Fraser>But you'd basically have to port a Linux driver over to the tiny USB host stack to get all this kind of stuff working.

00:54:50.060 --> 00:54:51.260
<v Liam Fraser>But it is possible.

00:54:51.620 --> 00:54:57.840
<v Liam Fraser>And it's kind of like the sort of, you know, one core debugging the other core and like the sleep modes and stuff.

00:54:57.840 --> 00:54:58.960
<v Liam Fraser>It's all possible.

00:54:58.960 --> 00:55:08.260
<v Liam Fraser>But you've got to sort of build your software differently, you know, to like not use the memory that you're powering down or not use the memory where the other core is running the debugger.

00:55:08.820 --> 00:55:13.440
<v Liam Fraser>So it's, and because it's a small team, we don't really have the time to like dedicate to that kind of stuff.

00:55:13.540 --> 00:55:15.960
<v Liam Fraser>But it's a great experiment for someone to do.

00:55:15.960 --> 00:55:25.000
<v Liam Fraser>Particularly if you've got a USB analyzer, you can, you know, plug a device into a Windows box, dump what it does, and then go and write a driver for it.

00:55:25.100 --> 00:55:26.260
<v Liam Fraser>And it's quite fun, actually.

00:55:27.040 --> 00:55:27.360
<v Raspberry Pi>That's cool.

00:55:27.700 --> 00:55:28.180
<v Raspberry Pi>That's great.

00:55:28.940 --> 00:55:29.480
<v Raspberry Pi>Other things?

00:55:29.680 --> 00:55:36.720
<v Raspberry Pi>I mean, I guess what I'm really hoping for is like there's like Easter eggs that you'll just tell me about, which is not really the point of Easter eggs.

00:55:36.880 --> 00:55:41.380
<v Raspberry Pi>But I guess also like as people are starting to buy, you know, they're so cheap.

00:55:41.460 --> 00:55:44.140
<v Raspberry Pi>I've seen people just like be like, well, yeah, I just threw them in my order.

00:55:44.140 --> 00:55:45.840
<v Raspberry Pi>I'm just going to buy a couple just to have them around.

00:55:46.660 --> 00:55:49.300
<v Raspberry Pi>But then what should people be thinking about?

00:55:49.400 --> 00:55:52.000
<v Raspberry Pi>Maybe, maybe not even just for the, you know, they can go check out the demos.

00:55:52.240 --> 00:55:54.980
<v Raspberry Pi>But then like thinking about like, how do we get these integrated into products?

00:55:55.020 --> 00:55:59.140
<v Raspberry Pi>What should people be thinking about these in product development side of things as well?

00:55:59.840 --> 00:56:03.020
<v Luke Renn>So in terms of integration, I think people are going to have a lot of fun with PIO.

00:56:03.540 --> 00:56:10.140
<v Luke Renn>You know, if you scroll through the data sheet or you look at the PIO chapter in the SDK book, that should give you a good idea of what it's about.

00:56:10.480 --> 00:56:12.700
<v Luke Renn>We set out to design something that could talk to anything.

00:56:12.700 --> 00:56:16.340
<v Luke Renn>I think we got about as close as we can with the hardware envelope that we have.

00:56:16.440 --> 00:56:18.160
<v Luke Renn>There are plenty of examples out there.

00:56:18.440 --> 00:56:25.860
<v Luke Renn>And then that's all about doing really tight deterministic IO to strange serial formats or parallel formats without any processor load.

00:56:25.860 --> 00:56:28.140
<v Luke Renn>You mentioned something about Easter eggs.

00:56:28.340 --> 00:56:34.340
<v Luke Renn>We do have one quite fun hardware Easter egg, which is the interpolator, which is some core local arithmetic hardware.

00:56:34.340 --> 00:56:38.320
<v Luke Renn>It's quite useful for, you know, fixed point DSP type things.

00:56:38.820 --> 00:56:42.800
<v Luke Renn>But the original purpose of that hardware was to run Super Mario Kart at 48 megahertz.

00:56:44.100 --> 00:56:45.920
<v Luke Renn>And you can have a lot of fun with that.

00:56:46.400 --> 00:56:56.340
<v Luke Renn>But I think PIO is my favorite feature in terms of integrating this into other hardware, which is, I think, the job of a microcontroller is to be the ambassador and the go between bits of digital hardware.

00:56:56.340 --> 00:56:56.460
<v Luke Renn>Yeah.

00:56:57.600 --> 00:56:57.960
<v Raspberry Pi>Yeah.

00:56:58.420 --> 00:56:58.640
<v Raspberry Pi>Yeah.

00:56:58.980 --> 00:56:59.340
<v Raspberry Pi>Yeah.

00:56:59.340 --> 00:57:04.520
<v Raspberry Pi>I think that's where I'm going to point people, especially for the, I think the demo stuff is like that, that kind of makes it feel like magic.

00:57:04.520 --> 00:57:12.500
<v Raspberry Pi>I mean, like one very obvious example I feel like is like just, you know, people love 28, WS 2812s and like, that's just such a messy serial format.

00:57:12.500 --> 00:57:16.560
<v Raspberry Pi>But like now it's not, you know, it's just like, okay.

00:57:16.560 --> 00:57:17.000
<v Raspberry Pi>Yes.

00:57:17.300 --> 00:57:20.540
<v Luke Renn>And a lot of people say, oh, you only get 32 instructions in the PIO.

00:57:20.940 --> 00:57:23.160
<v Luke Renn>A 2812 is four instructions total.

00:57:23.660 --> 00:57:30.260
<v Luke Renn>And you can just shovel pixel data into a FIFO and send it out to as many strings as you want at full speed without any processor overhead.

00:57:30.760 --> 00:57:33.540
<v Luke Renn>I don't think that's a particularly important industrial application.

00:57:34.040 --> 00:57:38.340
<v Luke Renn>But I think that the 2812 encapsulates a lot of the fun things about PIO quite nicely.

00:57:38.420 --> 00:57:41.340
<v Luke Renn>And there's a long write up about it in the SDK book.

00:57:41.740 --> 00:57:42.140
<v Raspberry Pi>Okay.

00:57:42.240 --> 00:57:42.660
<v Raspberry Pi>That's good.

00:57:42.700 --> 00:57:43.500
<v Raspberry Pi>I'll point people at that.

00:57:43.500 --> 00:57:43.900
<v Raspberry Pi>Yeah.

00:57:43.920 --> 00:57:49.140
<v Raspberry Pi>I mean, I remember at a friend who was trying to do like a, you know, a huge LED panel.

00:57:49.220 --> 00:57:50.320
<v Raspberry Pi>He was using WS 2812s.

00:57:50.360 --> 00:57:51.540
<v Raspberry Pi>He ran into a bunch of problems with it.

00:57:51.620 --> 00:57:53.300
<v Raspberry Pi>And then he used a BeagleBone Black, right?

00:57:53.320 --> 00:57:57.640
<v Raspberry Pi>And it's got PRUs in there and he had to do that and write all these spy drivers for it.

00:57:57.820 --> 00:58:01.080
<v Raspberry Pi>And it's like, but now it just gets smaller and simpler.

00:58:01.180 --> 00:58:04.420
<v Raspberry Pi>Like, you know, BeagleBone Black is a huge device comparatively, you know?

00:58:04.580 --> 00:58:09.840
<v Luke Renn>So I've seen a few comparisons between PIO and the PRUs on the Sitara.

00:58:09.840 --> 00:58:22.300
<v Luke Renn>I think if you take the scale of a Sitara where you have a big, I think it's a big Cortex A of some kind, and you have a little PRUs, which are kind of microcontroller cores, and you scale the whole system down to your Cortex A becomes an M0+.

00:58:22.300 --> 00:58:25.920
<v Luke Renn>You've got a similar size ratio between that and the PIO state machines.

00:58:26.700 --> 00:58:27.580
<v Luke Renn>It's the same job.

00:58:27.680 --> 00:58:32.060
<v Luke Renn>They offload stuff that is really hard real-time and low processing requirements from the processor.

00:58:32.520 --> 00:58:35.060
<v Luke Renn>The difference is the M0+, is already pretty good at hard real-time.

00:58:35.160 --> 00:58:40.320
<v Luke Renn>So it can take over some of the protocol stuff and PIO is just there to accelerate precise timing on the pins.

00:58:40.860 --> 00:58:42.760
<v Raspberry Pi>What about other low power type stuff?

00:58:42.840 --> 00:58:49.340
<v Raspberry Pi>I mean, is there other power modes that are maybe lower than expected because of 40 nanometers?

00:58:49.620 --> 00:58:51.080
<v Raspberry Pi>Or does that make it worse?

00:58:51.080 --> 00:58:55.540
<v Chris Gammell>So we use 40 LP.

00:58:56.100 --> 00:58:57.340
<v Chris Gammell>So that means low power.

00:58:57.960 --> 00:59:05.260
<v Chris Gammell>So that means the gate oxides are a bit thicker and some other magic stuff that I probably don't even understand that they do to basically...

00:59:05.260 --> 00:59:06.840
<v Raspberry Pi>Just for like leakages and things like that?

00:59:06.840 --> 00:59:15.300
<v Chris Gammell>Actually, what it does is it makes the leakage less and actually increases the dynamic power a bit, I think, because you're driving more capacitance on your MOSFET gates.

00:59:15.680 --> 00:59:15.760
<v Chris Gammell>Yeah.

00:59:15.760 --> 00:59:19.820
<v Chris Gammell>So we have put a few interesting things in for low power.

00:59:20.220 --> 00:59:23.680
<v Chris Gammell>But in general, we haven't engineered this for super ultra low power.

00:59:23.860 --> 00:59:32.200
<v Chris Gammell>And when I say super ultra low, I mean we're not doing any kind of crazy biasing to really get down into the tens of microamps type range.

00:59:32.200 --> 00:59:35.380
<v Chris Gammell>You know, there are microcontrollers out there that do that kind of thing.

00:59:35.820 --> 00:59:42.760
<v Chris Gammell>It's something that we are certainly interested in doing for any future silicon if we do another kind of microcontroller in this space.

00:59:43.140 --> 00:59:46.200
<v Chris Gammell>It's just a function of engineering team size, right?

00:59:46.620 --> 00:59:50.540
<v Chris Gammell>We chose to focus on the stuff that we're good at, which is the architecture, the digital side.

00:59:50.540 --> 00:59:55.460
<v Chris Gammell>And getting something out, a first shot at it to see what people think.

00:59:56.060 --> 00:59:58.620
<v Chris Gammell>So we've sort of done the best effort on some of the power stuff.

00:59:59.500 --> 01:00:03.700
<v Chris Gammell>I don't know if Liam or Luke want to talk about the dormant and coma modes.

01:00:04.860 --> 01:00:05.200
<v Liam Fraser>Yeah.

01:00:05.360 --> 01:00:09.560
<v Liam Fraser>So we've got two sort of modes of sleep, really.

01:00:09.820 --> 01:00:16.420
<v Liam Fraser>One is where you can send both of your processors into what they call deep sleep.

01:00:16.420 --> 01:00:23.640
<v Liam Fraser>And then once neither of the processors are requesting clocks, you can then turn off the clocks to most things.

01:00:23.860 --> 01:00:29.320
<v Liam Fraser>So there's basically a sleep enable register which says, what do you still want running?

01:00:29.740 --> 01:00:37.340
<v Liam Fraser>So in that case, you can basically run just like the RTC to wake you up in like two minutes time.

01:00:37.760 --> 01:00:42.360
<v Liam Fraser>And that will then wake you back up and only have that clock running.

01:00:42.360 --> 01:00:51.860
<v Liam Fraser>There's another mode called dormant mode, which we also call Tacoma mode internally, which basically stops all of the clocks running.

01:00:52.540 --> 01:00:55.600
<v Liam Fraser>So there's no clocks running on the chip at all.

01:00:56.080 --> 01:00:59.800
<v Liam Fraser>But you need some kind of external source to restart those clocks.

01:01:00.120 --> 01:01:04.620
<v Liam Fraser>So a GPIO edge or going high, that kind of thing.

01:01:05.040 --> 01:01:10.980
<v Liam Fraser>And you could, for example, keep the RTC running by supplying an external time reference to it.

01:01:10.980 --> 01:01:15.840
<v Liam Fraser>But the oscillator and the ring oscillator are both stopped.

01:01:16.520 --> 01:01:22.280
<v Liam Fraser>And then on top of that, we've got memory power downs, which do definitely help with your power consumption.

01:01:22.500 --> 01:01:27.300
<v Liam Fraser>But like I say, it's tricky to build the software when you start turning off memories,

01:01:27.520 --> 01:01:32.160
<v Liam Fraser>especially because our memories are laid out in a sort of striped pattern.

01:01:32.160 --> 01:01:35.100
<v Liam Fraser>So you get better performance out of it by default.

01:01:35.880 --> 01:01:36.040
<v Luke Renn>All right.

01:01:36.380 --> 01:01:39.280
<v Luke Renn>So we put quite a lot of work into the dynamic power side of things.

01:01:39.280 --> 01:01:40.620
<v Luke Renn>I think we've done pretty well there.

01:01:40.860 --> 01:01:45.940
<v Luke Renn>And the dormant mode where you turn off every oscillator in the chip, as well as every top level clock gate, it's quite neat.

01:01:46.500 --> 01:01:48.860
<v Luke Renn>We don't do quite so well on the static power side of things.

01:01:49.020 --> 01:01:52.560
<v Luke Renn>Part of that is, as a compromise, we only have one core power domain.

01:01:52.900 --> 01:01:56.140
<v Luke Renn>And that means we can get great power integrity with a pretty shallow metal stack,

01:01:56.420 --> 01:02:00.620
<v Luke Renn>which is important to run lots of logic fast on a very low cost die.

01:02:00.620 --> 01:02:05.000
<v Luke Renn>But that does mean that it does leak quite a bit in its lowest power sleep state.

01:02:05.520 --> 01:02:10.340
<v Luke Renn>We are looking at re-qualifying the silicon at higher and lower operating voltages,

01:02:10.340 --> 01:02:15.980
<v Luke Renn>which will give you a little bit more headroom at the top and also let you get a slightly lower sleep current.

01:02:16.200 --> 01:02:17.120
<v Luke Renn>But that's future work.

01:02:17.600 --> 01:02:17.740
<v Raspberry Pi>Okay.

01:02:18.180 --> 01:02:18.880
<v Raspberry Pi>Yeah, that's great.

01:02:18.960 --> 01:02:22.460
<v Raspberry Pi>I think it comes back to the goals for the project.

01:02:22.460 --> 01:02:28.560
<v Raspberry Pi>It seems like performance at low cost, that's kind of what it feels like it keeps coming back to.

01:02:29.140 --> 01:02:30.660
<v Raspberry Pi>And it seems like you guys have hit that.

01:02:31.120 --> 01:02:31.280
<v Raspberry Pi>Yes.

01:02:31.420 --> 01:02:34.180
<v Luke Renn>And especially memory at low cost, which I think is going to,

01:02:34.560 --> 01:02:40.540
<v Luke Renn>that's what enables you to use really dynamic programming languages like MicroPython in a more serious embedded context.

01:02:42.060 --> 01:02:42.500
<v Raspberry Pi>Yeah.

01:02:42.800 --> 01:02:42.940
<v Raspberry Pi>Yeah.

01:02:43.180 --> 01:02:47.880
<v Raspberry Pi>And then that drives accessibility, that drives ease of use, that kind of stuff.

01:02:47.880 --> 01:02:51.040
<v Raspberry Pi>And really that, that fits, it seems to fit well.

01:02:51.460 --> 01:02:57.760
<v Raspberry Pi>I think you guys have painted a really good picture of like how it fits into the Raspberry Pi mission and what you guys have been trying to do.

01:02:57.780 --> 01:02:59.460
<v Luke Renn>It fits nicely into our educational mission.

01:02:59.600 --> 01:03:06.460
<v Luke Renn>I also think it's an interesting thing for software engineers, embedded software engineers to use really low cost devices that have a lot of memory available,

01:03:06.460 --> 01:03:08.300
<v Luke Renn>because it changes the way you develop your software.

01:03:08.880 --> 01:03:13.900
<v Luke Renn>And your billable hours as a, particularly as a consultant, are also a part of your cost of that board.

01:03:13.900 --> 01:03:18.820
<v Luke Renn>If you're making 1,000, maybe you're happy to spend an extra five cents on the silicon and save yourself six hours of work.

01:03:19.560 --> 01:03:19.700
<v Raspberry Pi>Yep.

01:03:19.960 --> 01:03:20.160
<v Raspberry Pi>Yep.

01:03:20.200 --> 01:03:20.720
<v Raspberry Pi>That makes sense.

01:03:21.020 --> 01:03:21.120
<v Raspberry Pi>Yeah.

01:03:21.140 --> 01:03:24.600
<v Raspberry Pi>And I mean, I mean, I play mostly in the industrial space too.

01:03:24.800 --> 01:03:30.060
<v Raspberry Pi>And like, you know, looking at the PIO, that fits, that tickles all the right industrial nerves for me.

01:03:30.140 --> 01:03:32.340
<v Raspberry Pi>I think that like, that kind of like offloading, that's great.

01:03:32.720 --> 01:03:34.440
<v Raspberry Pi>And then anything else I'm doing is not like-

01:03:34.440 --> 01:03:38.560
<v Luke Renn>We have some really fun uses of PIO coming up in some of our internal stuff.

01:03:38.900 --> 01:03:43.220
<v Luke Renn>It's quite useful if you have some digital format on the board that's just coming out in not quite the right format,

01:03:43.220 --> 01:03:46.820
<v Luke Renn>and you need to bridge it into some memory, buffer it, process it, send it back out.

01:03:47.380 --> 01:03:49.920
<v Luke Renn>We're looking at integrating RP2040 and some of our stuff.

01:03:50.060 --> 01:03:51.320
<v Luke Renn>And PIO is a big part of that.

01:03:52.660 --> 01:03:52.980
<v Raspberry Pi>Yeah.

01:03:53.280 --> 01:03:53.880
<v Raspberry Pi>Yeah, that's great.

01:03:54.020 --> 01:03:57.800
<v Raspberry Pi>And I, yeah, I just think on the industrial side, it's just not, not that power constrained.

01:03:57.940 --> 01:04:03.900
<v Raspberry Pi>I mean, so the fact that it's not is like, I feel like there's, you know, there are like, like I think James said,

01:04:03.920 --> 01:04:07.080
<v Raspberry Pi>there's, there's different levels of, you know, how low power do you really need to go?

01:04:07.080 --> 01:04:13.120
<v Raspberry Pi>I don't see this going into any, like, you know, I don't see this going into a Fitbit anytime soon.

01:04:13.620 --> 01:04:20.320
<v Raspberry Pi>But at the same time, there might be other software tricks that people come up with to put it into the low power modes as needed.

01:04:20.600 --> 01:04:21.020
<v Raspberry Pi>And yeah.

01:04:21.300 --> 01:04:25.820
<v Raspberry Pi>So I feel like we're just so early days, it's, it's hard to, to put it into one corner anyways.

01:04:26.520 --> 01:04:26.920
<v Luke Renn>Yeah.

01:04:26.940 --> 01:04:27.840
<v Luke Renn>It's, it's all trade-offs.

01:04:27.920 --> 01:04:31.840
<v Luke Renn>I mean, we're in a completely different class, clearly from a big CordX 8 SOC.

01:04:31.840 --> 01:04:35.020
<v Luke Renn>Obviously we aren't in the hundred nanoamp sleep current class.

01:04:35.240 --> 01:04:41.220
<v Luke Renn>And I think that we have use cases where, where you won't get the performance you want at the cost unless you choose RB2040.

01:04:41.540 --> 01:04:43.560
<v Raspberry Pi>So that's cool.

01:04:44.160 --> 01:04:44.660
<v Raspberry Pi>All right.

01:04:44.660 --> 01:04:47.700
<v Raspberry Pi>So let's dip quickly into the, uh, under the Linux side.

01:04:47.800 --> 01:04:50.100
<v Raspberry Pi>I know that you guys are the embedded thing.

01:04:50.180 --> 01:05:00.700
<v Raspberry Pi>So maybe this is mostly for James, but there were some questions around, you know, just generally around, I have my own questions around the CM4 and things like that, where you guys see that going.

01:05:00.700 --> 01:05:04.700
<v Raspberry Pi>I think the industrial focus or the, you know, the broadly available focus is interesting as well.

01:05:05.200 --> 01:05:07.740
<v Raspberry Pi>What do you, what do you think into the future?

01:05:08.200 --> 01:05:15.480
<v Raspberry Pi>Raspberry Pi kind of, I guess, Raspberry Pi trading and being this hardware company and then, you know, having the educational mission on the foundation side.

01:05:15.760 --> 01:05:22.500
<v Raspberry Pi>But now you're, I think I keep seeing the, you know, Raspberry Pi making millions of units a year that are going into industrial products.

01:05:22.500 --> 01:05:24.060
<v Raspberry Pi>So like, what is that trade-off?

01:05:24.100 --> 01:05:33.100
<v Raspberry Pi>How does that end up playing into the, to the, the company and how you're thinking about things with both the CM4, the Raspberry Pi 4, and then I guess RB2040 as well?

01:05:33.860 --> 01:05:34.140
<v Chris Gammell>Okay.

01:05:34.720 --> 01:05:35.780
<v Chris Gammell>It's a, it's a great question.

01:05:36.500 --> 01:05:45.820
<v Chris Gammell>So we, I mean, a long time ago now, you know, we, we noticed that people were putting Raspberry Pis into, into products and, you know, they're buying Raspberry Pis, putting them in their box and selling them.

01:05:45.820 --> 01:05:51.200
<v Chris Gammell>And that was kind of the, sort of the genesis of the original compute module.

01:05:51.360 --> 01:06:04.300
<v Chris Gammell>So I put together the original compute module partly because I thought it was a thing that should exist because we had this nice platform, but you know, there's, there's, there was obviously lots of options for form factors that we didn't choose.

01:06:04.300 --> 01:06:07.660
<v Chris Gammell>And it would have been nice to make a thing that people could build with.

01:06:07.740 --> 01:06:11.900
<v Chris Gammell>And it was also a nod to the industrial guys, but I guess it was kind of an experiment at the beginning.

01:06:12.180 --> 01:06:13.420
<v Chris Gammell>How well is this going to go?

01:06:13.480 --> 01:06:13.680
<v Chris Gammell>Right.

01:06:13.680 --> 01:06:13.720
<v Chris Gammell>Right.

01:06:13.940 --> 01:06:16.460
<v Chris Gammell>But we've continually built on that.

01:06:16.740 --> 01:06:16.920
<v Chris Gammell>Right.

01:06:17.000 --> 01:06:21.240
<v Chris Gammell>At the beginning, it was pretty, well, it was unknown in, on the compute module side.

01:06:21.300 --> 01:06:21.400
<v Chris Gammell>Right.

01:06:21.400 --> 01:06:27.440
<v Chris Gammell>So people were still using Raspberry Pis in, in products, but not to a sort of serious degree, if you like.

01:06:27.860 --> 01:06:28.760
<v Chris Gammell>Compute module comes along.

01:06:29.040 --> 01:06:32.720
<v Chris Gammell>They probably still thought, well, you know, what's Raspberry Pi doing, making this kind of stuff.

01:06:32.900 --> 01:06:34.420
<v Chris Gammell>So some people started to pick it up.

01:06:34.660 --> 01:06:36.080
<v Chris Gammell>So it's been a kind of a slow burn.

01:06:36.080 --> 01:06:40.880
<v Chris Gammell>So then we released CM3, CM3, and then CM3 plus compute modules.

01:06:40.880 --> 01:06:43.840
<v Chris Gammell>And we've continued to, you know, produce Raspberry Pis.

01:06:43.940 --> 01:06:48.660
<v Chris Gammell>So people, I think now people can see we're quite serious in, you know, in this kind of space.

01:06:48.660 --> 01:06:48.980
<v Chris Gammell>Right.

01:06:48.980 --> 01:06:55.680
<v Chris Gammell>So we are kind of, when we design any product now, we are thinking of the industrial applications for it.

01:06:55.680 --> 01:07:07.860
<v Chris Gammell>So, for example, when I designed Pi 4, I went through the bill of materials to make sure that basically all of the stuff that we put on the Pi 4 board is completely suitable to put on the CM4.

01:07:08.080 --> 01:07:08.100
<v Chris Gammell>Right.

01:07:08.180 --> 01:07:10.780
<v Chris Gammell>So, you know, we use all the components.

01:07:10.780 --> 01:07:14.380
<v Chris Gammell>I mean, we're not industrial temperature necessarily.

01:07:14.740 --> 01:07:14.840
<v Chris Gammell>Right.

01:07:14.860 --> 01:07:16.400
<v Chris Gammell>We're not at minus 40 to 125.

01:07:16.800 --> 01:07:19.600
<v Chris Gammell>We still use sort of commercial grade chips for stuff.

01:07:20.200 --> 01:07:25.940
<v Chris Gammell>But where we, you know, but we do pay attention to all of the other stuff that can get you.

01:07:26.020 --> 01:07:26.180
<v Chris Gammell>Right.

01:07:26.240 --> 01:07:35.920
<v Chris Gammell>So we make sure that, you know, we do a good job of making sure that, you know, all the stuff we choose is, you know, the crystals are rated at, you know, minus 20 to plus 85.

01:07:35.920 --> 01:07:43.200
<v Chris Gammell>And, you know, basically nothing's going to noble us and then we can just pull that straight over to the compute module, which is what's happened on the sort of Pi 4.

01:07:43.520 --> 01:07:48.320
<v Chris Gammell>Dominic did a great job of taking that and reforming it into the CM4.

01:07:48.580 --> 01:07:50.760
<v Chris Gammell>But it's kind of, you know, the kind of the same hardware.

01:07:50.940 --> 01:08:00.060
<v Chris Gammell>I guess the only real change is the fact that we've swapped out the Ethernet Phi from a slightly cheaper, lower, what's the word?

01:08:00.760 --> 01:08:03.940
<v Chris Gammell>So the one on the Pi 4 doesn't do some of the more industrial Ethernet-y type stuff.

01:08:03.940 --> 01:08:07.660
<v Chris Gammell>So we put a slightly more expensive one on the CM4 so it can do that, do that stuff.

01:08:07.760 --> 01:08:07.820
<v Chris Gammell>Yeah.

01:08:07.880 --> 01:08:08.540
<v Chris Gammell>Lower capability.

01:08:08.840 --> 01:08:11.380
<v Chris Gammell>Pretty much it's, other than that, it's the same stuff, right?

01:08:11.420 --> 01:08:13.440
<v Chris Gammell>The same caps, the same silicon, the same crystals.

01:08:14.160 --> 01:08:19.820
<v Chris Gammell>And we know that people put Raspberry Pi, you know, the main Pi product in their product still, you know, that's still a big, a big market.

01:08:19.820 --> 01:08:31.280
<v Chris Gammell>And now they have the option to put compute modules in which, so if they want to choose to do their own form factor or have the industrial Ethernet or, you know, have the MMC flash on the device, then they can go do that.

01:08:31.280 --> 01:08:39.360
<v Chris Gammell>So it's just been a thing that we've grown and it took a while for people, as I said, for people to realize we were kind of serious in this space.

01:08:39.680 --> 01:08:44.420
<v Chris Gammell>But now we've got, you know, we've got several generations of modular industrial products.

01:08:44.420 --> 01:08:50.100
<v Chris Gammell>We've got a lot more sort of collateral on the, you know, documentation and a data sheet side.

01:08:50.500 --> 01:08:55.340
<v Chris Gammell>We've got the compliance program that Roger Thornton put together.

01:08:55.340 --> 01:09:07.620
<v Chris Gammell>So that makes it easy for anyone taking Raspberry Pi compute modules or Raspberry Pis to integrate them into their product and go through the same compliance house that we use for our products, right?

01:09:07.700 --> 01:09:09.700
<v Chris Gammell>So that compliance house is UL.

01:09:10.100 --> 01:09:14.680
<v Chris Gammell>They know how they have all of the test kit and the software that we use for our own products.

01:09:14.680 --> 01:09:21.440
<v Chris Gammell>So they can easily help people build their products if they're based on the Raspberry Pi products, if that makes sense.

01:09:21.500 --> 01:09:26.720
<v Chris Gammell>So we're kind of building this, you know, we're building out this structure to help people with their industrial design.

01:09:26.900 --> 01:09:32.380
<v Chris Gammell>Because actually, that kind of compliance and all of that kind of stuff, it's really hard and frustrating when you first get started.

01:09:32.640 --> 01:09:36.680
<v Chris Gammell>And it's really, it kind of feels nice to help people along that journey.

01:09:36.880 --> 01:09:39.200
<v Chris Gammell>And of course, it helps sell us, sell products as well.

01:09:39.580 --> 01:09:39.680
<v Raspberry Pi>Yeah.

01:09:39.680 --> 01:09:41.640
<v Raspberry Pi>And I think that that drives down costs as well.

01:09:41.780 --> 01:09:48.800
<v Raspberry Pi>I mean, it sounds, that kind of thing is, it seems like that's what other module makers do.

01:09:48.860 --> 01:09:50.760
<v Raspberry Pi>It's not like you guys started as a module maker, right?

01:09:50.760 --> 01:09:56.280
<v Raspberry Pi>It's not like you're selling only industrial modules that, you know, with super crazy ratings or anything like that.

01:09:56.380 --> 01:10:01.260
<v Raspberry Pi>But it's, it seems like a natural progression into that space, especially to get volumes up.

01:10:01.260 --> 01:10:07.900
<v Raspberry Pi>And I think kind of everyone, everyone benefits from that then because it helps to fund Raspberry Pi for future, future things.

01:10:07.900 --> 01:10:12.440
<v Raspberry Pi>And, you know, more hardening, more, more Raspberry Pis everywhere, really.

01:10:12.660 --> 01:10:13.500
<v Raspberry Pi>So that's, that part's great.

01:10:13.500 --> 01:10:21.580
<v Chris Gammell>And of course, we apply our kind of costing model to the CM4 as well as Pico, which is, you know, we try and cap the maximum price, right?

01:10:21.620 --> 01:10:30.900
<v Chris Gammell>So people, you know, we don't disadvantage the guy in the shed who only wants to build a hundred things versus the big guys who can afford the, you know, the many thousands of units.

01:10:31.860 --> 01:10:38.220
<v Raspberry Pi>Yeah, I do feel like that, that drives a lot of the, that drives a lot of the things that I've seen, you know, on the consulting side, hobby side, whatever, right?

01:10:38.220 --> 01:10:47.940
<v Raspberry Pi>Someone who wants to buy, wants to build a hundred of something, you know, even with the CM3, it was out there, but like the, it was hard to kind of get that stuff implemented.

01:10:47.940 --> 01:10:50.880
<v Raspberry Pi>It felt like, but now it just feels like it's getting easier and easier.

01:10:50.940 --> 01:10:52.560
<v Raspberry Pi>I've seen a lot of CM4s out in the marketplace.

01:10:52.560 --> 01:10:53.520
<v Raspberry Pi>I'm using one myself.

01:10:53.980 --> 01:11:00.520
<v Raspberry Pi>I mean, I, I think it's just, I think this is a model that is, has existed with module based design.

01:11:00.520 --> 01:11:11.320
<v Raspberry Pi>It's, there's nothing new in that regard, but I think that that, I think we're going to start seeing that more and more in terms of maker projects all the way up through industrial projects or professional projects, I suppose.

01:11:11.320 --> 01:11:25.700
<v Chris Gammell>I think the key thing, the things that we've done with CM4, we've integrated more stuff and we've also integrated a simpler, we've integrated all the power chain as well, which is actually quite critical because you only have to supply five volts and it will go and do stuff.

01:11:25.800 --> 01:11:25.980
<v Chris Gammell>Right.

01:11:25.980 --> 01:11:33.560
<v Chris Gammell>So we've just taken away that last bit of energy barrier with the CM3 plus you had to supply several supplies and make sure the sequencing was correct.

01:11:33.820 --> 01:11:39.320
<v Chris Gammell>So, you know, uh, uh, and now, but now you buy a thing, it's got flash wifi ethernet.

01:11:39.400 --> 01:11:41.920
<v Chris Gammell>You just need some wires and a five volt supply and off you go.

01:11:43.200 --> 01:11:43.520
<v Raspberry Pi>Yeah.

01:11:43.540 --> 01:11:48.600
<v Raspberry Pi>I have to say, I do wish the, I wish the, the input was three volts, three, three, but that's just a personal gripe.

01:11:48.640 --> 01:11:49.580
<v Raspberry Pi>You don't have to listen to me on that.

01:11:49.580 --> 01:11:53.980
<v Raspberry Pi>I wish there was like a, like a solder jumper so I could just bypass the stuff.

01:11:54.040 --> 01:11:58.940
<v Raspberry Pi>But I realized with the sequencing, like you're saying, it's all optimized for plug in and a USB connector.

01:11:58.940 --> 01:11:59.240
<v Raspberry Pi>Right.

01:11:59.240 --> 01:12:01.560
<v Raspberry Pi>So it's like, it's already built for that, but yeah.

01:12:01.560 --> 01:12:03.640
<v Chris Gammell>Are you thinking of lithium ion batteries?

01:12:03.760 --> 01:12:04.160
<v Chris Gammell>Is that your.

01:12:04.960 --> 01:12:05.320
<v Chris Gammell>Exactly.

01:12:05.580 --> 01:12:05.860
<v Chris Gammell>Yep.

01:12:05.860 --> 01:12:06.180
<v Raspberry Pi>Exactly.

01:12:06.180 --> 01:12:06.440
<v Raspberry Pi>Right.

01:12:06.440 --> 01:12:06.580
<v Raspberry Pi>Yeah.

01:12:06.620 --> 01:12:14.820
<v Raspberry Pi>I mean, and that's by boost converters are part of my, you know, ecosystem and similar things like on the ABC board that I do, which is power back powering a pie.

01:12:14.820 --> 01:12:18.920
<v Raspberry Pi>It uses a BQ 25, eight, nine, five, which is a great little chip for that sort of thing.

01:12:19.220 --> 01:12:26.160
<v Raspberry Pi>And like, just to be able to, to basically look like I'm doing a USB on the go.

01:12:26.320 --> 01:12:37.480
<v Raspberry Pi>Basically that's, that's how I get around it is basically I, I plug, I plug the output or sorry, the input of the pie is the output of a USB on the go chip effectively so that I can back power with five volts.

01:12:37.720 --> 01:12:40.880
<v Raspberry Pi>But then it's boosting and all the noise from that side of things.

01:12:41.680 --> 01:12:42.700
<v Raspberry Pi>That's just a personal gripe.

01:12:42.760 --> 01:12:43.300
<v Raspberry Pi>You can ignore me.

01:12:43.320 --> 01:12:43.620
<v Raspberry Pi>It's fine.

01:12:44.820 --> 01:12:45.880
<v Chris Gammell>No, it's, it's fine.

01:12:45.960 --> 01:12:51.700
<v Chris Gammell>I mean, the original, the original compute module was designed with this in mind, but that's why we had those multiple supplies.

01:12:51.700 --> 01:12:51.940
<v Chris Gammell>Right.

01:12:51.980 --> 01:12:54.320
<v Chris Gammell>So you could, you could do your own thing, but that makes it more complicated.

01:12:54.700 --> 01:13:02.660
<v Chris Gammell>And the, the, the, the switcher silicon, the, the PMIC on, on, um, pie four, uh, it's, it doesn't go down to three V three.

01:13:02.740 --> 01:13:02.920
<v Chris Gammell>Right.

01:13:03.080 --> 01:13:03.400
<v Chris Gammell>Unfortunately.

01:13:03.700 --> 01:13:06.380
<v Chris Gammell>So it's, uh, it is what it is.

01:13:06.720 --> 01:13:06.840
<v Raspberry Pi>Yeah.

01:13:06.860 --> 01:13:14.640
<v Raspberry Pi>And again, it's, it totally makes sense from like, like, I think that's the thing when, when all of these decisions are out there, it's like, man, I would, I would have made the same decisions.

01:13:14.640 --> 01:13:17.580
<v Raspberry Pi>You know, like, it's just like from a logical perspective, it makes sense.

01:13:17.580 --> 01:13:22.900
<v Raspberry Pi>I just feel like when there's, I, I, I haven't been, well, I haven't been able to talk to you guys yet and now I get to.

01:13:22.900 --> 01:13:24.300
<v Raspberry Pi>And so I feel very blessed for that.

01:13:24.300 --> 01:13:27.420
<v Raspberry Pi>Uh, so, uh, I'll call you guys next time.

01:13:27.500 --> 01:13:29.120
<v Raspberry Pi>I have a great, but, uh, not really.

01:13:29.500 --> 01:13:34.900
<v Raspberry Pi>Uh, let's see some other questions we had out there.

01:13:35.360 --> 01:13:37.780
<v Raspberry Pi>Uh, why dual HDMI?

01:13:38.120 --> 01:13:40.080
<v Raspberry Pi>Why, what was the, what was the thinking behind that?

01:13:40.280 --> 01:13:43.580
<v Raspberry Pi>I guess that's on the four, but versus like a full size single.

01:13:43.580 --> 01:13:44.680
<v Chris Gammell>Yeah, sure.

01:13:44.680 --> 01:13:46.540
<v Chris Gammell>Uh, that's quite, I think it's quite an easy one.

01:13:46.600 --> 01:13:49.080
<v Chris Gammell>It's we kind of think of the pie as a PC, right?

01:13:49.180 --> 01:13:50.860
<v Chris Gammell>We think that's a pretty valid use case.

01:13:50.860 --> 01:13:53.580
<v Chris Gammell>And as, as the generations progress, we get faster and faster.

01:13:53.580 --> 01:14:01.320
<v Chris Gammell>So Raspberry Pi four is now a fairly, you know, convincing desktop, uh, Linux machine, obviously not for.

01:14:01.680 --> 01:14:01.840
<v Raspberry Pi>Yeah.

01:14:01.840 --> 01:14:07.380
<v Raspberry Pi>Including the, the a hundred, I forget the name of the, the little keyboard thingy that's attached to the pie.

01:14:07.380 --> 01:14:07.420
<v Raspberry Pi>Yeah.

01:14:08.060 --> 01:14:08.300
<v Raspberry Pi>Yeah.

01:14:08.400 --> 01:14:14.740
<v Chris Gammell>So it just, you know, if you've got a, a, a computer often you want multiple screens.

01:14:14.740 --> 01:14:17.700
<v Chris Gammell>So, uh, we just thought, you know, this is a great feature.

01:14:17.880 --> 01:14:21.420
<v Chris Gammell>It's also kind of nice cause it's a feature that no one else really could offer.

01:14:21.420 --> 01:14:30.600
<v Chris Gammell>And because we get, because we work closely with Broadcom to sort of specify the architecture for these devices, we, we could sort of add it as a, okay, let's just add another HDMI.

01:14:31.300 --> 01:14:37.200
<v Chris Gammell>And, uh, I mean, it's obviously not quite that simple, but, um, it's just a feature that we think.

01:14:37.620 --> 01:14:44.700
<v Chris Gammell>You know, people would value and would be useful, especially in this kind of PC, you know, productivity machine or, uh, type, uh, use case.

01:14:45.360 --> 01:14:46.320
<v Raspberry Pi>Okay, cool.

01:14:46.980 --> 01:14:49.100
<v Raspberry Pi>I'm trying to make sure I cover all these questions.

01:14:49.100 --> 01:14:55.680
<v Raspberry Pi>Some of them are silly, so I'm going to skip some of them on the, I guess, I guess kind of on that working with Broadcom thing as well.

01:14:55.680 --> 01:15:00.480
<v Raspberry Pi>I mean, is it like, uh, you get what you get in terms of the chip that you're working with?

01:15:00.780 --> 01:15:04.180
<v Raspberry Pi>I guess, I don't even know is between the three and four has, has the chip changed recently?

01:15:04.180 --> 01:15:07.360
<v Raspberry Pi>Like when, when, when does that chip decision get made?

01:15:07.380 --> 01:15:09.800
<v Chris Gammell>So, okay.

01:15:09.900 --> 01:15:23.720
<v Chris Gammell>So back in the day, the, uh, the 2835 chip that we originally used on the, the very original Raspberry Pis and the, and the, you know, the, the sort of Gen one and the zero, that device already existed.

01:15:23.720 --> 01:15:25.780
<v Chris Gammell>It was built before Raspberry Pi was a thing.

01:15:26.000 --> 01:15:29.420
<v Chris Gammell>It was the thing that, um, so I, I used to work for Broadcom.

01:15:29.560 --> 01:15:30.880
<v Chris Gammell>Hebron used to work for Broadcom.

01:15:31.340 --> 01:15:37.860
<v Chris Gammell>In fact, quite a few of the people in the, in the, in the, in the team, the Raspberry Pi team today are ex-Broadcomers who actually worked on that chip.

01:15:37.860 --> 01:15:38.140
<v Chris Gammell>Yeah.

01:15:38.140 --> 01:15:38.860
<v Chris Gammell>Back in the day.

01:15:38.860 --> 01:15:39.080
<v Chris Gammell>Right.

01:15:39.160 --> 01:15:52.100
<v Chris Gammell>So I, uh, in, in, in my old life, I, I, I was kind of the founder of the video core graphics team within Broadcom many years ago and sort of disappeared off in 2009 to do other things for a bit before coming back to Raspberry Pi.

01:15:52.100 --> 01:16:01.520
<v Chris Gammell>But, um, it existed Eben, that was the sort of Eben's realization was, Hey, this is the chip that I could use for the thing that I've been wanting to build for ages, which is the Raspberry Pi.

01:16:01.600 --> 01:16:01.780
<v Chris Gammell>Right.

01:16:02.000 --> 01:16:03.340
<v Chris Gammell>Um, and that's kind of how it booted up.

01:16:03.380 --> 01:16:09.160
<v Chris Gammell>So that already existed, but then we already had kind of a, uh, you know, we obviously knew Broadcom very well.

01:16:10.160 --> 01:16:15.820
<v Chris Gammell>And for subsequent chips, we've always been able to have a bit of input in, Hey, you know, can you do us a chip that will do this?

01:16:15.960 --> 01:16:20.020
<v Chris Gammell>And usually it's an evolution of something they've already got or an evolution of the thing we've already got.

01:16:20.020 --> 01:16:27.380
<v Chris Gammell>So, you know, up to Pi three B plus, even we basically, it was just an evolution of the original chip in the first Pi, right?

01:16:27.540 --> 01:16:33.960
<v Chris Gammell>Just take out the, the, the weedier arm cores, add some more in and then kind of cut and shut, uh, make a new chip.

01:16:34.500 --> 01:16:40.640
<v Chris Gammell>And Pi four, the new device on that, the 2711 is, is a whole new design on 28 nanometers.

01:16:40.820 --> 01:16:42.440
<v Chris Gammell>So the old Pi chips were on 40 nanometers.

01:16:42.980 --> 01:16:48.300
<v Chris Gammell>So that was a, a bigger engineering effort, but it's kind of, you know, more of the same and we've got more scale.

01:16:48.300 --> 01:16:49.900
<v Chris Gammell>So we're a serious customer for Broadcom.

01:16:50.060 --> 01:16:54.320
<v Chris Gammell>So, you know, we can, we can work with them to, to, uh, to do this kind of stuff.

01:16:54.620 --> 01:16:55.980
<v Chris Gammell>I hope that, I hope that makes sense.

01:16:57.100 --> 01:17:00.680
<v Raspberry Pi>Yeah, no, that's, that's, I mean, that kind of is always what it felt like.

01:17:00.680 --> 01:17:04.280
<v Raspberry Pi>It was like a, not quite a retrofit, but it was a using what you get for initially.

01:17:04.280 --> 01:17:10.780
<v Raspberry Pi>And now that's interesting to hear that you're a big enough customer that like you get to subtly push, maybe push the giant around a little bit.

01:17:10.820 --> 01:17:12.180
<v Raspberry Pi>You know, that's, that's, that's interesting.

01:17:12.180 --> 01:17:16.920
<v Raspberry Pi>I assume for them, it's a huge marketing boon to have you guys on board.

01:17:17.100 --> 01:17:18.400
<v Raspberry Pi>So with using those chips, so.

01:17:18.960 --> 01:17:20.740
<v Chris Gammell>Yeah, there's that.

01:17:20.820 --> 01:17:23.260
<v Chris Gammell>And there's also the fact that, you know, we know how many Raspberry Pis we sell.

01:17:23.320 --> 01:17:27.180
<v Chris Gammell>It's quite easy to go and say, well, hey, you know, we're going to sell this many products.

01:17:27.720 --> 01:17:31.040
<v Chris Gammell>So they can do their kind of return on investment type calculations fairly easy.

01:17:31.440 --> 01:17:32.220
<v Chris Gammell>Yeah, exactly.

01:17:32.480 --> 01:17:32.660
<v Chris Gammell>Yeah.

01:17:33.080 --> 01:17:35.200
<v Chris Gammell>And usually what they're doing is an evolution of what's already there.

01:17:35.320 --> 01:17:38.900
<v Chris Gammell>So it's kind of a, sort of a, quite a low risk project for them, if you like.

01:17:38.900 --> 01:17:40.680
<v Chris Gammell>So it sort of makes, it wins for everybody, right?

01:17:41.900 --> 01:17:42.300
<v Raspberry Pi>Yeah.

01:17:42.540 --> 01:17:42.720
<v Raspberry Pi>Yeah.

01:17:42.720 --> 01:17:50.060
<v Raspberry Pi>I didn't figure it was, you know, bleeding edge, but I'm sure it's more leading edge, you know, like that kind of thing of like for the newer chips.

01:17:50.060 --> 01:17:56.680
<v Raspberry Pi>I know that the, the original chip was like, what, like for the 28 to fit 35 was like a set top box.

01:17:56.680 --> 01:17:58.360
<v Raspberry Pi>Is that what the original target market for that was?

01:17:59.060 --> 01:18:01.080
<v Raspberry Pi>Or more broadly than that?

01:18:01.980 --> 01:18:02.140
<v Raspberry Pi>Yeah.

01:18:02.200 --> 01:18:03.420
<v Raspberry Pi>Kind of broadly, broadly.

01:18:04.700 --> 01:18:06.100
<v Raspberry Pi>Video processing in general.

01:18:06.460 --> 01:18:07.340
<v Chris Gammell>It was originally.

01:18:07.340 --> 01:18:07.780
<v Chris Gammell>Yeah.

01:18:07.780 --> 01:18:07.780
<v Speaker ?>

01:18:07.780 --> 01:18:12.340
<v Chris Gammell>I was originally designed to be a, a coprocessor.

01:18:12.700 --> 01:18:13.820
<v Chris Gammell>So to drop in alongside.

01:18:13.820 --> 01:18:19.340
<v Chris Gammell>So when phones didn't really have a lot of multimedia drop in alongside the, the main SOC and do the acceleration.

01:18:20.660 --> 01:18:21.240
<v Chris Gammell>Got it.

01:18:21.920 --> 01:18:26.580
<v Chris Gammell>It ended up having an alarm core grafted onto the side of it kind of for engineering fun.

01:18:26.740 --> 01:18:28.840
<v Chris Gammell>And then it became useful for other things, right?

01:18:28.900 --> 01:18:31.280
<v Chris Gammell>It's kind of like a little system on a chip that could run Linux.

01:18:31.280 --> 01:18:32.380
<v Chris Gammell>And then, then, Hey, wow.

01:18:32.420 --> 01:18:33.720
<v Chris Gammell>It's, it's great for Raspberry Pi.

01:18:33.720 --> 01:18:42.660
<v Chris Gammell>So that, you know, there's just a sort of nice sequence of, of, of events that ended up making it really useful because it designed to be cheap as well.

01:18:42.660 --> 01:18:42.840
<v Chris Gammell>Right.

01:18:42.840 --> 01:18:48.060
<v Chris Gammell>Because mobile phone guys don't want to pay a lot of money for their, for their silicon.

01:18:48.060 --> 01:18:51.160
<v Chris Gammell>And so it kind of was all just the right thing at the right time.

01:18:53.020 --> 01:18:53.380
<v Raspberry Pi>Yep.

01:18:53.460 --> 01:18:53.720
<v Raspberry Pi>Okay.

01:18:53.840 --> 01:18:54.340
<v Raspberry Pi>That's great.

01:18:54.480 --> 01:18:56.140
<v Raspberry Pi>I mean, that's, that's good history.

01:18:56.140 --> 01:19:02.500
<v Raspberry Pi>I think, you know, on the documentation side, someone was asking about the schematics.

01:19:02.500 --> 01:19:06.440
<v Raspberry Pi>Uh, so the first Pi had a schematics, Pi 4 does not.

01:19:06.500 --> 01:19:08.360
<v Raspberry Pi>I, I've not looked close enough.

01:19:08.580 --> 01:19:09.280
<v Raspberry Pi>Is that correct?

01:19:09.280 --> 01:19:09.500
<v Raspberry Pi>That is correct.

01:19:09.680 --> 01:19:15.020
<v Chris Gammell>So we, uh, we, we do supply sort of reduced schematics for the, for the Pi boards these days.

01:19:15.520 --> 01:19:18.180
<v Chris Gammell>It's really just about the kind of IP protection.

01:19:18.440 --> 01:19:22.820
<v Chris Gammell>Uh, unfortunately we do, we know we spend a lot of money developing these products.

01:19:22.820 --> 01:19:33.660
<v Chris Gammell>We like to share as much as we possibly can with people on all of the products, but there's certain things that we, we like to keep to ourselves and maybe one day we can change that.

01:19:34.160 --> 01:19:40.000
<v Raspberry Pi>But it's just, you know, when you guys make a full custom, uh, you know, all the way down to the silicon, then you, then you get to do that.

01:19:40.000 --> 01:19:40.160
<v Raspberry Pi>Right.

01:19:40.180 --> 01:19:42.900
<v Raspberry Pi>I mean, like, uh, but yeah, maybe.

01:19:42.900 --> 01:19:43.260
<v Raspberry Pi>Yeah.

01:19:43.420 --> 01:19:45.320
<v Chris Gammell>I, I mean, it is what it is right now.

01:19:45.940 --> 01:19:52.800
<v Chris Gammell>You know, uh, I like to tell people that, you know, the fact that we've built this business and it's successful and it does make some money means we can employ bright engineers.

01:19:52.820 --> 01:19:55.220
<v Chris Gammell>Like Luke and Liam and we can do awesome stuff.

01:19:55.220 --> 01:19:55.420
<v Chris Gammell>Right.

01:19:55.440 --> 01:19:56.960
<v Chris Gammell>So we've got to kind of protect that.

01:19:57.020 --> 01:19:57.220
<v Raspberry Pi>Yeah.

01:19:57.420 --> 01:19:57.660
<v Chris Gammell>Right.

01:19:58.000 --> 01:20:04.300
<v Chris Gammell>So we, we, you know, we want to make things as open as we can, but there's some things that we feel, you know, is, is, could be risky to open.

01:20:04.300 --> 01:20:07.080
<v Chris Gammell>So we, you know, just being pragmatic as a business.

01:20:07.540 --> 01:20:07.900
<v Raspberry Pi>Yeah.

01:20:07.900 --> 01:20:15.020
<v Raspberry Pi>I mean, you guys sound like great engineers and I think that the, the focus on trade off, you know, we've said trade offs a couple of times on this episode.

01:20:15.020 --> 01:20:22.500
<v Raspberry Pi>And I just feel like that's, that is the basis of engineering and, you know, all decisions that we've discussed, it just feels like, yeah, there's trade offs.

01:20:22.500 --> 01:20:25.380
<v Raspberry Pi>And, you know, you're making the best way forward you can.

01:20:25.560 --> 01:20:27.600
<v Raspberry Pi>And so that's, that's fine with me.

01:20:27.960 --> 01:20:28.840
<v Raspberry Pi>I'm cool with it, guys.

01:20:29.560 --> 01:20:33.920
<v Raspberry Pi>I don't know if that matters at all, you know, globally, but, uh, trade offs are what they are.

01:20:34.180 --> 01:20:34.300
<v Speaker ?>Yeah.

01:20:34.300 --> 01:20:36.200
<v Chris Gammell>I mean, I think that is engineering in a nutshell, right?

01:20:36.280 --> 01:20:38.060
<v Chris Gammell>Good engineering and good business.

01:20:38.420 --> 01:20:38.740
<v Chris Gammell>Right.

01:20:38.740 --> 01:20:39.140
<v Chris Gammell>Yeah.

01:20:40.580 --> 01:20:40.820
<v Chris Gammell>Right.

01:20:40.920 --> 01:20:41.240
<v Chris Gammell>Exactly.

01:20:41.440 --> 01:20:41.700
<v Chris Gammell>Exactly.

01:20:42.960 --> 01:20:43.320
<v Raspberry Pi>Okay.

01:20:43.420 --> 01:20:48.420
<v Raspberry Pi>Well, anything else I should know or our audience should know, I mean, uh, how they can help maybe.

01:20:48.420 --> 01:20:50.240
<v Raspberry Pi>And are you guys looking for that sort of thing?

01:20:50.320 --> 01:20:53.160
<v Raspberry Pi>More demos, more help, more on the software SDK side of things.

01:20:53.280 --> 01:20:53.740
<v Raspberry Pi>Are you hiring?

01:20:54.260 --> 01:20:56.000
<v Raspberry Pi>What, what, what are we thinking on that side of things?

01:20:56.300 --> 01:21:01.640
<v Chris Gammell>Do we have anything on the sort of software side with, uh, with Pico or RP2040, Luke or Liam?

01:21:02.360 --> 01:21:04.480
<v Luke Renn>We accept pull requests to the SDK.

01:21:04.860 --> 01:21:05.080
<v Luke Renn>Okay.

01:21:05.340 --> 01:21:08.580
<v Luke Renn>Lots of people are working on, uh, things like Rust support at the moment.

01:21:09.100 --> 01:21:12.020
<v Luke Renn>There's some really interesting stuff going on, particularly in the Rust community.

01:21:12.020 --> 01:21:16.500
<v Luke Renn>I mean, they were able to get to, to Blinky based on our documentation within a couple of days.

01:21:17.020 --> 01:21:22.880
<v Luke Renn>Uh, we don't have any internal bandwidth to help out with the, the Rust support other than, uh, helping out with support questions.

01:21:22.880 --> 01:21:28.480
<v Luke Renn>So if you are an expert in Rust or you, you enjoy Rust, then definitely go jump on that project and help those guys out.

01:21:28.880 --> 01:21:31.480
<v Luke Renn>I think Rust will be really, really interesting in this system.

01:21:31.640 --> 01:21:33.480
<v Chris Gammell>And anything to say on RTOS?

01:21:34.200 --> 01:21:35.580
<v Luke Renn>We're looking at a free RTOS port.

01:21:35.920 --> 01:21:39.880
<v Luke Renn>We will publish more details when we have something to actually put on GitHub and have people hack on.

01:21:40.580 --> 01:21:41.360
<v Raspberry Pi>Okay, cool.

01:21:41.540 --> 01:21:41.980
<v Raspberry Pi>That's great.

01:21:42.900 --> 01:21:43.240
<v Raspberry Pi>Throw in.

01:21:43.600 --> 01:21:44.080
<v Raspberry Pi>I like Zephyr.

01:21:44.300 --> 01:21:44.940
<v Raspberry Pi>If you guys like Zephyr.

01:21:45.220 --> 01:21:46.120
<v Raspberry Pi>I'm also a fan of Zephyr.

01:21:46.280 --> 01:21:46.500
<v Raspberry Pi>Go for that.

01:21:47.560 --> 01:21:47.920
<v Raspberry Pi>Yeah.

01:21:48.080 --> 01:21:48.260
<v Raspberry Pi>Yeah.

01:21:48.640 --> 01:21:49.000
<v Raspberry Pi>Cool.

01:21:49.200 --> 01:21:49.560
<v Raspberry Pi>All right.

01:21:49.580 --> 01:21:50.020
<v Raspberry Pi>That's great.

01:21:50.080 --> 01:21:50.440
<v Raspberry Pi>That's great.

01:21:50.440 --> 01:21:50.600
<v Raspberry Pi>Yeah.

01:21:50.920 --> 01:21:55.520
<v Raspberry Pi>So where can people find out more about you guys individually, where they can find, follow you online?

01:21:55.520 --> 01:21:58.020
<v Raspberry Pi>And then, uh, where can they find out more about the boards?

01:21:58.140 --> 01:22:01.060
<v Raspberry Pi>And I guess probably just we'll say Googling on, on that side of things.

01:22:01.060 --> 01:22:03.860
<v Raspberry Pi>But if there's anything special they should see, where should they go to look?

01:22:04.420 --> 01:22:07.620
<v Luke Renn>I mean, you can find me on Twitter at Ren6991.

01:22:07.800 --> 01:22:09.780
<v Luke Renn>Most of that is posting about my own projects.

01:22:09.900 --> 01:22:16.080
<v Luke Renn>I've got a little hobby project in the background the last couple of years where I've been trying to build a competitor to the Game Boy Advance from scratch.

01:22:16.540 --> 01:22:17.500
<v Luke Renn>About 20 years too late.

01:22:17.660 --> 01:22:17.980
<v Luke Renn>Nice.

01:22:17.980 --> 01:22:18.880
<v Luke Renn>It's called Wisk Boy.

01:22:19.060 --> 01:22:19.840
<v Luke Renn>So check that out.

01:22:21.180 --> 01:22:21.400
<v Liam Fraser>Cool.

01:22:21.720 --> 01:22:21.880
<v Chris Gammell>Yeah.

01:22:21.900 --> 01:22:22.420
<v Chris Gammell>I'm on Twitter.

01:22:22.720 --> 01:22:27.780
<v Chris Gammell>If you could follow me, if you like, I tweet about random things, uh, often just my own stuff as well.

01:22:27.780 --> 01:22:29.040
<v Chris Gammell>At James Adams 314.

01:22:29.860 --> 01:22:30.220
<v Liam Fraser>Yeah.

01:22:30.260 --> 01:22:34.340
<v Liam Fraser>And I'm on Twitter as Fraser Liam, and I'm also on GitHub as Liam Fraser.

01:22:35.020 --> 01:22:35.320
<v Raspberry Pi>Okay.

01:22:35.360 --> 01:22:35.900
<v Raspberry Pi>That's great.

01:22:36.040 --> 01:22:36.240
<v Raspberry Pi>Yeah.

01:22:36.240 --> 01:22:37.420
<v Raspberry Pi>All right.

01:22:37.460 --> 01:22:38.100
<v Raspberry Pi>Well, thanks guys.

01:22:38.180 --> 01:22:41.720
<v Raspberry Pi>We'll have links and all the, we'll have links about everything we've talked about here in the show notes.

01:22:41.900 --> 01:22:46.460
<v Raspberry Pi>And, uh, people can always ask, uh, questions in the comment section on Twitter as well.

01:22:46.540 --> 01:22:47.400
<v Raspberry Pi>You can ask questions.

01:22:47.400 --> 01:22:51.240
<v Raspberry Pi>Uh, we'll tag everybody on Twitter so that you can find everyone nice and easy.

01:22:51.620 --> 01:22:53.180
<v Raspberry Pi>Thank you so much for joining me here.

01:22:53.180 --> 01:22:55.360
<v Raspberry Pi>I, uh, and thanks for developing these products.

01:22:55.360 --> 01:23:06.500
<v Raspberry Pi>I think it's going to be, it's really exciting to see what you guys are doing and what the future is for the education side, but then, you know, more broadly in terms of custom silicon, you know, where Raspberry Pi is going.

01:23:07.240 --> 01:23:07.780
<v Raspberry Pi>It's been a pleasure.

01:23:08.520 --> 01:23:09.060
<v Liam Fraser>Thank you.

01:23:09.460 --> 01:23:09.680
<v Luke Renn>Yeah.

01:23:09.680 --> 01:23:10.320
<v Luke Renn>Thanks for having us on.

01:23:10.780 --> 01:23:11.080
<v Raspberry Pi>All right.

01:23:11.180 --> 01:23:11.760
<v Raspberry Pi>Talk to you guys soon.

01:23:12.100 --> 01:23:12.300
<v Raspberry Pi>Bye.

01:23:12.540 --> 01:23:12.900
<v Luke Renn>Thanks.

01:23:14.420 --> 01:23:18.440
<v Raspberry Pi>As you grab another slice of Raspberry Pi, we'd like to thank the naturally sweet nature of our patrons.

01:23:18.780 --> 01:23:22.180
<v Raspberry Pi>They're in the kitchen and in the Discord channel, cooking up the next bit of technology conversation.

01:23:22.520 --> 01:23:24.820
<v Raspberry Pi>Join the chip chat at patreon.com slash the amp hour.

01:23:24.820 --> 01:23:28.500
<v Raspberry Pi>Come talk through your next embedded or Linux based system and join the club of amp hour listeners.
