WEBVTT

00:00:00.000 --> 00:00:01.600
<v Chris Gammell>This is The Amp Hour Podcast.

00:00:03.020 --> 00:00:05.860
<v Chris Gammell>Released October 2nd, 2025.

00:00:08.080 --> 00:00:09.640
<v Chris Gammell>Episode 704.

00:00:11.120 --> 00:00:13.840
<v Chris Gammell>Applied Embedded Electronics with Jerry Toomey.

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

00:00:33.900 --> 00:00:36.300
<v Chris Gammell>Hi, and I'm Jerry Toomey from Effective Electrons.

00:00:36.680 --> 00:00:37.720
<v Chris Gammell>Welcome, Jerry. How are you doing?

00:00:37.900 --> 00:00:39.280
<v Chris Gammell>Doing well today. Doing well.

00:00:39.580 --> 00:00:43.540
<v Chris Gammell>Great. Well, I first heard you on the Embedded Podcast a little bit more than a year ago.

00:00:43.580 --> 00:00:44.460
<v Chris Gammell>I think it was June of 2024.

00:00:44.980 --> 00:00:48.860
<v Chris Gammell>And I immediately thought, man, I wish we would have gotten him on the Amp Hour first.

00:00:48.980 --> 00:00:50.780
<v Chris Gammell>But I enjoyed the heck out of that interview.

00:00:50.920 --> 00:00:52.880
<v Chris Gammell>So nice job on there. And we're going to extend on that today.

00:00:53.340 --> 00:00:56.260
<v Dave Jones>Thanks. What kind of questions can I answer for you today?

00:00:56.740 --> 00:00:58.300
<v Chris Gammell>How do I make better products, Jerry?

00:00:58.300 --> 00:01:00.240
<v Chris Gammell>I think that's the thing.

00:01:00.380 --> 00:01:03.040
<v Chris Gammell>Like your book, Applied Embedded Electronics.

00:01:03.480 --> 00:01:06.060
<v Chris Gammell>And, you know, it's about making better embedded electronics.

00:01:06.600 --> 00:01:07.140
<v Chris Gammell>How do I do that?

00:01:07.200 --> 00:01:10.400
<v Chris Gammell>How do I move things forward so that I don't have random field failures?

00:01:10.540 --> 00:01:11.760
<v Chris Gammell>How do I improve as an engineer?

00:01:11.920 --> 00:01:16.360
<v Chris Gammell>You know, I'm kind of at that point in my career where I'm capable, but I'm, you know, I'm not perfect.

00:01:17.160 --> 00:01:19.700
<v Dave Jones>Well, I don't know if we can ever achieve perfect,

00:01:19.840 --> 00:01:24.300
<v Dave Jones>especially in the fast-moving field of electronics and the methods changing all the time.

00:01:24.540 --> 00:01:25.820
<v Dave Jones>How long have you been in the business, Chris?

00:01:26.320 --> 00:01:28.060
<v Chris Gammell>21 years, depending on how you count it.

00:01:28.060 --> 00:01:31.440
<v Chris Gammell>2006 was really my first non-co-op job.

00:01:31.560 --> 00:01:34.980
<v Chris Gammell>So maybe pushing 20 years is probably a better way to say it, but yeah.

00:01:35.300 --> 00:01:38.660
<v Dave Jones>Okay. I'm feeling a little bit old because I've been doing this for over 40 now.

00:01:38.840 --> 00:01:39.900
<v Chris Gammell>I'm chasing you, but yeah.

00:01:40.220 --> 00:01:44.840
<v Chris Gammell>And I do kind of wonder as well, like from 20 to 40, you know, how do things migrate?

00:01:44.940 --> 00:01:47.100
<v Chris Gammell>How do you keep filling out the chapters in a book like this, I suppose?

00:01:47.360 --> 00:01:50.100
<v Dave Jones>It's an ongoing process with the methods changing,

00:01:50.100 --> 00:01:56.560
<v Dave Jones>but there's a number of things that covered in the books that are pretty time static that don't change.

00:01:56.560 --> 00:01:59.460
<v Dave Jones>And one of the things that when I was developing this book, I said,

00:01:59.520 --> 00:02:04.500
<v Dave Jones>I did not want to do something that was going to be outdated in six months.

00:02:04.620 --> 00:02:10.880
<v Dave Jones>You know, here's an applications manual for a ST microelectronics microcontroller and how to use it,

00:02:10.880 --> 00:02:15.720
<v Dave Jones>because that's going to be something that's historically significant within a year or two.

00:02:15.720 --> 00:02:19.240
<v Dave Jones>I was dealing more with how to do robust systems.

00:02:19.660 --> 00:02:26.640
<v Dave Jones>And a lot of what's in the book is motivated by a problem solving I was involved with for many,

00:02:26.740 --> 00:02:30.100
<v Dave Jones>many clients where they'd come to me with a project that had been developed

00:02:30.100 --> 00:02:35.680
<v Dave Jones>and they either hit problems with performance or noise or regulatory testing

00:02:35.680 --> 00:02:39.660
<v Dave Jones>or something that just had them stymied.

00:02:39.740 --> 00:02:40.840
<v Dave Jones>I'd get dragged into it.

00:02:40.840 --> 00:02:47.380
<v Dave Jones>Usually ended up fixing a multitude of things that became the motivation for first large number of articles

00:02:47.380 --> 00:02:48.880
<v Dave Jones>in electronic design magazine.

00:02:49.160 --> 00:02:57.320
<v Dave Jones>I've written 30 odd articles for them and for EDN and a few other places as well on various technical topics.

00:02:57.720 --> 00:03:01.580
<v Dave Jones>It was basically a situation of saying, okay, these are the things people have problems with.

00:03:01.740 --> 00:03:05.580
<v Dave Jones>So the name of the game is let's put something together in an organized manner

00:03:05.580 --> 00:03:08.680
<v Dave Jones>that'll take me out of business fixing other people's problems.

00:03:08.820 --> 00:03:10.600
<v Dave Jones>I can say, read the book, read the book.

00:03:10.840 --> 00:03:12.980
<v Chris Gammell>You've been consulting for a long time, I suppose.

00:03:13.200 --> 00:03:15.040
<v Chris Gammell>So what were the kind of the subject areas?

00:03:15.120 --> 00:03:17.280
<v Chris Gammell>You mentioned EMI style things.

00:03:17.700 --> 00:03:20.140
<v Chris Gammell>I saw you're in San Diego where there's a lot of RF stuff.

00:03:20.380 --> 00:03:23.320
<v Chris Gammell>What were the industries and verticals you were often working in?

00:03:23.560 --> 00:03:24.800
<v Dave Jones>The list is long.

00:03:25.240 --> 00:03:26.220
<v Dave Jones>A little bit of a quick history.

00:03:26.420 --> 00:03:29.220
<v Dave Jones>I did college and grad school in Massachusetts.

00:03:30.040 --> 00:03:34.080
<v Dave Jones>I worked in the electronics industry around the Boston area for a while.

00:03:34.340 --> 00:03:39.600
<v Dave Jones>Got recruited to go out to San Jose, Silicon Valley and spent about 10 years there.

00:03:39.600 --> 00:03:44.740
<v Dave Jones>And then I ended up going down into San Diego where the weather's nicer and there's people

00:03:44.740 --> 00:03:47.300
<v Dave Jones>with lives and things other than work.

00:03:47.680 --> 00:03:49.560
<v Dave Jones>Silicon Valley can be a little bit work and fast.

00:03:49.940 --> 00:03:51.620
<v Chris Gammell>Much better tacos and stuff too, I think, right?

00:03:52.020 --> 00:03:53.100
<v Chris Gammell>Yeah, for sure.

00:03:53.240 --> 00:03:53.420
<v Chris Gammell>Yeah.

00:03:53.560 --> 00:03:53.960
<v Chris Gammell>For sure.

00:03:54.340 --> 00:03:59.780
<v Chris Gammell>I think San Diego, I think the military electronics, I think about Qualcomm's down there.

00:03:59.880 --> 00:04:00.680
<v Chris Gammell>There's a bunch of RF stuff.

00:04:00.780 --> 00:04:04.280
<v Chris Gammell>One of our longtime guests of the show was a RF designer out there.

00:04:04.280 --> 00:04:08.200
<v Chris Gammell>I often kind of think military RF, high-end chip stuff.

00:04:08.860 --> 00:04:11.960
<v Dave Jones>Yeah, there's a lot of that down here for sure.

00:04:12.500 --> 00:04:14.620
<v Dave Jones>There's also a lot of life science stuff.

00:04:15.040 --> 00:04:19.600
<v Dave Jones>I've also migrated in the past 10 years or so to doing a lot of medical electronics.

00:04:20.120 --> 00:04:25.500
<v Dave Jones>Before that, I've had times when I've done consumer stuff, aerospace stuff, defense projects.

00:04:25.500 --> 00:04:27.900
<v Dave Jones>I've done DARPA research things.

00:04:28.840 --> 00:04:30.260
<v Dave Jones>And the list kind of goes on.

00:04:30.400 --> 00:04:35.340
<v Dave Jones>And I'm a little bit of an anomaly because I consider myself a DC to daylight kind of analog

00:04:35.340 --> 00:04:35.960
<v Dave Jones>person.

00:04:36.380 --> 00:04:39.780
<v Dave Jones>But a lot of what I've ended up doing has been for the digital world.

00:04:40.100 --> 00:04:41.960
<v Dave Jones>Very high-speed data systems.

00:04:42.360 --> 00:04:44.400
<v Dave Jones>They're basically a communications channel problem.

00:04:44.620 --> 00:04:46.120
<v Dave Jones>They're not really a digital problem.

00:04:46.420 --> 00:04:51.140
<v Dave Jones>A lot of things with robust design, you ask the question about, you know, how do you become

00:04:51.140 --> 00:04:51.820
<v Dave Jones>a better designer?

00:04:51.820 --> 00:04:56.040
<v Dave Jones>One of the things I did with the book is I broke it down into a bunch of topics that people

00:04:56.040 --> 00:05:01.620
<v Dave Jones>frequently have problems with and covered each of those in depth as much as I could.

00:05:01.740 --> 00:05:06.200
<v Dave Jones>I mean, the book's 600 pages, so consequently, there's a lot there.

00:05:06.700 --> 00:05:10.720
<v Dave Jones>It was a situation where one of the first things I had to do was teach people about the fact that

00:05:10.720 --> 00:05:17.920
<v Dave Jones>what they learned at university about the nature of signals and systems is frequently not the

00:05:17.920 --> 00:05:19.480
<v Dave Jones>real world things.

00:05:19.480 --> 00:05:23.640
<v Dave Jones>Academic stuff teaches you about ideal digital systems, for sure.

00:05:23.880 --> 00:05:28.560
<v Dave Jones>They're going to teach you about ideal signal systems, but they're not going to go into things

00:05:28.560 --> 00:05:35.060
<v Dave Jones>like noise, immunity, and second-order problems with things like inductance and cross-coupling

00:05:35.060 --> 00:05:38.600
<v Dave Jones>and a multitude of other things as well.

00:05:39.320 --> 00:05:39.460
<v Chris Gammell>Got it.

00:05:39.520 --> 00:05:42.500
<v Chris Gammell>So they call you up and they say, Jerry, Jerry, look at this logic analyzer.

00:05:42.580 --> 00:05:43.760
<v Chris Gammell>It's got all this garbage on here.

00:05:43.880 --> 00:05:45.120
<v Chris Gammell>And then you pull out the scope.

00:05:45.220 --> 00:05:46.120
<v Chris Gammell>You pull out the eye diagram.

00:05:46.320 --> 00:05:47.720
<v Chris Gammell>You pull out the VNA, that sort of thing.

00:05:47.720 --> 00:05:50.200
<v Dave Jones>That's basically been part of it many times.

00:05:50.360 --> 00:05:52.340
<v Dave Jones>I'll give you a very typical example.

00:05:52.860 --> 00:05:59.780
<v Dave Jones>Medical devices, company can remain nameless, but I got called in on a project and it was

00:05:59.780 --> 00:06:03.200
<v Dave Jones>a situation where they had gone in for regulatory testing.

00:06:03.560 --> 00:06:07.180
<v Dave Jones>The regulatory testing associated with medical devices is pretty strenuous.

00:06:07.380 --> 00:06:13.560
<v Dave Jones>You've got applied EMI issues, applied ESD issues, magnetic field issues, and things like

00:06:13.560 --> 00:06:18.520
<v Dave Jones>that where the system has to keep working throughout all of that stuff.

00:06:18.700 --> 00:06:25.340
<v Dave Jones>And you can't have the blue screen of death on ESD pulse because it's a medical device and

00:06:25.340 --> 00:06:29.500
<v Dave Jones>that's not going to be well-received in the operating room, to say the least.

00:06:29.860 --> 00:06:32.420
<v Dave Jones>So it's a little bit more strenuous in the testing.

00:06:32.620 --> 00:06:37.620
<v Dave Jones>It's kind of like an aerospace way of thinking about it where reliability is first and foremost

00:06:37.620 --> 00:06:40.740
<v Dave Jones>cost is much less of an issue.

00:06:40.740 --> 00:06:47.540
<v Dave Jones>But getting back to the topic at hand, this particular client, medical device, and they

00:06:47.540 --> 00:06:51.780
<v Dave Jones>went into regulatory testing and they found all kinds of problems.

00:06:52.040 --> 00:06:58.680
<v Dave Jones>The guy that was in charge of the project was much more of a digital person and very little

00:06:58.680 --> 00:07:01.940
<v Dave Jones>experience on the analog or the signal integrity side of things.

00:07:01.940 --> 00:07:10.540
<v Dave Jones>I found things like no ESD protection and no running cables off of boards where there was

00:07:10.540 --> 00:07:13.500
<v Dave Jones>data streams, where there was no error correction.

00:07:13.920 --> 00:07:16.000
<v Dave Jones>There was no detection of errors.

00:07:16.220 --> 00:07:19.140
<v Dave Jones>There was no common mode rejection of noise.

00:07:19.260 --> 00:07:25.240
<v Dave Jones>It was ground reference signal going off of a board, which is a suicide jump when you're

00:07:25.240 --> 00:07:27.540
<v Dave Jones>trying to have something work in a hostile environment.

00:07:27.780 --> 00:07:31.860
<v Dave Jones>Early on in the book, the first one of the early things I do is I talk about

00:07:31.860 --> 00:07:37.420
<v Dave Jones>situations with the fact that a lot of what you get in academia is ideal.

00:07:38.520 --> 00:07:44.240
<v Dave Jones>Ideal signals, ideal data streams, and no noise, no corruption of signals, things like

00:07:44.240 --> 00:07:44.480
<v Dave Jones>that.

00:07:44.540 --> 00:07:47.800
<v Dave Jones>You might see a little bit of that in grad school, but that's kind of about it.

00:07:47.980 --> 00:07:48.920
<v Dave Jones>I go into that.

00:07:49.120 --> 00:07:57.400
<v Dave Jones>I go into basic components, and certain components are non-ideal relative to capacitor variances.

00:07:57.660 --> 00:08:00.540
<v Dave Jones>Everybody treats capacitors until they get some experience.

00:08:00.540 --> 00:08:03.660
<v Dave Jones>They treat them as, oh, I put down a 0.1 microfarad capacitor.

00:08:04.280 --> 00:08:09.000
<v Dave Jones>The reality is something very different depending upon what the actual capacitor is.

00:08:09.060 --> 00:08:10.240
<v Dave Jones>That's very simple stuff.

00:08:10.480 --> 00:08:10.860
<v Dave Jones>Right, right.

00:08:10.940 --> 00:08:13.320
<v Dave Jones>But a lot of it never gets covered in academia.

00:08:14.100 --> 00:08:16.560
<v Chris Gammell>What were the levels of engineers you were working with as well?

00:08:16.620 --> 00:08:20.220
<v Chris Gammell>I mean, I guess it's going to depend company to company, but when are you getting called

00:08:20.220 --> 00:08:21.940
<v Chris Gammell>for these kind of engagements as well?

00:08:21.940 --> 00:08:26.000
<v Dave Jones>I've gotten it from people at all levels.

00:08:26.220 --> 00:08:33.300
<v Dave Jones>Case in point, a few years back, I was developing high-speed data for IBM mainframes, and that

00:08:33.300 --> 00:08:40.540
<v Dave Jones>got done because of the fact I had done something similar a year before that was with Cray, again,

00:08:40.680 --> 00:08:44.060
<v Dave Jones>doing high-speed data over copper within the computer systems.

00:08:44.060 --> 00:08:46.840
<v Dave Jones>And IBM wanted a similar system.

00:08:46.940 --> 00:08:52.660
<v Dave Jones>So I ended up doing high-speed data for groups of people that were extremely experienced when

00:08:52.660 --> 00:08:54.780
<v Dave Jones>it came to developing computer systems.

00:08:55.440 --> 00:09:02.100
<v Dave Jones>But this niche area of high-speed data signal processing was a little bit outside their forte.

00:09:02.100 --> 00:09:05.680
<v Chris Gammell>Yeah, those names are not around much anymore, Jerry.

00:09:05.820 --> 00:09:06.900
<v Chris Gammell>In the same context, at least.

00:09:06.980 --> 00:09:09.880
<v Chris Gammell>Now it's like IBM's like, I'd like to sell you some SaaS software solutions.

00:09:10.640 --> 00:09:16.900
<v Dave Jones>Ah, but IBM still does mainframes, and Cray is still out there doing NSA computers.

00:09:17.360 --> 00:09:18.060
<v Dave Jones>No way.

00:09:18.300 --> 00:09:19.540
<v Dave Jones>Okay, I learned today.

00:09:19.600 --> 00:09:20.420
<v Dave Jones>I had no idea.

00:09:20.720 --> 00:09:25.180
<v Dave Jones>Cray still does massive multiprocessor systems, whatever the acronym is for that.

00:09:25.620 --> 00:09:27.340
<v Dave Jones>Lots of parallel computing processing.

00:09:27.340 --> 00:09:31.460
<v Dave Jones>Those projects were over 10 years ago, but I think they serve as a good example where

00:09:31.460 --> 00:09:35.760
<v Dave Jones>you're going to get extremely experienced people that are lacking knowledge in a particular area.

00:09:36.740 --> 00:09:36.760
<v Chris Gammell>Right.

00:09:36.940 --> 00:09:41.700
<v Chris Gammell>And I can imagine, too, as systems scale, like you said, the interconnect, the things that are,

00:09:42.100 --> 00:09:45.320
<v Chris Gammell>you're going to get at the edges, you're going to have problems at the edges, versus

00:09:45.320 --> 00:09:51.440
<v Chris Gammell>someone who's like a complex VLSI, like silicon designer, and thinking about like,

00:09:51.820 --> 00:09:54.340
<v Chris Gammell>they're not thinking about the wire, they're thinking about the silicon, that sort of thing.

00:09:54.340 --> 00:09:59.040
<v Chris Gammell>So like having that cross-knowledge capabilities do seem like you need to kind of bring a bunch

00:09:59.040 --> 00:09:59.680
<v Chris Gammell>of skills in there.

00:10:00.240 --> 00:10:04.000
<v Dave Jones>Yeah, it becomes more of a communications channel problem at that point, because of the fact

00:10:04.000 --> 00:10:08.520
<v Dave Jones>that you're trying to put data across wires, where it's not ones and zeros going across

00:10:08.520 --> 00:10:11.640
<v Dave Jones>the wires, it's actually multiple standing wave transitions.

00:10:12.040 --> 00:10:18.240
<v Dave Jones>So you have multiple bits on the same wire at the same time, just doing its transmission

00:10:18.240 --> 00:10:20.000
<v Dave Jones>line going across the wire.

00:10:20.000 --> 00:10:26.120
<v Dave Jones>So you start to get down to your bits underneath a tenth of a nanosecond and worse, and you

00:10:26.120 --> 00:10:29.200
<v Dave Jones>basically start running into all kinds of interesting analog problems.

00:10:29.600 --> 00:10:31.740
<v Dave Jones>But, you know, that's just one particular area.

00:10:32.460 --> 00:10:37.340
<v Chris Gammell>That's actually probably way past the kind of the threshold of what I would actually be

00:10:37.340 --> 00:10:37.880
<v Chris Gammell>doing as well.

00:10:37.940 --> 00:10:41.820
<v Chris Gammell>So like when I think about, you know, improving my own skills, I mean, I guess there are nanosecond

00:10:41.820 --> 00:10:46.020
<v Chris Gammell>transitions, but they're, you know, they're clock edges that need to be straight, but it's

00:10:46.020 --> 00:10:49.080
<v Chris Gammell>not, it's not something that I'm like clocking quite that fast.

00:10:49.080 --> 00:10:55.180
<v Dave Jones>Well, it's an interesting thing that you mentioned that because of the fact that when you have

00:10:55.180 --> 00:10:59.500
<v Dave Jones>a data stream going across wires, what are the things that limit your performance?

00:11:00.320 --> 00:11:05.420
<v Dave Jones>And a lot of people will say data rate, but I think it comes down to two things.

00:11:06.060 --> 00:11:10.860
<v Dave Jones>And I go into this in the book quite a bit in the chapter on reliable data communication.

00:11:11.380 --> 00:11:15.380
<v Dave Jones>And that is rise and fall times and distance traveled.

00:11:15.380 --> 00:11:20.200
<v Dave Jones>If you have extremely fast rise fall times, you have a situation where you have a transmission

00:11:20.200 --> 00:11:21.080
<v Dave Jones>line problem.

00:11:21.420 --> 00:11:26.880
<v Dave Jones>Even when the distance traveled is, you know, under a centimeter, you need to understand those

00:11:26.880 --> 00:11:28.680
<v Dave Jones>two things and how they play off of each other.

00:11:29.100 --> 00:11:29.220
<v Chris Gammell>All right.

00:11:29.260 --> 00:11:34.720
<v Chris Gammell>Well, maybe we could do some example quasi design activities here, just as like, you know,

00:11:35.060 --> 00:11:35.820
<v Chris Gammell>gaming it out.

00:11:35.820 --> 00:11:39.000
<v Chris Gammell>Thinking about when I call Jerry, when I, when I read the book, that sort of thing, maybe

00:11:39.000 --> 00:11:39.780
<v Chris Gammell>we could talk through it.

00:11:40.020 --> 00:11:44.080
<v Chris Gammell>You have some stuff in there about choosing power supplies, about choosing microcontrollers,

00:11:44.160 --> 00:11:48.660
<v Chris Gammell>about defensive coding kind of really does cover the gamut of runs, the gamut rather of

00:11:48.660 --> 00:11:53.200
<v Chris Gammell>different thought processes you need to have different considerations needed to make.

00:11:53.200 --> 00:11:58.180
<v Chris Gammell>But if you were brought in at the right at the beginning of a project, let's talk about

00:11:58.180 --> 00:11:59.340
<v Chris Gammell>like a glucose monitor.

00:11:59.720 --> 00:12:05.580
<v Chris Gammell>That's a Bluetooth glucose monitor talking, you know, to a, to a gateway.

00:12:06.340 --> 00:12:11.480
<v Chris Gammell>Is there, are there any special considerations you start with in those kind of application

00:12:11.480 --> 00:12:15.660
<v Chris Gammell>spaces or, or is it more, or maybe that's too pedestrian even for a lot of these considerations?

00:12:16.120 --> 00:12:16.720
<v Chris Gammell>Well, it's funny.

00:12:16.800 --> 00:12:20.480
<v Dave Jones>You mentioned glucose monitors because I've done those for Dexcom.

00:12:20.880 --> 00:12:21.400
<v Dave Jones>Oh, okay.

00:12:21.500 --> 00:12:21.900
<v Dave Jones>Yeah.

00:12:21.920 --> 00:12:22.140
<v Dave Jones>Okay.

00:12:22.140 --> 00:12:22.580
<v Dave Jones>There we go.

00:12:22.580 --> 00:12:26.040
<v Dave Jones>I helped them get through three of their early generation products.

00:12:26.600 --> 00:12:32.280
<v Dave Jones>Two of their on-body monitor systems, and then a combined insulin pump and glucose monitor

00:12:32.280 --> 00:12:33.600
<v Dave Jones>for hospital use.

00:12:33.760 --> 00:12:34.040
<v Chris Gammell>All right.

00:12:34.060 --> 00:12:35.440
<v Chris Gammell>So we're right, right in the wheelhouse then.

00:12:35.480 --> 00:12:36.000
<v Chris Gammell>That sounds great.

00:12:36.080 --> 00:12:39.340
<v Chris Gammell>But I think medical devices these days, I think a lot of that stuff, it's kind of the

00:12:39.340 --> 00:12:39.920
<v Chris Gammell>time is right.

00:12:40.000 --> 00:12:41.540
<v Chris Gammell>There's a bunch of stuff around it.

00:12:41.780 --> 00:12:42.320
<v Dave Jones>Oh, for sure.

00:12:42.540 --> 00:12:45.660
<v Dave Jones>I helped develop a wearable EEG monitor as well.

00:12:45.740 --> 00:12:50.160
<v Dave Jones>A few years back, that was kind of a nice project that I enjoyed because of the fact that

00:12:50.160 --> 00:12:54.780
<v Dave Jones>before, if you were trying to monitor EEGs on a patient, you had to have them in the hospital

00:12:54.780 --> 00:12:57.180
<v Dave Jones>in a bed with, you know, all kinds of stuff wired up to them.

00:12:57.680 --> 00:13:02.280
<v Dave Jones>This became a manifestation that looked like a deck of cards kind of thing that you wore.

00:13:02.280 --> 00:13:09.640
<v Dave Jones>And it linked out, but it also recorded and kept the memory so that you could just hand it back in,

00:13:09.680 --> 00:13:10.680
<v Dave Jones>and it was all there.

00:13:10.780 --> 00:13:15.140
<v Dave Jones>So even if the RF data links were lost, you still had the whole EEG recording.

00:13:15.580 --> 00:13:17.900
<v Dave Jones>But I would start with something of that nature.

00:13:17.900 --> 00:13:23.140
<v Dave Jones>If it was a new project of architecting the system, architecting a system depends upon,

00:13:23.320 --> 00:13:24.740
<v Dave Jones>you know, what is it you're trying to do?

00:13:24.880 --> 00:13:25.940
<v Dave Jones>What's coming in?

00:13:25.940 --> 00:13:27.960
<v Dave Jones>What does the user need to see or do?

00:13:28.460 --> 00:13:31.840
<v Dave Jones>Defining your needs, defining your interfaces, and things of that nature.

00:13:32.660 --> 00:13:38.500
<v Dave Jones>And that can be simple from a standalone, bare metal, microcontroller kind of setup at the

00:13:38.500 --> 00:13:39.340
<v Dave Jones>heart of the whole thing.

00:13:39.380 --> 00:13:42.540
<v Dave Jones>Or it can be a multiprocessor distributed system.

00:13:42.760 --> 00:13:44.520
<v Dave Jones>Industrial systems use that a lot.

00:13:44.880 --> 00:13:46.280
<v Dave Jones>You can have two extremes there.

00:13:46.480 --> 00:13:51.760
<v Dave Jones>And then you have to scope out the system for what's needed in the way of communication

00:13:51.760 --> 00:13:52.760
<v Dave Jones>between devices.

00:13:53.140 --> 00:13:55.640
<v Dave Jones>What are the devices that are needed in the system?

00:13:56.480 --> 00:14:00.480
<v Dave Jones>And before you even go into the guts of things, you're looking at it as a black box.

00:14:01.000 --> 00:14:06.960
<v Dave Jones>What the application end user's person sees and figuring out from there going one level

00:14:06.960 --> 00:14:08.320
<v Dave Jones>down into the electronics.

00:14:08.620 --> 00:14:10.200
<v Dave Jones>That's typically a starting point.

00:14:10.700 --> 00:14:10.820
<v Chris Gammell>Got it.

00:14:10.840 --> 00:14:15.400
<v Chris Gammell>So if you're advising on like these kind of architecture level decisions, usually in medical

00:14:15.400 --> 00:14:17.360
<v Chris Gammell>space, it's not super cost constrained.

00:14:17.460 --> 00:14:18.620
<v Chris Gammell>So that's not driving a lot of it.

00:14:18.620 --> 00:14:24.760
<v Chris Gammell>But are there thoughts around, you know, just generic, like how often is it like jelly bean,

00:14:24.920 --> 00:14:29.640
<v Chris Gammell>like, you know, five volt to three, three buck converter type of things that you worry about

00:14:29.640 --> 00:14:34.520
<v Chris Gammell>versus the more kind of esoteric, weird parts that might be needed?

00:14:34.840 --> 00:14:36.540
<v Chris Gammell>Like how are you thinking about those sort of things?

00:14:36.540 --> 00:14:41.440
<v Dave Jones>Once you get a basic architecture done, you've got a situation where you're determining your

00:14:41.440 --> 00:14:42.860
<v Dave Jones>peripherals and your interconnects.

00:14:43.120 --> 00:14:47.240
<v Dave Jones>You're starting to develop a little bit more at the block level of diagram of a system.

00:14:47.900 --> 00:14:53.240
<v Dave Jones>And usually what happens with stuff like that is things start to very quickly rear the heads

00:14:53.240 --> 00:14:53.540
<v Dave Jones>going.

00:14:53.540 --> 00:14:57.360
<v Dave Jones>This is going to be the bottleneck of the system.

00:14:57.920 --> 00:15:01.300
<v Dave Jones>Sometimes it's getting power consumption down to virtually nothing.

00:15:01.920 --> 00:15:04.000
<v Dave Jones>Medical implantables, that's a big issue.

00:15:04.760 --> 00:15:08.200
<v Dave Jones>So you want to get the power consumption down to, you know, like virtually nothing.

00:15:08.320 --> 00:15:11.020
<v Dave Jones>And that could take up 90 percent of your effort.

00:15:11.420 --> 00:15:12.780
<v Dave Jones>And the rest of it's straightforward.

00:15:12.960 --> 00:15:15.740
<v Dave Jones>Or I worked on a multi-camera endoscope.

00:15:16.140 --> 00:15:19.760
<v Dave Jones>And the thing that turned out to be the gating problem with that system

00:15:19.760 --> 00:15:23.580
<v Dave Jones>was the miniaturization of the distal head on the endoscope.

00:15:23.860 --> 00:15:26.960
<v Dave Jones>In this particular case, we were packing five video cameras

00:15:26.960 --> 00:15:32.960
<v Dave Jones>into an area that was 11 millimeters in diameter and 13 millimeters long.

00:15:33.480 --> 00:15:36.920
<v Dave Jones>And we had five video cameras in there.

00:15:36.920 --> 00:15:37.180
<v Dave Jones>Wow.

00:15:37.460 --> 00:15:40.220
<v Chris Gammell>And that's the actual like sensor down in the endoscope,

00:15:40.340 --> 00:15:43.360
<v Chris Gammell>not like fiber coming back out to a sensor up top.

00:15:43.720 --> 00:15:44.160
<v Dave Jones>Correct.

00:15:44.360 --> 00:15:49.060
<v Dave Jones>The fiber sensor method was done many years ago and has become obsolete.

00:15:49.060 --> 00:15:51.680
<v Dave Jones>The cameras are in the distal heads of the endoscopes these days.

00:15:52.200 --> 00:15:56.940
<v Dave Jones>But for that particular situation, we developed an entire endoscope system front to back.

00:15:57.320 --> 00:16:00.440
<v Dave Jones>The desktop box, it basically runs and controls everything,

00:16:00.700 --> 00:16:02.760
<v Dave Jones>all the computer systems, et cetera, et cetera, et cetera.

00:16:03.480 --> 00:16:08.260
<v Dave Jones>And it was a situation where the gating issue that took the most amount of engineering time

00:16:08.260 --> 00:16:10.200
<v Dave Jones>was the miniaturization of that distal head.

00:16:10.740 --> 00:16:10.920
<v Chris Gammell>Got it.

00:16:11.020 --> 00:16:12.540
<v Chris Gammell>That's good, though, because like in both those cases,

00:16:12.540 --> 00:16:15.960
<v Chris Gammell>you're kind of talking about kind of figuring out the hardest tasks.

00:16:15.960 --> 00:16:20.600
<v Chris Gammell>It's not saying, oh, the Bluetooth part will be easy or, oh, the power will be easy.

00:16:20.600 --> 00:16:23.520
<v Chris Gammell>But it's just like, where are we going to focus our attention?

00:16:23.960 --> 00:16:26.080
<v Chris Gammell>Do you have any methods for kind of intuition?

00:16:26.320 --> 00:16:27.140
<v Chris Gammell>Is it experience?

00:16:27.300 --> 00:16:30.700
<v Chris Gammell>Like, how do you figure out what will be the hardest part of those black boxes?

00:16:30.700 --> 00:16:33.700
<v Dave Jones>I think it's an experience question largely.

00:16:34.020 --> 00:16:38.100
<v Dave Jones>Once you define the architecture of a system, certain things will stand out as straightforward

00:16:38.100 --> 00:16:40.180
<v Dave Jones>to experienced designers.

00:16:40.840 --> 00:16:42.840
<v Dave Jones>You know, you've been in the business for 20 odd years.

00:16:42.960 --> 00:16:46.280
<v Dave Jones>So I'm sure you've looked at a system and gone, this is the beast.

00:16:46.400 --> 00:16:47.420
<v Dave Jones>The rest of it's straightforward.

00:16:48.220 --> 00:16:53.740
<v Dave Jones>And consequently, those types of things largely gate on experience.

00:16:53.740 --> 00:16:59.240
<v Dave Jones>I've always said with a good engineering team, you can have 10 fresh graduates out of college.

00:16:59.460 --> 00:17:03.220
<v Dave Jones>But if you got one or two experienced people to give them guidance, you can get something

00:17:03.220 --> 00:17:04.400
<v Dave Jones>productive out of all of them.

00:17:04.760 --> 00:17:06.360
<v Chris Gammell>It's tough to have that experience sometimes, too.

00:17:06.440 --> 00:17:09.940
<v Chris Gammell>Like, I mean, it sounds like in this scenario, too, we're also talking about companies that

00:17:09.940 --> 00:17:15.020
<v Chris Gammell>are going external to hire your experience or similar kind of things as well.

00:17:15.140 --> 00:17:15.320
<v Chris Gammell>Right.

00:17:15.360 --> 00:17:17.960
<v Chris Gammell>And so then you'd be coming in, you'd be guiding them.

00:17:18.040 --> 00:17:19.560
<v Chris Gammell>You'd be like kind of pointing out like that.

00:17:19.620 --> 00:17:21.840
<v Chris Gammell>Oh, there'd be there'd be dragons, that sort of thing.

00:17:21.840 --> 00:17:24.200
<v Dave Jones>There'd be dragons with big headaches.

00:17:24.540 --> 00:17:24.660
<v Dave Jones>Yeah.

00:17:24.660 --> 00:17:26.700
<v Dave Jones>Make sure you have a large bottle of Tylenol.

00:17:28.100 --> 00:17:28.500
<v Chris Gammell>Yeah.

00:17:28.520 --> 00:17:32.880
<v Chris Gammell>And it does kind of seem like from your, you know, just going through the various kind

00:17:32.880 --> 00:17:38.640
<v Chris Gammell>of high level chapters as well, the power systems, battery power, EMI, external driving

00:17:38.640 --> 00:17:39.900
<v Chris Gammell>peripheral stuff like that.

00:17:39.920 --> 00:17:44.800
<v Chris Gammell>It sounds like each of these might be definitely areas of focus for those junior teams that you're

00:17:44.800 --> 00:17:45.080
<v Chris Gammell>advising.

00:17:45.240 --> 00:17:45.400
<v Dave Jones>Sure.

00:17:46.000 --> 00:17:51.700
<v Dave Jones>But it's also a situation where if you look at the nature of the book, it's

00:17:51.700 --> 00:17:58.940
<v Dave Jones>very much a situation where the things that I focus on are the things that screw people

00:17:58.940 --> 00:18:00.560
<v Dave Jones>up in their design cycle.

00:18:01.260 --> 00:18:05.760
<v Dave Jones>And those things predominantly are analog in nature.

00:18:06.180 --> 00:18:10.940
<v Dave Jones>You may be dealing with a digital system end to end, but the problems tend to be analog.

00:18:12.360 --> 00:18:13.420
<v Dave Jones>Well, think about it.

00:18:13.660 --> 00:18:15.960
<v Dave Jones>Digital communication is all about data corruption.

00:18:15.960 --> 00:18:22.000
<v Dave Jones>Short from low speed and short proximity connections, you know, like an I2C situation, it's easy

00:18:22.000 --> 00:18:26.980
<v Dave Jones>on a board because you're going maybe a megahertz, a few megahertz in data rate, a couple of inches

00:18:26.980 --> 00:18:28.340
<v Dave Jones>across a common ground board.

00:18:28.460 --> 00:18:28.980
<v Dave Jones>That's easy.

00:18:29.700 --> 00:18:33.340
<v Dave Jones>But you start to do high speed data, it starts to get messy.

00:18:33.740 --> 00:18:37.380
<v Dave Jones>It starts to turn into an analog problem and a signal corruption problem.

00:18:37.900 --> 00:18:39.060
<v Dave Jones>Power systems are similar.

00:18:39.600 --> 00:18:41.380
<v Dave Jones>What screws up in power systems?

00:18:41.380 --> 00:18:44.240
<v Dave Jones>The things that fail are usually due to noise.

00:18:44.560 --> 00:18:46.380
<v Dave Jones>You get a situation with switching supplies.

00:18:47.040 --> 00:18:49.700
<v Dave Jones>You got a couple of buck converters in a system.

00:18:50.000 --> 00:18:54.400
<v Dave Jones>They're all generating all kinds of noise and they can get into your analog front ends or in

00:18:54.400 --> 00:19:02.280
<v Dave Jones>the way of switching noise, or they can just make you fail FCC section 15 on EMI, radiated

00:19:02.280 --> 00:19:02.780
<v Dave Jones>EMI.

00:19:03.240 --> 00:19:06.120
<v Dave Jones>Again, it's analog stuff that has problems.

00:19:06.800 --> 00:19:11.100
<v Dave Jones>The power systems, one of the things in the power systems chapter in the book, I go into the

00:19:11.100 --> 00:19:12.760
<v Dave Jones>basics that are available to you.

00:19:13.120 --> 00:19:19.880
<v Dave Jones>And I will usually suggest that if you need an AC to DC converter, buy that commercially.

00:19:20.120 --> 00:19:25.400
<v Dave Jones>You could develop it yourself, but the amount of time and effort involved with that, when

00:19:25.400 --> 00:19:30.800
<v Dave Jones>there's thousands of options out there from highly qualified companies and they're cutthroat

00:19:30.800 --> 00:19:35.880
<v Dave Jones>competitive on pricing, it's usually more time and money effective to just go buy the AC

00:19:35.880 --> 00:19:37.760
<v Dave Jones>to DC converter off the shelf.

00:19:37.760 --> 00:19:43.420
<v Dave Jones>Then you get like, let's say 12 volts or 5 volts or 24 volts or whatever's needed into

00:19:43.420 --> 00:19:44.580
<v Dave Jones>your circuit boards.

00:19:44.700 --> 00:19:46.840
<v Dave Jones>And at that point, you've probably got to go down to 5.

00:19:46.860 --> 00:19:48.160
<v Dave Jones>You've got to go down to 3.3.

00:19:48.260 --> 00:19:49.900
<v Dave Jones>You've probably got some stuff at 1.8.

00:19:50.120 --> 00:19:52.800
<v Dave Jones>You've probably got some stuff at 1.2.

00:19:53.260 --> 00:19:56.900
<v Dave Jones>And, you know, the different voltages of the various CMOS families.

00:19:56.900 --> 00:20:04.440
<v Dave Jones>So, you've got a situation where those buck converters are going to be something that is

00:20:04.440 --> 00:20:11.200
<v Dave Jones>generating EMI or classic case of digital thinking in an analog scenario was when somebody

00:20:11.200 --> 00:20:17.560
<v Dave Jones>had a very sensitive analog front end for signal processing and the power supply that they

00:20:17.560 --> 00:20:20.820
<v Dave Jones>put on the thing was coming from switching converter.

00:20:20.820 --> 00:20:25.580
<v Dave Jones>And basically, the switching converter was swapping the analog front end with noise.

00:20:26.320 --> 00:20:30.040
<v Dave Jones>So, again, it's the analog stuff that comes back and bites you.

00:20:30.480 --> 00:20:33.880
<v Chris Gammell>And when you come in and you like kind of parachute in for these sort of things as well, is it like

00:20:33.880 --> 00:20:38.820
<v Chris Gammell>you are often working directly with embedded engineers and you're kind of the analog guru

00:20:38.820 --> 00:20:42.220
<v Chris Gammell>who's kind of helping to wave the wand and make the problems go away?

00:20:42.480 --> 00:20:43.680
<v Dave Jones>That's been largely it.

00:20:43.800 --> 00:20:46.200
<v Dave Jones>I wish it was simple as waving wands.

00:20:46.200 --> 00:20:51.040
<v Chris Gammell>Well, of course, RFI wands, you know, little current loop wands, right?

00:20:51.340 --> 00:20:51.740
<v Chris Gammell>Okay.

00:20:52.380 --> 00:20:54.120
<v Chris Gammell>If you're sniffing out signals, for sure.

00:20:54.480 --> 00:20:55.000
<v Chris Gammell>It's interesting.

00:20:55.140 --> 00:20:58.740
<v Chris Gammell>I do wonder about like kind of effective communication with those teams as well.

00:20:58.800 --> 00:21:01.980
<v Chris Gammell>Like, I guess even in a design context, too, like what does it look like when you're

00:21:01.980 --> 00:21:03.920
<v Chris Gammell>interacting with an embedded team?

00:21:04.160 --> 00:21:09.080
<v Dave Jones>Well, I like to basically work with teams in a manner that doesn't alienate people.

00:21:09.720 --> 00:21:13.980
<v Dave Jones>And as we all know, in a group of engineers, you've got a group of egos that you've got to

00:21:13.980 --> 00:21:14.740
<v Dave Jones>deal with as well.

00:21:14.740 --> 00:21:19.560
<v Dave Jones>And the name of the game is let's have a conversation about what's going on.

00:21:19.640 --> 00:21:25.180
<v Dave Jones>Let's understand it together and help guide them in a self-discovery manner to boot.

00:21:25.580 --> 00:21:29.240
<v Dave Jones>I think we've all seen the big pretentious person that comes into the room.

00:21:29.460 --> 00:21:34.580
<v Dave Jones>Seagull manager is a lovely, often known as, you know, fly in, dumps on everything, flies

00:21:34.580 --> 00:21:34.880
<v Dave Jones>away.

00:21:35.520 --> 00:21:36.680
<v Chris Gammell>I've never heard that term, actually.

00:21:37.340 --> 00:21:38.040
<v Dave Jones>That's pretty good.

00:21:38.180 --> 00:21:38.480
<v Dave Jones>Seagull management?

00:21:38.740 --> 00:21:39.600
<v Dave Jones>Yeah, I've never heard of that.

00:21:39.660 --> 00:21:40.420
<v Dave Jones>Yeah, that's good.

00:21:40.660 --> 00:21:43.620
<v Dave Jones>The word is usually something a little bit different, but you get the idea.

00:21:43.620 --> 00:21:44.160
<v Dave Jones>Got it.

00:21:44.220 --> 00:21:44.540
<v Dave Jones>Got it.

00:21:44.580 --> 00:21:44.740
<v Dave Jones>OK.

00:21:44.880 --> 00:21:47.940
<v Dave Jones>You don't want to do that because then the people aren't going to listen to you the next

00:21:47.940 --> 00:21:48.640
<v Dave Jones>time they see you.

00:21:48.860 --> 00:21:53.020
<v Dave Jones>It's a situation where, you know, you get in a lab with a person, you start looking at

00:21:53.020 --> 00:21:58.220
<v Dave Jones>things on a scope and you say, well, you see this and here's the ground over on this board

00:21:58.220 --> 00:22:00.100
<v Dave Jones>and here's the ground over on that board.

00:22:00.100 --> 00:22:04.080
<v Dave Jones>And let's see what happens when we turn the system on to the two grounds relative to each

00:22:04.080 --> 00:22:04.300
<v Dave Jones>other.

00:22:04.880 --> 00:22:11.580
<v Dave Jones>Then what happens is you get a situation where the person, where people learn about the fact

00:22:11.580 --> 00:22:15.220
<v Dave Jones>there is no such thing as an ideal connection between things.

00:22:15.620 --> 00:22:20.320
<v Dave Jones>There's always some, you know, RLC, inductance, resistance in the connections.

00:22:20.320 --> 00:22:26.980
<v Dave Jones>And then you say, OK, now typically what gets done to deal with this variation in ground

00:22:26.980 --> 00:22:29.620
<v Dave Jones>between the two is the signals ascent differentially.

00:22:30.320 --> 00:22:34.820
<v Dave Jones>And by doing that, you can usually compensate for a volt or two of common mode noise.

00:22:35.400 --> 00:22:40.400
<v Dave Jones>That works very well at, you know, two adjacent circuit boards, the reasonably good chassis ground

00:22:40.400 --> 00:22:41.060
<v Dave Jones>underneath them.

00:22:41.700 --> 00:22:44.760
<v Dave Jones>But, oh, now we're going to extend that out to 100 feet.

00:22:44.760 --> 00:22:46.940
<v Dave Jones>Now we have to take a different approach.

00:22:47.640 --> 00:22:53.880
<v Dave Jones>And again, it's a matter of having a conversation with the involved parties about what's the

00:22:53.880 --> 00:22:55.340
<v Dave Jones>proper way to deal with it.

00:22:55.640 --> 00:23:02.700
<v Dave Jones>But let's have a self-discovery process where you learn about the nature of the problem in

00:23:02.700 --> 00:23:07.360
<v Dave Jones>a hands-on manner, because if you got the signals in front of you, you can't argue with

00:23:07.360 --> 00:23:08.400
<v Dave Jones>the nature of the signals.

00:23:09.160 --> 00:23:09.300
<v Chris Gammell>Got it.

00:23:09.360 --> 00:23:09.580
<v Chris Gammell>Yes.

00:23:09.680 --> 00:23:13.960
<v Chris Gammell>So it does sound like a lot of like bench time, a lot of kind of empirical measurement,

00:23:13.960 --> 00:23:18.580
<v Chris Gammell>things like that, you know, kind of discovery, discovery on the bench, that kind of piece.

00:23:19.100 --> 00:23:23.560
<v Dave Jones>That's a good part of it, because when I'm doing medical devices, usually what happens

00:23:23.560 --> 00:23:29.780
<v Dave Jones>is it's not so much a discovery on the bench as in the testing shop came back with all the

00:23:29.780 --> 00:23:31.200
<v Dave Jones>regulatory testing results.

00:23:32.360 --> 00:23:39.160
<v Dave Jones>And because of the failures to pass on all of that stuff, that is your lab data that you

00:23:39.160 --> 00:23:41.460
<v Dave Jones>then have to sit down and address together.

00:23:42.040 --> 00:23:43.880
<v Chris Gammell>And then you strategize through that sort of thing.

00:23:43.960 --> 00:23:49.080
<v Chris Gammell>Talk about what board turns you might be needing to make, that sort of remedial actions.

00:23:49.600 --> 00:23:53.720
<v Chris Gammell>I'm sure that's also one that when the lab report comes back, that's also when your phone

00:23:53.720 --> 00:23:55.240
<v Chris Gammell>starts ringing in the general case anyway.

00:23:55.480 --> 00:23:56.400
<v Chris Gammell>It happens that way.

00:23:56.480 --> 00:23:56.900
<v Chris Gammell>Who could fix this?

00:23:57.380 --> 00:23:58.220
<v Chris Gammell>Jerry could fix this.

00:23:58.580 --> 00:23:59.140
<v Chris Gammell>That sort of thing.

00:23:59.580 --> 00:23:59.720
<v Dave Jones>Yeah.

00:23:59.840 --> 00:24:04.480
<v Dave Jones>And sometimes when I've developed relationships with clients, I've had situations where they

00:24:04.480 --> 00:24:09.020
<v Dave Jones>get me in earlier in the game rather than later in the game so they don't make the

00:24:09.020 --> 00:24:09.840
<v Dave Jones>same mistakes.

00:24:10.500 --> 00:24:12.640
<v Dave Jones>And that can go well.

00:24:12.980 --> 00:24:19.020
<v Dave Jones>And I've had situations where the design engineers have said, can we get Jerry Toomey in here to

00:24:19.020 --> 00:24:22.160
<v Dave Jones>coach us on this a little bit because we've never done this before?

00:24:22.920 --> 00:24:26.860
<v Dave Jones>And sometimes what happens as well as if I've worked with some of these guys or ladies in

00:24:26.860 --> 00:24:31.180
<v Dave Jones>the past, I'll get a call informally and I'll try to help them out as much as I can off the

00:24:31.180 --> 00:24:31.420
<v Dave Jones>record.

00:24:31.420 --> 00:24:34.460
<v Dave Jones>They come to me with questions and stuff because they've worked with me in the past.

00:24:35.160 --> 00:24:35.280
<v Chris Gammell>Got it.

00:24:35.320 --> 00:24:35.460
<v Chris Gammell>Yeah.

00:24:35.480 --> 00:24:39.520
<v Chris Gammell>It's interesting because I mean, you do have a chapter on coding as well, but all the things

00:24:39.520 --> 00:24:43.000
<v Chris Gammell>you're talking about, it sounds like a lot of this stuff really does get solved.

00:24:43.520 --> 00:24:45.520
<v Chris Gammell>And the title of the book too, Applied Embedded Electronics.

00:24:45.800 --> 00:24:49.960
<v Chris Gammell>When I first approached it, when I first heard you on Embedded FM actually as well, I kind of

00:24:49.960 --> 00:24:54.360
<v Chris Gammell>assumed that it was going to be more kind of embedded methods that were going to fix things.

00:24:54.380 --> 00:24:57.400
<v Chris Gammell>But like you keep saying, you kind of keep coming back to the analog side of things.

00:24:57.400 --> 00:25:03.100
<v Chris Gammell>So it does seem like a lot of this is happening at the board layout stage, at the block diagram

00:25:03.100 --> 00:25:05.140
<v Chris Gammell>stage, how you're choosing architecture, that sort of thing.

00:25:05.600 --> 00:25:09.020
<v Dave Jones>It's a situation where things like architecture decisions.

00:25:09.860 --> 00:25:13.520
<v Dave Jones>One of the things I always like to say is I never have noise problems on anything that

00:25:13.520 --> 00:25:14.060
<v Dave Jones>I design.

00:25:14.360 --> 00:25:18.900
<v Dave Jones>And the reason I can say that usually with pretty good authority is because of the fact that

00:25:18.900 --> 00:25:25.060
<v Dave Jones>when I build a system up, design it myself from scratch, I include all of the contingencies

00:25:25.060 --> 00:25:32.980
<v Dave Jones>and all of the proactive solutions to noise and EMI and ESD issues from the get-go.

00:25:33.520 --> 00:25:38.460
<v Chris Gammell>Here's a man that likes the zero-ohm resistors and your extra placeholders for capacitors and

00:25:38.460 --> 00:25:39.100
<v Chris Gammell>that sort of thing.

00:25:39.320 --> 00:25:43.060
<v Dave Jones>I have no problems with doing do-not stuffs on first-generation boards.

00:25:43.420 --> 00:25:44.400
<v Dave Jones>Oh yeah, big time.

00:25:44.500 --> 00:25:48.220
<v Chris Gammell>It does kind of contrast a little bit with size constraints, but I feel like it's like you just

00:25:48.220 --> 00:25:50.720
<v Chris Gammell>say, the first one's not going to be the smallest design.

00:25:51.180 --> 00:25:54.960
<v Chris Gammell>You're going to move your way down the stack and make smaller and smaller things.

00:25:54.960 --> 00:25:56.160
<v Chris Gammell>Over time, right?

00:25:56.420 --> 00:25:56.520
<v Chris Gammell>Sure.

00:25:57.020 --> 00:26:01.280
<v Dave Jones>You would have gotten a kick out of, it wasn't a project I was involved in, but a friend

00:26:01.280 --> 00:26:04.260
<v Dave Jones>of mine was involved with this one back in my San Jose days.

00:26:04.720 --> 00:26:10.420
<v Dave Jones>The very first generation DVD player, this would be early 90s, I think it was.

00:26:10.660 --> 00:26:12.720
<v Chris Gammell>I just remember them being very, very expensive.

00:26:12.960 --> 00:26:15.660
<v Chris Gammell>Like, wow, that stuff was high end at the time.

00:26:16.220 --> 00:26:23.760
<v Dave Jones>The first generation DVD players out were, there were no IC system on a chip for those devices

00:26:23.760 --> 00:26:24.680
<v Dave Jones>at that time.

00:26:25.120 --> 00:26:30.540
<v Dave Jones>And it was a big, messy circuit board scenario for the first couple of builds.

00:26:30.860 --> 00:26:37.140
<v Dave Jones>And they got it down to something like a single board that 10 by 12 inches, something pretty

00:26:37.140 --> 00:26:37.920
<v Dave Jones>big like that.

00:26:38.220 --> 00:26:41.040
<v Dave Jones>And that's what went out as the first generation DVD players.

00:26:41.320 --> 00:26:45.420
<v Dave Jones>And this is ancient history, but the name of the game is the thing hasn't changed in the

00:26:45.420 --> 00:26:47.420
<v Dave Jones>fact that they got something out there.

00:26:47.420 --> 00:26:51.420
<v Dave Jones>There was a large amount of discrete circuitry in it, not specialized circuitry, not system

00:26:51.420 --> 00:26:52.400
<v Dave Jones>on a chip mentality.

00:26:52.840 --> 00:26:56.620
<v Dave Jones>For that first generation product, the product went for over a thousand dollars.

00:26:56.760 --> 00:26:59.740
<v Dave Jones>And this was back in early 1990s money.

00:27:00.300 --> 00:27:00.520
<v Chris Gammell>Of course.

00:27:00.600 --> 00:27:00.680
<v Chris Gammell>Yeah.

00:27:00.700 --> 00:27:04.320
<v Chris Gammell>I look at the, you know, I was at Keithley Instruments and the stuff that was out in the

00:27:04.320 --> 00:27:04.620
<v Chris Gammell>nineties.

00:27:04.780 --> 00:27:07.840
<v Chris Gammell>I looked at that in the 2010s when I was working on it.

00:27:07.940 --> 00:27:10.620
<v Chris Gammell>And I was like, oh, this stuff looks so old.

00:27:10.680 --> 00:27:13.160
<v Chris Gammell>But at the time it was like, no, that was, that was what was available.

00:27:13.160 --> 00:27:15.240
<v Chris Gammell>And that's what the chips were at.

00:27:15.360 --> 00:27:18.880
<v Chris Gammell>And it was not state of the art at the time, but it was, it was just the normal electronics

00:27:18.880 --> 00:27:19.380
<v Chris Gammell>at the time.

00:27:19.560 --> 00:27:20.720
<v Chris Gammell>And it's what you had available.

00:27:20.820 --> 00:27:21.360
<v Chris Gammell>So you worked with it.

00:27:22.000 --> 00:27:27.020
<v Dave Jones>As you go back, historically, you've got a situation, you go back to a lot of single

00:27:27.020 --> 00:27:34.280
<v Dave Jones>transistor level designs, stuff that was more, to me, that's 1970s, 1980s kind of thinking

00:27:34.280 --> 00:27:37.760
<v Dave Jones>where there were tons and tons of discreet in design.

00:27:38.060 --> 00:27:41.780
<v Dave Jones>Because you're going back into an era where the definition of an integrated circuit back

00:27:41.780 --> 00:27:48.440
<v Dave Jones>then was 555 timers, 741 op amp and 7400 series logic.

00:27:48.720 --> 00:27:49.560
<v Dave Jones>That was it.

00:27:49.640 --> 00:27:51.400
<v Dave Jones>Beyond that, you went to discrete transistors.

00:27:52.300 --> 00:27:52.320
<v Chris Gammell>Right.

00:27:52.440 --> 00:27:55.460
<v Chris Gammell>The era of looking at Jim Williams schematics and similar, right?

00:27:55.680 --> 00:27:55.880
<v Dave Jones>Yeah.

00:27:56.020 --> 00:27:59.360
<v Dave Jones>Dealing with, be it Barry Gilbert or Bob Pease.

00:27:59.520 --> 00:28:01.280
<v Dave Jones>And, you know, this is all going to be analog.

00:28:01.940 --> 00:28:08.160
<v Dave Jones>And I'm sorry, this is, it may be an analog world, but the way, the way you interface to

00:28:08.160 --> 00:28:12.160
<v Dave Jones>it is still very digital, but you do have all kinds of analog considerations making that

00:28:12.160 --> 00:28:12.400
<v Dave Jones>real.

00:28:13.200 --> 00:28:16.440
<v Chris Gammell>You know, thinking about your book and kind of your role as you, when you come into companies

00:28:16.440 --> 00:28:18.520
<v Chris Gammell>too, like how are the youngins going to learn this stuff?

00:28:18.640 --> 00:28:22.240
<v Chris Gammell>That's, you know, one thing I think about is like, you know, I'm sure LLMs will get better,

00:28:22.380 --> 00:28:27.480
<v Chris Gammell>but there's no Jerry Toomey, LLM, nor is, would it be able to act in the same manner?

00:28:27.480 --> 00:28:31.220
<v Chris Gammell>You know, there's design rules you can put into place in CAD programs and similar, but

00:28:31.220 --> 00:28:37.440
<v Chris Gammell>it does feel like when stuff hits the fan, at some point people are going to need to have

00:28:37.440 --> 00:28:39.940
<v Chris Gammell>this knowledge and kind of the intuition there.

00:28:40.040 --> 00:28:42.720
<v Chris Gammell>How are the newest engineers supposed to gather this intuition?

00:28:43.180 --> 00:28:47.740
<v Dave Jones>Frequently it's by hard, painful learning experiences, but it was that way for us when

00:28:47.740 --> 00:28:48.800
<v Dave Jones>we were starting out too.

00:28:49.280 --> 00:28:53.020
<v Dave Jones>One of the reasons for the book was I said, I don't want people to have these learning

00:28:53.020 --> 00:28:53.680
<v Dave Jones>experiences.

00:28:53.680 --> 00:28:57.600
<v Dave Jones>They follow the guidelines that I've given them in the book for, you know, everything

00:28:57.600 --> 00:29:03.360
<v Dave Jones>from how to set up a battery system to how to do their digital system to how to do the

00:29:03.360 --> 00:29:08.540
<v Dave Jones>power system, EMI, their driving peripheral devices, sensing things, all of that.

00:29:08.700 --> 00:29:14.860
<v Dave Jones>If they follow the guidelines that are here, they are going to eliminate a lot of the problems

00:29:14.860 --> 00:29:17.860
<v Dave Jones>that they're going to run into if they were on a learning curve.

00:29:18.100 --> 00:29:22.680
<v Dave Jones>Because first time design in any particular area, you're not aware of a lot of things.

00:29:22.680 --> 00:29:23.680
<v Dave Jones>You're not aware of noise.

00:29:23.800 --> 00:29:25.660
<v Dave Jones>You're not aware of the special needs of the system.

00:29:26.520 --> 00:29:29.440
<v Dave Jones>And consequently, you may end up doing it more than once.

00:29:29.760 --> 00:29:30.600
<v Chris Gammell>You don't know what you don't know.

00:29:30.680 --> 00:29:32.940
<v Chris Gammell>And then you eventually you do know what you don't know, right?

00:29:33.360 --> 00:29:37.280
<v Dave Jones>You put it together and then you go fight the fires, put the fires out.

00:29:37.480 --> 00:29:43.340
<v Dave Jones>And it's funny because about half of my career has been in board and system level work, but

00:29:43.340 --> 00:29:45.940
<v Dave Jones>about half of my career has been in integrated circuits.

00:29:46.300 --> 00:29:49.940
<v Dave Jones>I've done a lot of analog mixed signal RF design at the chip level.

00:29:49.940 --> 00:29:54.580
<v Dave Jones>Nowadays, modern engineers, they go, oh, we're going to simulate this.

00:29:54.660 --> 00:29:55.540
<v Dave Jones>We're going to simulate this.

00:29:55.620 --> 00:29:56.580
<v Dave Jones>We're going to simulate this.

00:29:56.700 --> 00:30:00.360
<v Dave Jones>And if I'm designing a chip, I'm going to be living on a simulator.

00:30:00.600 --> 00:30:02.120
<v Dave Jones>No discussion on that.

00:30:02.220 --> 00:30:02.780
<v Dave Jones>That's a given.

00:30:03.400 --> 00:30:10.640
<v Dave Jones>But if I'm designing a board, my personal approach on that is I will rarely simulate anything.

00:30:10.780 --> 00:30:13.260
<v Dave Jones>I will tend to architect it out by hand.

00:30:13.260 --> 00:30:18.240
<v Dave Jones>I will tend to build something up and then I will experimentally work with it and improve

00:30:18.240 --> 00:30:19.880
<v Dave Jones>it as on an as needed basis.

00:30:20.380 --> 00:30:21.180
<v Chris Gammell>What kind of chip level stuff?

00:30:21.400 --> 00:30:23.240
<v Dave Jones>Are you still doing that or is that more in the past?

00:30:23.680 --> 00:30:24.780
<v Dave Jones>More in the past.

00:30:25.020 --> 00:30:28.680
<v Dave Jones>I've been called in as a consultant a couple of times recently on stuff, but it's basically

00:30:28.680 --> 00:30:30.520
<v Dave Jones>been people with special needs.

00:30:30.620 --> 00:30:35.660
<v Dave Jones>They didn't understand the issues and stuff that I solved in a day or two kind of thinking.

00:30:35.660 --> 00:30:42.000
<v Dave Jones>The last big, big chip projects I did were probably RF power amplifiers.

00:30:42.360 --> 00:30:47.060
<v Dave Jones>I used to work with a company down here in Southern California, Axiom Micro Devices.

00:30:47.240 --> 00:30:48.020
<v Dave Jones>They bought out and gone.

00:30:48.320 --> 00:30:49.620
<v Dave Jones>Broadcom bought their product line.

00:30:49.920 --> 00:30:53.440
<v Dave Jones>But I was, I think, employee number six in the door there as a startup.

00:30:54.160 --> 00:31:00.080
<v Dave Jones>We were doing RF power amplifiers, but we were using CMOS foundry processes to do that.

00:31:00.520 --> 00:31:04.800
<v Dave Jones>And if you start putting together the voltages and currents and all the information associated

00:31:04.800 --> 00:31:09.520
<v Dave Jones>with an RF power amplifier and you go, wait a second, this does not work on a CMOS process

00:31:09.520 --> 00:31:10.860
<v Dave Jones>because of the voltages involved.

00:31:10.960 --> 00:31:15.380
<v Dave Jones>You have to go to gallium arsenide or, you know, some other friendly high frequency, high

00:31:15.380 --> 00:31:16.740
<v Dave Jones>voltage type of process.

00:31:16.740 --> 00:31:22.020
<v Dave Jones>We were doing electromagnetic methods, doing things down at lower voltages at the CMOS

00:31:22.020 --> 00:31:27.880
<v Dave Jones>get handling it and then going out through an RF transformer to create an actual RF power

00:31:27.880 --> 00:31:30.700
<v Dave Jones>amplifier, but doing it on a cheap CMOS process.

00:31:31.000 --> 00:31:34.780
<v Dave Jones>So it's been a couple of years since I've been doing IC design, except for, like I said,

00:31:34.800 --> 00:31:39.260
<v Dave Jones>doing some firefighting for various associates with specific problems.

00:31:40.060 --> 00:31:41.160
<v Chris Gammell>Yeah, I never gotten into that space.

00:31:41.240 --> 00:31:45.640
<v Chris Gammell>I mean, I can imagine that that really brings home, especially with the simulation kind of

00:31:45.640 --> 00:31:50.080
<v Chris Gammell>aspect of it, but like the base level nature of understanding, you know, more integrated

00:31:50.080 --> 00:31:53.660
<v Chris Gammell>circuit you might be pulling off the shelf and using in a design at a board level kind

00:31:53.660 --> 00:31:53.920
<v Chris Gammell>of thing.

00:31:54.740 --> 00:31:55.640
<v Dave Jones>Different world.

00:31:56.140 --> 00:32:00.060
<v Dave Jones>And even when you're pulling any chip off the shelf and using it, the nature of the

00:32:00.060 --> 00:32:03.920
<v Dave Jones>challenges are going to be very associated with the problem you're trying to solve and

00:32:03.920 --> 00:32:05.280
<v Dave Jones>the signals you're trying to process.

00:32:05.400 --> 00:32:09.200
<v Dave Jones>Because sometimes it's fairly straightforward stuff because it's low in frequency and you

00:32:09.200 --> 00:32:11.120
<v Dave Jones>don't require crazy resolution to do it.

00:32:11.280 --> 00:32:16.560
<v Dave Jones>But other times it's really high frequency stuff or really small signals that you have

00:32:16.560 --> 00:32:18.720
<v Dave Jones>to be extremely sensitive to how things get done.

00:32:19.220 --> 00:32:22.840
<v Chris Gammell>Ground planes and things like that on silicon, are there kind of gotchas in that space as well?

00:32:23.060 --> 00:32:29.000
<v Dave Jones>Ground planes and silicon are an exercise in suffering the fact that you will have high

00:32:29.000 --> 00:32:33.740
<v Dave Jones>frequency inductance issues and you will have the ground plane twist like a chip due to

00:32:33.740 --> 00:32:36.500
<v Dave Jones>current injection into the ground plane if you don't know what you're doing.

00:32:36.900 --> 00:32:40.720
<v Dave Jones>And you will have a similar problem with boards, as I'm sure you know.

00:32:40.840 --> 00:32:44.700
<v Dave Jones>You've probably, I'm sure you've seen variation in ground across a board dynamically.

00:32:45.200 --> 00:32:47.660
<v Dave Jones>So that's definitely an issue or problem.

00:32:47.980 --> 00:32:49.260
<v Dave Jones>There are ways to deal with it.

00:32:49.300 --> 00:32:54.060
<v Dave Jones>When you're inside of a chip, absolutely without doubt or question, it will always be a fully

00:32:54.060 --> 00:32:56.420
<v Dave Jones>differential design, no matter what it is.

00:32:56.420 --> 00:33:00.780
<v Dave Jones>And that is because you are never going to get a good hard ground reference system on

00:33:00.780 --> 00:33:01.240
<v Dave Jones>a chip.

00:33:01.480 --> 00:33:02.220
<v Dave Jones>It doesn't happen.

00:33:02.820 --> 00:33:09.340
<v Chris Gammell>So kind of like a rule of thumb for you is just to think differentially on almost any

00:33:09.340 --> 00:33:10.880
<v Chris Gammell>ground impacted system, sounds like.

00:33:11.220 --> 00:33:13.220
<v Dave Jones>If it's inside of a chip, it's always differential.

00:33:13.540 --> 00:33:19.760
<v Dave Jones>If it's on a board and if it's a five volt swing signal and I need to detect, you know,

00:33:19.760 --> 00:33:25.760
<v Dave Jones>one volt, three volt and four volts with 100 millivolts of variance on it, they don't care.

00:33:26.260 --> 00:33:27.440
<v Dave Jones>That can be ground referenced.

00:33:28.160 --> 00:33:30.520
<v Chris Gammell>Well, and you've written articles about grounding in the past as well.

00:33:30.660 --> 00:33:34.060
<v Chris Gammell>I mean, usually when I start thinking about grounding, I think about like, you know, star

00:33:34.060 --> 00:33:37.420
<v Chris Gammell>ground versus common ground versus, you know, split grounds.

00:33:37.560 --> 00:33:39.520
<v Chris Gammell>Where do you kind of fall on a lot of these things?

00:33:39.980 --> 00:33:43.940
<v Dave Jones>Well, that's to me more of a chassis and multi-board thinking.

00:33:43.940 --> 00:33:50.620
<v Dave Jones>Typically grounding, if it's on a singular circuit board, common uncut ground is the way

00:33:50.620 --> 00:33:51.020
<v Dave Jones>to go.

00:33:51.180 --> 00:33:53.220
<v Dave Jones>Dedicated ground plane is the way to go.

00:33:53.880 --> 00:33:58.300
<v Dave Jones>And sometimes if it's a big complex board, there'll even be multiple ground planes, multiple

00:33:58.300 --> 00:34:01.120
<v Dave Jones>ground plane layers, but stitched together with vias.

00:34:01.640 --> 00:34:02.260
<v Dave Jones>Yeah, tied together.

00:34:02.400 --> 00:34:03.020
<v Dave Jones>Yeah, totally.

00:34:03.300 --> 00:34:03.460
<v Dave Jones>Yeah.

00:34:03.460 --> 00:34:03.660
<v Dave Jones>Yeah.

00:34:03.860 --> 00:34:10.200
<v Chris Gammell>And I feel like the prevalence of like low cost multi-layer PCBs have really kind of changed

00:34:10.200 --> 00:34:11.320
<v Chris Gammell>the starting point for me.

00:34:11.360 --> 00:34:13.740
<v Chris Gammell>Whereas I may have like suffered a two-layer board in the past.

00:34:13.740 --> 00:34:19.080
<v Chris Gammell>I'm like, why am I even bothering, you know, just like started four and don't even be shy

00:34:19.080 --> 00:34:20.320
<v Chris Gammell>about going to six these days.

00:34:20.720 --> 00:34:21.460
<v Dave Jones>Totally agree with you.

00:34:21.680 --> 00:34:22.220
<v Dave Jones>A hundred percent.

00:34:22.560 --> 00:34:28.300
<v Dave Jones>The thing is you have to then teach people going, Hey, why have you cut the ground plane

00:34:28.300 --> 00:34:28.800
<v Dave Jones>up here?

00:34:29.160 --> 00:34:31.000
<v Dave Jones>Oh, I needed to get a signal across.

00:34:31.000 --> 00:34:38.040
<v Dave Jones>And then you go, okay, you get out the soldering iron and you patch the signal out through a

00:34:38.040 --> 00:34:42.960
<v Dave Jones>discrete thing and you put a copper patch over the thing and you go back to a solid ground

00:34:42.960 --> 00:34:43.240
<v Dave Jones>plane.

00:34:43.300 --> 00:34:47.200
<v Dave Jones>And then you look at the spectrum analyzer on EMI and you say, see, you just changed the

00:34:47.200 --> 00:34:49.960
<v Dave Jones>signal radiating from the board by about seven decibels.

00:34:49.960 --> 00:34:50.180
<v Dave Jones>Right.

00:34:50.500 --> 00:34:52.260
<v Chris Gammell>Got rid of your, your slot antenna there.

00:34:53.440 --> 00:34:57.540
<v Dave Jones>There's a lot of people that they, they come out of college and they don't understand this

00:34:57.540 --> 00:35:00.000
<v Dave Jones>stuff, especially if their focus is digital.

00:35:00.160 --> 00:35:01.400
<v Chris Gammell>You're talking to one of them, man.

00:35:01.400 --> 00:35:03.060
<v Chris Gammell>I mean, that's the thing.

00:35:03.120 --> 00:35:04.260
<v Chris Gammell>Like, where do you learn this sort of thing?

00:35:04.280 --> 00:35:09.620
<v Chris Gammell>It's like you learn it from sitting down next to a engineer such as yourself, or, you know,

00:35:09.640 --> 00:35:13.080
<v Chris Gammell>maybe someone who's at your company, but it's, I've written in the past about like the solo

00:35:13.080 --> 00:35:14.980
<v Chris Gammell>engineer and I've written about it lovingly.

00:35:14.980 --> 00:35:19.720
<v Chris Gammell>Like, I think it is possible to do so much more as a standalone engineer, either at a small

00:35:19.720 --> 00:35:21.920
<v Chris Gammell>business or just on your own if you want to build your own stuff.

00:35:22.600 --> 00:35:27.860
<v Chris Gammell>But the loss there, and often it's driven by monetary factors, is just like the fact that

00:35:27.860 --> 00:35:31.040
<v Chris Gammell>there's not anyone to learn from, you know, it's like I can learn from the internet maybe,

00:35:31.560 --> 00:35:34.680
<v Chris Gammell>but that's not quite the same as being on a bench next to you, Jerry.

00:35:34.680 --> 00:35:38.140
<v Chris Gammell>Well, that's also separating the wheat from the chaff when it comes to the internet.

00:35:39.180 --> 00:35:40.260
<v Dave Jones>I don't know if that's getting better though.

00:35:40.600 --> 00:35:41.560
<v Dave Jones>I think it's getting worse.

00:35:41.820 --> 00:35:42.960
<v Dave Jones>And probably so.

00:35:43.180 --> 00:35:49.400
<v Dave Jones>We've all had situations where people get on Reddit or EDA board or one of the other places that

00:35:49.400 --> 00:35:51.600
<v Dave Jones>host engineering discussion groups.

00:35:51.860 --> 00:35:56.980
<v Dave Jones>And some people love to have their opinion, but unfortunately they don't have the experience

00:35:56.980 --> 00:35:59.480
<v Dave Jones>or knowledge to back up what they're proselytizing.

00:36:00.200 --> 00:36:00.320
<v Chris Gammell>Sure.

00:36:00.520 --> 00:36:00.760
<v Chris Gammell>Sure.

00:36:00.840 --> 00:36:02.300
<v Chris Gammell>But on the internet, nobody knows your dog.

00:36:04.420 --> 00:36:05.600
<v Dave Jones>Yeah, this is true.

00:36:05.720 --> 00:36:07.320
<v Dave Jones>Even if you do get a blue check mark.

00:36:07.600 --> 00:36:07.860
<v Chris Gammell>Right.

00:36:08.780 --> 00:36:09.880
<v Dave Jones>You've got to pay for that.

00:36:10.080 --> 00:36:10.900
<v Chris Gammell>You've just got to pay for it.

00:36:10.920 --> 00:36:11.280
<v Chris Gammell>That's right.

00:36:11.360 --> 00:36:15.340
<v Chris Gammell>Honestly, that's what I worry about with the, you know, the LLMs kind of being in the mix

00:36:15.340 --> 00:36:19.280
<v Chris Gammell>these days too, is that like, you know, I've fallen subject to it myself of just like,

00:36:19.280 --> 00:36:22.660
<v Chris Gammell>oh, well, I lovingly call it the dummy box because it makes me into a dummy.

00:36:22.860 --> 00:36:27.000
<v Chris Gammell>But like I asked the dummy box for a question and it confidently tells me an answer.

00:36:27.320 --> 00:36:31.640
<v Chris Gammell>But like, if it doesn't know anything about signal grounding and, you know, best practices,

00:36:31.940 --> 00:36:35.740
<v Chris Gammell>I'm, you know, if I'm taking it on faith and not looking at references and not looking at

00:36:35.740 --> 00:36:39.060
<v Chris Gammell>multiple sources and not looking at, you know, sources of truth, like books and primary

00:36:39.060 --> 00:36:44.360
<v Chris Gammell>sources, it's like, okay, well, I might just be listening to a blue check mark or, you know,

00:36:44.360 --> 00:36:48.720
<v Chris Gammell>a dog on the internet, but it's actually just in the form of a LLM, you know, that sort of thing.

00:36:48.720 --> 00:36:54.140
<v Dave Jones>Yeah. And the thing is the AI tools that are out there, they're in their infancy,

00:36:54.440 --> 00:37:01.140
<v Dave Jones>but they're growing and they're improving. Most of those have lots of room for improvement. But

00:37:01.140 --> 00:37:07.640
<v Dave Jones>again, I cautioned that, you know, that was the case when the Osborne portable computer came out

00:37:07.640 --> 00:37:14.340
<v Dave Jones>40 years ago and it was a huge box with a huge handle. And this is a portable computer back in that

00:37:14.340 --> 00:37:19.080
<v Dave Jones>era and look where we are today. So I think you're going to see that improve.

00:37:20.360 --> 00:37:26.220
<v Dave Jones>But there's room for improvement. And the thing I tell people that feel threatened by AI, as I say,

00:37:26.660 --> 00:37:33.520
<v Dave Jones>go ask AI about the topic that you know more about than anybody else in the world,

00:37:33.520 --> 00:37:38.260
<v Dave Jones>or you've worked with extensively, and you'll actually find out how stupid AI is right now.

00:37:38.260 --> 00:37:40.260
<v Dave Jones>It'll get in better. It will get better.

00:37:40.720 --> 00:37:44.880
<v Chris Gammell>I'm not concerned about it getting being not being good enough. Now I'm worried about my own

00:37:44.880 --> 00:37:48.920
<v Chris Gammell>kind of reliance on it, you know, kind of that sneaking reliance on it where I ask it a question.

00:37:49.060 --> 00:37:52.220
<v Chris Gammell>Oh, okay. You know, try a thing. It's just try a thing. It's just that sort of thing.

00:37:52.400 --> 00:37:56.560
<v Chris Gammell>But then more broadly, I worry about kind of the whole world being in that in that direction as well.

00:37:56.600 --> 00:38:00.840
<v Chris Gammell>And it's like, yeah, I'm sure it's going to get better. But the true intuition and you know,

00:38:00.840 --> 00:38:06.020
<v Chris Gammell>when the rubber hits the road, when someone's not passing EMI testing, and they're on a bench,

00:38:06.020 --> 00:38:11.520
<v Chris Gammell>and the LLM or the dummy box is no longer suggesting things that make sense, then what,

00:38:11.640 --> 00:38:16.020
<v Chris Gammell>right? Like when there's truly no one who knows anymore, you know, like, what do we do then?

00:38:16.900 --> 00:38:21.980
<v Dave Jones>And that's why they write books. And that's why even today, people read books from 3000 years ago

00:38:21.980 --> 00:38:27.820
<v Dave Jones>that were written in Greek, or written in Latin, or whatever. And they're still able to find

00:38:27.820 --> 00:38:29.780
<v Dave Jones>philosophical knowledge from those things.

00:38:29.780 --> 00:38:33.640
<v Dave Jones>It's not like they're depublishing your book and others. So yeah, I guess that is a good point.

00:38:33.940 --> 00:38:37.080
<v Dave Jones>Goodness. Now that would be a badge of honor having my book banned.

00:38:37.260 --> 00:38:37.400
<v Dave Jones>Yeah.

00:38:39.440 --> 00:38:45.360
<v Dave Jones>But we've got a situation where one of the many other things that gets done here is the

00:38:45.360 --> 00:38:50.720
<v Dave Jones>organization of the book, as we started to talk about before, it's based upon topics. It's based

00:38:50.720 --> 00:38:55.800
<v Dave Jones>upon, okay, you got to do a battery system. So there's a chapter on how to do battery systems.

00:38:55.800 --> 00:39:03.440
<v Dave Jones>And what are the options there? What are the battery chemistries there? What's viable right now?

00:39:03.760 --> 00:39:08.920
<v Dave Jones>And I always have a caveat emptor on that one of the fact that, oh, battery technology is changing

00:39:08.920 --> 00:39:13.760
<v Dave Jones>and changing a lot. It's growing by leaps and bounds. It's getting progressively better,

00:39:13.760 --> 00:39:20.120
<v Dave Jones>but it's a slow progression. There haven't been any radical breakthroughs. It's been more of an

00:39:20.120 --> 00:39:26.600
<v Dave Jones>evolution than radical steps taking forward. Yeah. I guess no new chemistries that a lot

00:39:26.600 --> 00:39:29.900
<v Chris Gammell>of people are going to have access to. One thing that I've noticed in the battery space has just

00:39:29.900 --> 00:39:35.360
<v Chris Gammell>been maybe, and it may just be where I'm focused personally, but like, it's just like the increasingly

00:39:35.360 --> 00:39:40.780
<v Chris Gammell>small battery size, you know, just because of size constraint for devices and the fact that they can

00:39:40.780 --> 00:39:45.140
<v Chris Gammell>make, you know, 20 million amp hour batteries and just these ridiculously small form factors.

00:39:45.140 --> 00:39:51.240
<v Chris Gammell>And then it's down to the engineer to like, just make designs that can sip incredibly small currents

00:39:51.240 --> 00:39:55.880
<v Chris Gammell>and still wake up and do something useful with that. And, and, you know, persist for hours, days,

00:39:56.140 --> 00:40:02.060
<v Dave Jones>weeks, whatever. Bluetooth is a great example of that. Bluetooth systems, Bluetooth, low power systems

00:40:02.060 --> 00:40:10.260
<v Dave Jones>do two things. One, they work with a extremely small duty cycles. So they're very briefly on do their

00:40:10.260 --> 00:40:15.400
<v Dave Jones>thing. And then they, they're, they're basically off for 95% of the time or even more. There's a

00:40:15.400 --> 00:40:20.600
<v Dave Jones>background digital controller, but the, the actual RF circuits are live for extremely short periods of

00:40:20.600 --> 00:40:27.120
<v Dave Jones>time. And the other thing too, is they do try to power optimize what's there. So reduce the overall

00:40:27.120 --> 00:40:33.980
<v Dave Jones>power, reduce the duty cycle. And as you know, things like Bluetooth or distributed network systems

00:40:33.980 --> 00:40:38.480
<v Dave Jones>nowadays, um, internet of things are all. I should probably should have known that. That's the,

00:40:38.480 --> 00:40:41.100
<v Chris Gammell>that's the space I work in. I should probably should have been what you were talking about,

00:40:41.140 --> 00:40:45.340
<v Dave Jones>but yeah. Yeah. And IOT stuff, a lot of it, they require two hours of battery life

00:40:45.340 --> 00:40:48.580
<v Dave Jones>as to pass the standard. I'm sure you've run into that already.

00:40:49.300 --> 00:40:53.540
<v Chris Gammell>Uh, actually I, I don't know what you mean by that. Like a Bluetooth based device that is IOT

00:40:53.540 --> 00:40:56.900
<v Chris Gammell>centric or is there some kind of regulation that I, maybe I don't know.

00:40:56.900 --> 00:41:05.920
<v Dave Jones>There's a few standards that are out there that are for IOT where they've got a distributed mesh

00:41:05.920 --> 00:41:13.200
<v Dave Jones>network in a house and to meet the standard of the product line that's doing it. They mandate that

00:41:13.200 --> 00:41:19.500
<v Dave Jones>the battery life must be two years or a year or whatever the heck it is, because they're,

00:41:19.540 --> 00:41:24.320
<v Dave Jones>they're doing a mesh network throughout a house. Now, do you really want to go back and change out

00:41:24.320 --> 00:41:29.220
<v Dave Jones>all the batteries in the 35 things you've got around the house every two months? No, you don't.

00:41:29.320 --> 00:41:29.780
<v Dave Jones>Of course not.

00:41:29.780 --> 00:41:33.960
<v Chris Gammell>Got it. I heard you say two hours. That's where, that's where my confusion was. So did two years

00:41:33.960 --> 00:41:36.080
<v Chris Gammell>makes more sense? Okay. Yeah. Yeah. So got it.

00:41:36.080 --> 00:41:41.600
<v Dave Jones>Two years. Yeah. IOT does a lot of that because they're, they're pushing wireless and they're

00:41:41.600 --> 00:41:48.240
<v Dave Jones>pushing basically wireless communication and no hardwired power whenever possible. I've got mixed

00:41:48.240 --> 00:41:53.860
<v Dave Jones>feelings about that. I mean, I've kind of, of the opinion, I prefer things that plug into the wall

00:41:53.860 --> 00:41:58.680
<v Dave Jones>just for reliability, get the batteries out of the equation. Consequently, in a lot of applications,

00:41:58.680 --> 00:42:01.420
<v Dave Jones>I'll say, do you really need this thing to be battery powered?

00:42:01.800 --> 00:42:05.260
<v Chris Gammell>And that's like a system level design too, right? That's like an architectural type of thing. It's

00:42:05.260 --> 00:42:10.680
<v Chris Gammell>like, is it something that's driving product decision versus just a expectation from a product

00:42:10.680 --> 00:42:16.040
<v Dave Jones>maker? Sure. As we all know, ease of use is important. Reliability without having to muss and

00:42:16.040 --> 00:42:20.660
<v Dave Jones>fuss with it is important for something to be marketable. There were, there were a bunch of

00:42:20.660 --> 00:42:28.780
<v Dave Jones>products out there probably back in the nineties through the 2010, 2015 region. There were a lot

00:42:28.780 --> 00:42:32.440
<v Dave Jones>of things out there where the battery life was not that good. Cell phones come to mind.

00:42:33.040 --> 00:42:38.640
<v Dave Jones>You probably remember Nokia phones being extremely popular because they got the battery life thing

00:42:38.640 --> 00:42:42.480
<v Dave Jones>down to something low aggravation where you constantly weren't on a charger.

00:42:42.920 --> 00:42:46.200
<v Chris Gammell>Whenever I think of like nineties battery problems, I was thinking of the Sega Game Gear.

00:42:46.200 --> 00:42:49.860
<v Chris Gammell>My friend would like load six double A's into there and it'd get like four hours of battery life.

00:42:50.000 --> 00:42:54.020
<v Chris Gammell>And then he'd like frustratingly like rip them out and replace them. And it would just be a pile of

00:42:54.020 --> 00:42:57.820
<v Chris Gammell>dead batteries if he was going on a road trip somewhere. And it's just like, oh, that's kind

00:42:57.820 --> 00:43:01.300
<v Chris Gammell>of wasteful. At the time they had like, they were like linear regulators and some of the handhelds

00:43:01.300 --> 00:43:05.420
<v Chris Gammell>that were out there too. And there were full color VGA, you know, style displays. And it's just,

00:43:05.540 --> 00:43:08.460
<v Chris Gammell>no, that's not going to work out great in the timeframe it was in.

00:43:08.980 --> 00:43:12.020
<v Chris Gammell>Well, as long as they're not having to power up a cathode ray tube, right?

00:43:12.500 --> 00:43:13.800
<v Chris Gammell>Yeah, right, right. Exactly.

00:43:13.800 --> 00:43:19.060
<v Dave Jones>You know, a lot of this is stuff that you basically, you can get experience and you can

00:43:19.060 --> 00:43:22.880
<v Dave Jones>learn about the stuff. But a lot of times what happens is you learn from your mistakes

00:43:22.880 --> 00:43:27.960
<v Dave Jones>and I'm trying to minimize the number of mistakes. You're going to make it work

00:43:27.960 --> 00:43:34.520
<v Dave Jones>with the chapters that are in the book, because we're dealing with how to do things and how to

00:43:34.520 --> 00:43:39.340
<v Dave Jones>do things based upon what's needed to be applied in the real world.

00:43:39.340 --> 00:43:44.360
<v Chris Gammell>Well, looking forward, I mean, like you've had a long storied career. What are you excited about

00:43:44.360 --> 00:43:47.740
<v Chris Gammell>the electronic space in the near future? Are you trying out new projects? Are you

00:43:47.740 --> 00:43:49.600
<v Chris Gammell>writing new books, that sort of thing?

00:43:49.800 --> 00:43:53.800
<v Dave Jones>I've been debating doing a couple of other books, but I don't think they'd be electronic centric.

00:43:54.000 --> 00:44:00.880
<v Dave Jones>I have a pet peeve of mine. You're familiar with Ray Kierswell? He's a futurist that likes to

00:44:00.880 --> 00:44:06.420
<v Dave Jones>claim the singularity is coming. And he writes books about the singularity approaching and things like

00:44:06.420 --> 00:44:12.300
<v Dave Jones>that. And I've read a couple of his books and I look at some of the things he predicts and he's

00:44:12.300 --> 00:44:19.500
<v Dave Jones>just so detached from what can be realized. You know, magical things. We've reached limitations

00:44:19.500 --> 00:44:24.800
<v Dave Jones>on CMOS scaling. It's kind of like they talk about the two nanometer CMOS node, but the truth be known

00:44:24.800 --> 00:44:31.700
<v Dave Jones>is you really can't go below. I think it's 10 or 11 nanometers due to physics. And consequently,

00:44:31.700 --> 00:44:36.340
<v Dave Jones>they're sort of lying to you when they say they, oh, this is the two nanometer mode. And I go, okay,

00:44:36.340 --> 00:44:41.320
<v Dave Jones>where's the two nanometer features in this thing? And they don't exist. So we've been running Moore's

00:44:41.320 --> 00:44:48.940
<v Dave Jones>law, hot and heavy for 40 years. Yes. Right. And then in the right here and now, the way people are

00:44:48.940 --> 00:44:56.300
<v Dave Jones>improving things is they're not improving things with smaller transistors. They're more improving

00:44:56.300 --> 00:45:05.640
<v Dave Jones>things with more parallel processing. And that is an issue that I haven't seen any breakthroughs. I,

00:45:05.760 --> 00:45:11.080
<v Dave Jones>I read a little bit about quantum computing here and there, but I haven't seen anything yet that I

00:45:11.080 --> 00:45:15.900
<v Dave Jones>would consider is going to get the same kind of widespread application that you would actually have,

00:45:15.980 --> 00:45:21.560
<v Chris Gammell>you know, with a typical CMOS ASIC. Yeah. I wonder about in, in a lot of these cases too,

00:45:21.600 --> 00:45:25.860
<v Chris Gammell>of like they were driving up efficiency by driving down power rails in the past as well. So parallelization,

00:45:25.860 --> 00:45:32.140
<v Chris Gammell>lower voltages, but we're just like, we've approached diode voltages for, you know, like it does seem like

00:45:32.140 --> 00:45:37.220
<v Chris Gammell>kind of the, the gas is out of the tank. And so then where, where do you go from there? Software also

00:45:37.220 --> 00:45:40.560
<v Chris Gammell>does improve a lot of these things, you know, just writing better algorithms, that sort of thing.

00:45:40.860 --> 00:45:46.480
<v Dave Jones>There's an article I did for electronic design. It's still up on my website and electronics design

00:45:46.480 --> 00:45:53.300
<v Dave Jones>still has it on their website as well. And the title of the article, I may, I'm paraphrasing here was,

00:45:53.300 --> 00:45:57.920
<v Chris Gammell>um, tiny transistors, giant molecules, Moore's law crashes into the laws of physics. Yeah. I'm

00:45:57.920 --> 00:46:02.560
<v Dave Jones>looking at it right now. That's it. That's a good one. The predictions that I had in that sort of,

00:46:02.860 --> 00:46:07.540
<v Dave Jones>you know, they rang true, but the way we did things even back 15 years ago is we're going to more and

00:46:07.540 --> 00:46:14.240
<v Dave Jones>more parallel processing. And if you look at the clocking of PCs microprocessor, uh, the PC

00:46:14.240 --> 00:46:18.440
<v Dave Jones>microprocessor clocking rate hasn't really significantly changed in the last five or 10 years.

00:46:18.440 --> 00:46:25.000
<v Dave Jones>You know, it's incrementally gone up a little bit, but it wasn't like way back when the PC was a new

00:46:25.000 --> 00:46:31.800
<v Dave Jones>thing and, Oh, 20 megahertz, uh, and six months later, 80 megahertz and six months later, 200 megahertz

00:46:31.800 --> 00:46:37.620
<v Dave Jones>and 133 megahertz with a turbo button. Right. And what happened is, you know, we kind of got up into

00:46:37.620 --> 00:46:44.960
<v Dave Jones>the three gigahertz clocking range on the internals on a microprocessor. And I think the fastest thing out

00:46:44.960 --> 00:46:51.340
<v Dave Jones>there right now in common CMOS microprocessors is on the order of about a five gigahertz internal clock.

00:46:51.840 --> 00:46:58.060
<v Dave Jones>That is a situation where the reason they're getting beyond that is parasitics. They've got a

00:46:58.060 --> 00:47:03.860
<v Dave Jones>situation with distributed capacitance, distributed inductances of interconnects. I can get those

00:47:03.860 --> 00:47:09.980
<v Dave Jones>transistors to go at 20 gigahertz and I've done it. But once you go out into a distributed logic system,

00:47:10.060 --> 00:47:14.540
<v Dave Jones>you know, with auto routing and auto layout and all that good stuff, you're back down at,

00:47:14.540 --> 00:47:18.700
<v Dave Jones>you know, the five gigahertz are even worse, worse than that, just to keep the thing surviving

00:47:18.700 --> 00:47:24.200
<v Dave Jones>in the environment that's got distributed capacitance and inductance associated with the signals.

00:47:24.920 --> 00:47:28.680
<v Chris Gammell>Yeah. Like making timing across the chip, that sort of thing. And all the edges you need to make,

00:47:28.720 --> 00:47:30.660
<v Chris Gammell>all of the pipeline you need to do that sort of thing.

00:47:30.840 --> 00:47:31.640
<v Chris Gammell>Sure. Exactly.

00:47:32.040 --> 00:47:35.860
<v Chris Gammell>Yeah. It is interesting, like looking at the spec, you know, I'm on a Mac M4, whatever,

00:47:35.860 --> 00:47:41.700
<v Chris Gammell>and it's just like the number of cores and GPUs. And like you said, it's just more and more of the

00:47:41.700 --> 00:47:44.760
<v Chris Gammell>same, but put towards different tasks internally with software, that sort of thing.

00:47:45.040 --> 00:47:49.500
<v Dave Jones>It's basically more parallel processing. And we're also dealing with a situation where aren't they

00:47:49.500 --> 00:47:53.300
<v Dave Jones>still, isn't Intel still trying to do x86 compliance devices?

00:47:53.620 --> 00:47:55.580
<v Chris Gammell>I don't think anyone knows what Intel is doing these days, Jerry.

00:47:57.040 --> 00:47:57.980
<v Chris Gammell>Yeah, this is true.

00:47:57.980 --> 00:48:00.280
<v Chris Gammell>If anyone's listening from Intel, good luck to you, sir or madam.

00:48:01.360 --> 00:48:06.040
<v Dave Jones>Yeah, because let's face it, the microprocessor has gone to risk architecture devices.

00:48:06.040 --> 00:48:11.580
<v Dave Jones>And there's a real good reason for that because you eliminate a ton of useless architecture issues

00:48:11.580 --> 00:48:18.820
<v Dave Jones>and transistors and things like that, that were created to support a rather complex instruction set.

00:48:19.180 --> 00:48:23.320
<v Dave Jones>You didn't need that. They went to risk processors, done much better with that.

00:48:23.680 --> 00:48:29.240
<v Dave Jones>As you know, things like ARM architectures are all risk processor architectures.

00:48:29.240 --> 00:48:33.840
<v Dave Jones>They don't support a complex instruction set like an Intel x86 compliant device does.

00:48:33.840 --> 00:48:38.900
<v Dave Jones>It's kind of, how do I put it this way? Legacy devices, unfortunately,

00:48:39.480 --> 00:48:42.340
<v Dave Jones>trying to make things backwards compatible. You pay prices.

00:48:43.300 --> 00:48:46.620
<v Chris Gammell>Yeah, totally. Yeah, you're hauling a lot of baggage with you on the way forward, huh?

00:48:47.600 --> 00:48:48.320
<v Chris Gammell>Oh, yeah.

00:48:48.440 --> 00:48:54.220
<v Chris Gammell>Yeah, that actually could probably be Intel's current tagline, hauling a lot of baggage.

00:48:55.960 --> 00:49:00.260
<v Dave Jones>Well, I haven't worked with Intel in a long time. I'd be curious to know what's going on

00:49:00.260 --> 00:49:03.220
<v Dave Jones>in there relative to foundry issues and what they're doing there.

00:49:03.380 --> 00:49:03.860
<v Dave Jones>Yeah, totally.

00:49:03.980 --> 00:49:07.020
<v Dave Jones>And what they're doing looking at next generation architectures because,

00:49:07.220 --> 00:49:10.580
<v Dave Jones>yeah, they've kind of fallen by the wayside to a certain extent.

00:49:10.720 --> 00:49:14.060
<v Chris Gammell>Yeah. Yep. Well, Jerry, where can people find you? Where can they find your book?

00:49:14.200 --> 00:49:15.380
<v Chris Gammell>Where can they reach out if they're interested?

00:49:15.500 --> 00:49:19.860
<v Dave Jones>Okay. The book is published by O'Reilly Publishing. They're huge. A lot of people in the

00:49:19.860 --> 00:49:24.160
<v Dave Jones>software world, tons of software books put out by O'Reilly. Title of the book is Applied

00:49:24.160 --> 00:49:30.380
<v Dave Jones>Embedded Electronics, and the subtitle is Design Essentials for Robust Systems. It's available

00:49:30.380 --> 00:49:37.160
<v Dave Jones>online on Amazon, Barnes & Noble. There's actually a specialty copy that's done for the India market

00:49:37.160 --> 00:49:46.980
<v Dave Jones>that's coming out of a publisher in India as well. And they can find me at effectiveelectrons.com.

00:49:47.180 --> 00:49:53.340
<v Dave Jones>On that site, you'll find a list of my publications, information about the book and what's in the book.

00:49:53.340 --> 00:49:58.480
<v Dave Jones>Also, I personally can be found on LinkedIn. If anybody in the world of hardware engineering

00:49:58.480 --> 00:50:03.500
<v Dave Jones>electronics asks me for a connection, I'll give them a connection on LinkedIn just because of the

00:50:03.500 --> 00:50:10.600
<v Dave Jones>fact that the hardware guys I keep close to me and the marketing and salespeople I kind of ignore.

00:50:11.340 --> 00:50:15.780
<v Chris Gammell>Got it. Yeah. All right. That's great. Well, Jerry, thank you for being here. I really appreciate it.

00:50:15.800 --> 00:50:18.240
<v Chris Gammell>Thanks for writing this book. I'm sure a lot of people are going to get a lot out of it. So thanks

00:50:18.240 --> 00:50:22.060
<v Dave Jones>for being here. Thanks for having me, Chris. Enjoy doing it. Please reach out if you've got any

00:50:22.060 --> 00:50:26.460
<v Dave Jones>questions on things because I'd be happy to help you out. Thanks so much. Okay. Have a good day now.

00:50:26.460 --> 00:50:26.960
<v Dave Jones>Bye.
