#95 – An Interview with Øyvind Janbu - Feracious Fabless Facilitator

Download episode · 32 MB
Also on Apple · Spotify · YouTube · RSS
Show Notes
[display_podcast]
Welcome Øyvind Janbu, CTO of Energy Micro!
- Øyvind went to school in Trondheim where there are multiple schools and many tech companies based around them.
- Many early members, including the CEO, were part of ChipCon, which was later purchased by Texas Instruments.
- Energy Micro (EM) is mostly employee owned.
- Since EM is a fabless semiconductor company, the processing (manufacturing) is done primarily at TSMC.
- "Le Sense" is an homage to the movie Pulp Fiction, in the same scene where they mention the Royale with Cheese.
- Energy Micro has a VP of Simplicity, dedicated to making things easier for the customer.
- The radios coming from EM are a variety of radio standards, including Bluetooth Low Energy.
- The royalties of an ARM core are confidential, but ARM has more information about licensing in their annual reports.
- Some of the newest parts in the EM Gecko family use the ARM M0+ core, which many vendors are promoting right now for low power.
- The EM products have some unusual features, like DMA from an ADC while in sleep mode.
- Energy Micro publishes their longevity guarantee right on their website for all to see.
- Chips are available through distributors like Digikey and have been part of their strategy from day one.
Many thanks to Øyvind for being on our show and giving us more insight into chip companies. He was really straightforward with his answers and we hope you learned a lot from him. Please leave any additional questions in the comments and we’ll try to make sure the proper people answer them.
Transcript
Oyvian Yanbu: This is the Amp Hour Podcast, recorded previously but aired on May 13th, 2012. Episode 95, with guest Oyvian Yanbu, Horatius Fabulous Facilitator.
Dave Jones: Welcome to the Amp Hour. I'm Dave Jones from the EEV blog.
Chris Gammell: And I'm Chris Gammell of Chris Gammell's Analog Life.
Evin Yanbu: And I'm Evin Yanbu. I'm CTO with Engine Micro. It's great to be here. Thank you for joining us.
Dave Jones: If I'm pronouncing your name correctly, it's very difficult for us Australians to pronounce that. I'm sorry.
Evin Yanbu: Yeah, I know. But it's good. It's good.
Dave Jones: It's a very common first name, isn't it?
Evin Yanbu: Actually, it's a very common first name in Energy Micro, but it's not that common in Norway. Oh, okay. You have a high percentage of Evin's in the company, which is, I think, a fantastic advantage that we have.
Dave Jones: So if you go for a job at Energy Micro, if you got the correct first name, I think you're a shoe-in.
Evin Yanbu: It's also possible to change your name if you really want the job. All right. That's good to know.
Chris Gammell: If you're really serious. People of the world around, if you're named Mike or Bob or anything else, they want you as a weapon.
Dave Jones: So you're the chief technology officer of Energy Micro, which is a startup. It is. It is. What does a CTO actually do?
Evin Yanbu: So what do I actually do or what am I supposed to be doing?
Dave Jones: Right. Oh, both.
Evin Yanbu: Okay. Well, if it takes the last question first, what am I supposed to be doing? I'm supposed to be basically defining our roadmap and figuring out what to do next and what to do for the future. Right. And then there's another guy responsible for actually doing it.
Dave Jones: Right.
Chris Gammell: So we can give you suggestions today. We want this chip. We want that chip. And then 16 to 18 months from now, we'll see it on the shelf. That's how it works. All right. Fantastic. All right. Only CTOs on the show from now on, Dave. We can just start steering the whole industry like this.
Dave Jones: And we love having CTOs on because it really gives us a technical insight into companies like this, which we only ever see from like the outside and from the chips and the salespeople and things like that. So it's really good to get an insight. So do you actually –
Chris Gammell: I think CTOs are really interesting too because it's like an executive level position, right? And yet you're still – your hands are in the technology. You're still actively – you know what's going on versus sometimes that stereotype of executives who are more looking at the numbers and dealing with the high-level stuff versus the – The real stuff. Gritty, nitty, yeah, the awesome stuff, right? The stuff we care about here.
Evin Yanbu: Yeah, exactly.
Dave Jones: So do you still get your hands dirty on a daily basis?
Evin Yanbu: Yeah, I do. I mean sometimes I do what I'm basically supposed to be doing. Right. Other periods I do work hands-on on our chip development or specific tasks. So I mean we're still a small company, right? Yeah. And so people internally we do what we need to do to get the chips out and get the software out and – yeah. So it's more of a case – Customers happy.
Dave Jones: It's more of a case if you do it because you have to because you don't have hundreds of employees to do all the work. So it's all hands on deck.
Evin Yanbu: Yeah. I think it's partly kind of do it when you have to and partly, of course, because I'm still – You're still a tech. – kind of hacky engineer. And I mean what I enjoy the most is to actually sit down and make stuff, right? Awesome. Excellent.
Dave Jones: That's brilliant. We love this guy already. All right.
Chris Gammell: We need every executive to be like that. I'm not hopeful for every executive but that's amazing that you are. And there's another example of that too like Bob Dobkin from LT. I know that he's a CTO as well. I was talking about him the other day. And he's still making chips as well.
Dave Jones: And he's still making videos as well. He did a recent video for the LT 3080 as well explaining how it works. I mean, wow. You know? Yeah.
Chris Gammell: So you guys are a rare breed and it's really cool. It's really cool, man. I aspire to that someday. Yeah.
Dave Jones: So we've got a whole bunch of viewer questions and I don't think we'll get through them all. So apologies to people who submitted questions and we don't get to them. Maybe we'll get to them in a roundabout way. But there's one question on here which raised a point right now from Hacked Fridge Magnet. That's his username from our forum. And he says basically he discovered that both you and your CEO are graduates from the same university. Is that correct?
Evin Yanbu: Yeah. Actually, I think, I don't know, like half or two-thirds or more probably of our, say, engineer employees are coming from this university. Because it's basically the best and biggest technical university in Norway.
Dave Jones: Got it. How many universities in Norway? Because you're not a terribly big country, are you, in terms of population?
Evin Yanbu: No. Actually, I mean, I would say universities with education relevant to engineering, kind of software, hardware, design, probably three. But we also have other universities, I mean, smaller ones that are coming.
Dave Jones: Got it. And are the majority of your employees from Norway or all of them?
Evin Yanbu: Yeah, well, the majority is from Norway, yeah, for sure. But we're quite an international company still. We have, I think, five or six Chinese guys employed in China.
Dave Jones: Okay.
Evin Yanbu: I mean, working with sales and FAs and reference designs and so forth. And similar also smaller groups around the world, both in sales and support.
Oyvian Yanbu: Right.
Evin Yanbu: And operations. And so we're quite an international company. Also in the design team here in Oslo, in the chip design, we have people coming from Korea and Canada and Netherlands. And I think a guy just employed now from, oh, I probably don't even remember the right country. Anyway. It's almost necessary these days.
Chris Gammell: I mean, talent comes from all over, right? It does. It does. The fact that you guys are pulling in talent from everywhere, that's a good sign of a company. You know, the fact that you're recognizing that there's good talent everywhere. So that's awesome.
Evin Yanbu: Yeah.
Dave Jones: And Hacked FridgeMax's actual question, what he was getting at, was that how important do you think it is that a CEO of a company like this actually has a technical background, is actually an engineer in this? Do you think that's important or is it better to have a CEO who's just interested in the finances or something like that?
Evin Yanbu: I think it's a really good question. So my experience from this is probably a bit one-sided because I've been working at Engine Micro now since the beginning, well, basically in 2008, although the company was founded in 2007. And before that, also spent eight years in ChipCon, which was acquired by Texas Instruments. But the whole time, it's the same CEO. So the CEO of Engine Micro also was the CEO and founder of ChipCon. And he is the tech guy. But he, I mean, he's a tech guy, but not to offend him or anything, but there's a reason why he's the CEO and not the CTO. Got it. So his passion, I think, is more into building good companies, making a success, making great stuff, rather than the details of the technology. So he really, he understands technology for sure. But he's not, yeah, you understand what I mean. Yeah. Yeah, yeah, yeah. There's a certain skill set you need to be a CEO as well. But to answer the question, I think the setting that we have with, say, a very technically driven, say, management, it works for sure. As long as you, there's at least a couple of guys that also care a lot about the finance and the funding. The business side of things, yeah. Yeah, yeah, for sure. But I'm convinced that the other, I mean, having a less technically capable CEO is also a perfect solution in another case. So I'm really not sure what the answer is. I know that our setting works very well.
Dave Jones: Yep.
Evin Yanbu: And I'm very certain that the other setting also works well for others.
Dave Jones: Which would probably be a larger, like once you get, like, huge, like you're a Texas Instruments or you're a, you know, you're a, someone like that. Maybe it's better to have a CEO who's just focused on the business finance side and the technologies left to the CTO and others who are better. True, true. Yeah.
Oyvian Yanbu: Okay. Yeah.
Chris Gammell: Okay. Well, can we maybe get, could you give us a little more background of it? You mentioned the company started in 07. You know, what was the, what was the ramp like? I mean, how did, how does, how does a startup even start up in the chip industry? I guess that's kind of the, the base question. Because I wouldn't know where to start. No.
Evin Yanbu: Well, as, as I mentioned, our CEO at the NGO Micro, which is called Geir Fera, he was also the CEO and founder of Chipcom or one of three founders of Chipcom. And Chipcom was acquired by Texas Instruments in, in 2006.
Dave Jones: And for about 200, a couple hundred million dollars, right? It was a fairly substantial amount of money. Yeah.
Evin Yanbu: Good sum of money. Excellent. Which basically led, I mean, I think Geir, he continued for another year leading that, basically leading a division of Texas Instruments. But at some point he decided that he wanted to do something else. I mean, he was more of a small company guy than a large company guy. I mean, I was there, I was there as well. I also left for another company again, but I think, I mean, Texas Instruments is a great company. I have to say. But still, sometimes you feel you need to move on, right? Sure.
Chris Gammell: Especially if you have the startup bug. It seems like people who have the startup bug just jump from startup to startup to startup because they get that rush. I've never, I've never done that myself. I don't know.
Evin Yanbu: Yeah. Yeah. I think, like, like you said, there was a fair amount of money involved in the acquisition. And I think a lot of people ask Geir, our CEO, about, okay, so why didn't you just retire, right? Yeah. Yeah, that's right. And I think the main motivation for him is that basically he wants to prove that the first time wasn't just luck. I got it. Yeah.
Chris Gammell: It's that startup mentality too. It's just the drive, man. That's awesome.
Evin Yanbu: All you startup guys, you're crazy.
Chris Gammell: I know. Yeah.
Evin Yanbu: It's great. So anyway, he and I started chatting again when, well, I had left for a little while before and he basically resigned and he didn't know what to do. I mean, what, I mean, whether he should start a new semiconductor company or something else or whatever. But anyway, after him convincing me for a good while, I also resigned my new job and joined him. And we got a couple of other guys as well on the team and basically said that, okay, let's do it. And really, we had set ourselves some quite high goals, but we didn't really know how to achieve them. I mean, not in any level of detail. Sure. Yeah. We just thought that we'll find a way.
Dave Jones: So did you actually have the idea before you quit your job? Like, did you have the idea that you'd do low power energy micro, you know, these low power arm devices? Or did you just go, let's do a chip startup and figure it out what chips you'd do later? How did that work?
Evin Yanbu: So when we did the, I think from the Chippicon days, we had a lot of experience with making radio transceivers and also some of them with embedded MCUs. And certainly when ARM started getting traction with their new Cortex-M series, Cortex-M3 at the time, we saw this as a perfect fit, right? And there weren't many licensees at the time that we were doing this, only a couple. And then basically we figured, we had a very clear mindset for doing Cortex-M3. There were some alternatives that we also considered, but I think more from a financial point, just to have an alternative rather than there was actually a real technical alternative. Also, I think the traction that Cortex-M series has seen in the market lately, I mean, it's given us a lot of advantages rather than, say, doing our own core or going a completely different direction. For sure.
Dave Jones: Was ARM your first and only choice or did you consider something else? And why did you pick ARM? Is it because you had experience in it or because you knew it was going to be the future of cores?
Evin Yanbu: I think it was both that we had a very good feeling for what they'd done. They had the exact right focus that we were trying to do as well. I mean, focusing on reducing both size, of course, and the power consumption. And it was basically a perfect fit. But we did have another alternative. We did also talk to MIPS at the time.
Dave Jones: Okay. Yep. Which Arizona, which Hycrochip ended up using MIPS as their architecture for the PIC-32s. They decided not to go with ARM because everyone else was doing ARM, so they wanted to be different and chose MIPS. So whether or not that will pay off, I don't know.
Chris Gammell: Yeah. It makes you wonder if there is – I mean, is there an advantage to being kind of like the run-with crowd or do you try and just kind of eat out the others?
Evin Yanbu: I think there's a huge advantage to run-with the crowd in this case at least. Right. Okay. I think if you go with MIPS, which I mean, I don't want to say anything bad about MIPS either because the solution, I think, is technically good and everything. But what you end up these days, I think, is to basically spend most of your customer meeting convincing people why MIPS is as good as ARM. Rather than saying, okay, we have ARM. Okay, it's good. So let's talk about everything else. Yeah.
Dave Jones: It makes getting those sales a lot easier, which is important for a chip startup. I mean, that would be a huge deal.
Evin Yanbu: If you look at, say, the whole ecosystem of tools and middleware and everything, then you start to really gain a lot of advantages from choosing ARM rather than something which may be as good but not as well supported. Got it.
Chris Gammell: Yeah. I kind of had that same experience with ARM. With ARM, I was kind of – all these vendors keep coming in and talking to me and saying, oh, we have an ARM chip now. And I'm like, okay, you and everybody else is brother. But the thing is, once you do switch over, you're like, okay, well, now I can go to anyone, right? And you can actually pick the best peripherals you need, the best powers consumption in your case, right? So it's an interesting strategic decision. And obviously, ARM has been benefiting from it. I mean, I guess my inner Dave, I guess it is, was like, oh, no, what if they shut down tomorrow and ARM's no longer available? And I'm a conspiracy theorist with that. But really, that's just not – I don't think that's realistic. No, it's not – And if there is – yeah, I mean, there's already the IP out there.
Dave Jones: Well, it's just the IP, really. That's all it is. And you make your own chips from that. So you decided to do this startup. Where did the money come from? Did you have any money at the start? Did you throw your own money in? I know you got $13 million in venture capital funding from a firm. But how long did that take?
Evin Yanbu: Yeah, so if we go back again – so we basically decided to found the company and to give it a go. And I think we were about eight, nine employees at the time when basically we started really working, which was beginning of 2008, around January. And at that time, we had invested basically only our own money. I mean, a lot of it coming then from the acquisition. Of ChipCon. Yeah. Yeah. Of course. I mean, also to a big majority, it's our CEO who has the big money coming in. Checkbook. Yep. Yes. So we've had a few rounds. But actually, we managed without VC money for the first few years. Excellent. Which also, of course, made it possible for us to get a better pricing for the company once we did get the visas in. So still, we have gotten some VC money, which is true, from two different Norwegian VC companies.
Dave Jones: Right.
Evin Yanbu: But we still have a good majority of the shares sitting inside the employees.
Dave Jones: So you sort of implied there that the longer you wait, the more you spend your own money and build up the company, the more you will get in venture capital funding later on? Is that –
Evin Yanbu: Well, no. But I mean, the better pricing you will get. So if they give you a certain sum of money, right, they will get a smaller share.
Dave Jones: Oh, they'll get a smaller percentage, right. Yes, exactly. They'll get 10% instead of 50%.
Evin Yanbu: Yeah.
Dave Jones: Right. Okay. Got it.
Evin Yanbu: Because you can justify that the company is actually, I mean, something that will live for a good while and will actually be able to make the products that you have on PowerPoint.
Dave Jones: Right.
Evin Yanbu: Yeah. Yeah.
Chris Gammell: It's not all concept drawings. It's actual drawings, right? Yeah. Or in your case, it's schematics and chips. Or even real chips.
Evin Yanbu: Yeah.
Dave Jones: So you started in 2009 technically – sorry, 2007 technically, and you were ramping up in 2008, but you didn't release your first product until 2009. That's true. So is that like that 18-month to two-year development, is that normal for developing your first chip as a chip startup?
Evin Yanbu: I don't think it's normal. I would say it's actually faster than normal. Oh, okay. At least if you count – so we did start in 2008 in January. I think in like April or May, we actually got some servers and we actually got some design software. Okay. And basically, roughly a year later, we taped out the chip and that involved – I mean, we did get some IP, of course, from ARM, like the Cortex. And also things like RAM and flash is typically IP. But absolutely everything on the analog side is designed from scratch by ourselves. There's no IP. There's not even like the pads are IP because there isn't anything that actually fits all the requirements that we had.
Dave Jones: Right. So how much of the chip would – what percentage of the chip would be the ARM core and what percentage would be the low-power peripherals and other things around it?
Evin Yanbu: That's a good question. I think – I don't have the numbers on top of my head, but the ARM core is a relatively small part of the chip area in total. Okay. Well, depending on which chip, of course, you're talking about. But if we go back to the first chip family, I think it's – I mean, if it's 10% or if it's 20%, I would have – Right, but it's fairly small. But anyway, it's not – there's no like 50%. I mean, things that typically dominate these chips are still memory, like flash. Right. Right. Of course, yeah. Yeah. And also, of course, all the different peripherals and analog and – so, yeah.
Chris Gammell: So that first day, I mean, like – so when you guys actually start to sit down and you have these, you know, EDA tools in front of you, is it just like, well, let's get making some op-ans.
Evin Yanbu: Time to make the donuts. Yes, it is almost. I mean, we did start, of course, getting like bullet point specifications. But I think we're less formalistic than if you move to a bigger company where everything has to go through all the formal reviews and everything.
Evin Yanbu: Yeah. Or like, okay, let's just do it. Let's make some cool stuff. Yeah. That kind of mentality. Yeah, exactly. So less formal. But still with, of course, a very – I mean, quality is everything still, right? So we didn't take any shortcuts when it comes to verification and making sure stuff works. Right. That's good. So making FPGA prototypes and, yeah, doing what we needed to do.
Dave Jones: Okay. So you actually did prototyping in FPGA. So you didn't go from just simulation and verification in software straight to the first actual chip.
Evin Yanbu: No, I think I would be surprised if anyone doesn't make FPGA prototype if you're going to make this kind of complexity. Because, I mean, for sure, in a simulation environment, you will be able to find a lot of bugs. You will be able to verify a lot. But you're still restricted by at least a couple of things. I mean, one is runtime. That once you get to a certain level, I mean, if you want to really stress test things, then, I mean, you want to loop things forever and ever. Yeah. And so making FPGA that can run either really at the speed, which is going to be live later on or at least close to it, is a huge advantage when it comes to simulation time.
Dave Jones: But that's only going to allow you to test your digital parts. How do you prototype your analog sections, all the low power stuff and your analog peripherals and your power shutdowns and things like that?
Evin Yanbu: Yeah. It's kind of challenging. But some of it, we actually also have prototyped in the FPGA. Others, then we rely on the simulation environment to verify those. Right.
Dave Jones: Okay.
Evin Yanbu: But for sure, it's possible to make analog models or digital models of analog circuitry in FPGA if you want to.
Dave Jones: Fair enough.
Evin Yanbu: Yeah.
Chris Gammell: So do you have input from – so you said you had quality up front and everything like that. But another big concern I would think would be the actual process nodes and working with fabs and stuff like that because you eventually have to imagine that the stuff will be made. Even at a startup, I'm sure the focus is on getting the hardware in there. And so did you already have an agreement in place with a foundry or did you just – you just knew that we're going to be on this process node and there's these constraints and there's six or seven foundries that can do this stuff. How did that whole thing work?
Evin Yanbu: Yeah. No. The foundry node is certainly very important. And we are working with TSMC in Taiwan. Okay. Which is – you probably know it. I mean, it's basically the biggest – It's the biggest.
Evin Yanbu: It's the biggest. It's the monster. And certainly there are alternatives. But we had worked with TSMC before and it's a big advantage to both be able to take advantage of the relationship that you have. And they know you and you know them. And also, I mean, to give them credit, TSMC, they're the biggest for many reasons. But they're the biggest also because they're really good at what they do and they are – I mean, you can trust them basically.
Chris Gammell: Right. Yeah. I mentioned last week's show about Intel and I used to be in the semiconductor industry and how the equipment vendors would talk about Intel. Well, the other ones they were talking about was TSMC. It's like, oh, those guys. I mean, they would thump on them and they'd make sure that they were getting the best process equipment. They were leading the nodes basically. I mean, it really is Intel and TSMC that are leading that stuff.
Evin Yanbu: Yeah.
Chris Gammell: Yeah. That is a nice advantage.
Dave Jones: How easy would it be to pick up and move from TSMC to someone else if you had to? Let's say TSMC couldn't actually deliver because they're producing 10 billion chips for Apple and you really need parts. How easy and how fast could you move to another foundry if you had to?
Evin Yanbu: Well, it's not trivial at least. So, it would depend on at least how compatible the processes were and probably it would be similar to a new chip design. Of course, saving some that you just don't want it to do the same as you've done before. But they probably have to re-simulate a lot of the analog in particular and perhaps even do a complete redesign depending on the differences.
Dave Jones: Ouch.
Evin Yanbu: Yeah. So, it's quite challenging. So, you're kind of stuck. Right. But let's say if you wanted to and if we had to, I would just guess that it would take us like up to half a year probably to do it.
Chris Gammell: Wow, to move. So, it's like if there's a supply problem or something like that, it's like, no, we can't just – you kind of hitch your wagon to TSMC at that point and you're just – you have to kind of work through it with them and stuff like that. Typically, yeah. Yeah.
Evin Yanbu: Of course, you could invest these kind of things up front, right, having a dual supply. But I think almost no one does that anymore. All right. I mean, people used to do that for, say, analog chips, right, before. Yep. And some even said that this was a must. But I think if you look at the digital chips today or processors, I mean, I may be wrong, but I don't think anyone does it anymore. Got it. It's too costly and it's too hard to actually get compatible processes. I mean, of course, inside TSMC, for instance, they do have different fabs that can manufacture the same stuff. Right. So if there's an earthquake or a fire in one place, you may still be able to at least manufacture a percentage of what you had going to the other factory. Yeah. That's a good scale thing, right?
Dave Jones: Yeah. What is your strategy with actually when you manufacture these chips? Is it you manufacture probably just enough to satisfy your current demand and a little bit of stock? Or do you go, right, well, we've got a run schedule. We're going to do, you know, 10 times more chips than what we have orders for. Do you keep a lot of stock or what's the strategy?
Evin Yanbu: Oh, I think I'm not sure how much of this is public or not. Oh, okay. But I could give you a little bit of an answer. Sure. So lead time, as seen by our customers, is extremely important.
Dave Jones: Of course. Yeah. That can make or break a deal.
Evin Yanbu: Yes. And, I mean, depending on the semiconductor cycle, right, in periods, big manufacturers have like half a year lead time, which is killing customers, right? Yep. I mean, they don't know what to do.
Dave Jones: Both myself and Chris have been caught up in that before. Yes. Almost every designer has.
Speaker ?: Yeah.
Evin Yanbu: And so basically lead time is one of the really important factors for us, right? If we have a really high lead time, then this will be an argument for not choosing Energy Micro. Of course. So we do focus on low lead time, and even the lead time is less than the manufacturing time in the silicon fab. Right. Which means that we are actually manufacturing up front based on… Sales projections. Forecasts. Forecasts, yeah. To some degree, of course. Of course. And then depending on… Also, of course, we have different package options and so forth. I mean, after the wafer fab, we have to go through test and assembly. Oh, yeah. Perhaps also the wafer testing and assembly and final test. And it's quite complex, right, with the number of products that we actually have. Yeah. And different variants on memory configurations and everything. So it's a bit of a challenge, but we have a big focus on lead time, which basically means that we have to be a little bit forward leaning when it comes to manufacturing. Sure.
Dave Jones: With the… I mean, you differentiate yourself by having super low power 32-bit processors. Are they the lowest in the industry or do you have competitors in that sort of low power ARM core market? Yeah.
Evin Yanbu: Yeah. So certainly we have. I mean, it would be a bit stupid of me to say that we don't have competitors.
Dave Jones: And who would they be? Who would be your main competitors? You think, probably.
Evin Yanbu: Well, I think probably our main competitor, if I was to mention one, it would be ST.
Dave Jones: Right.
Evin Yanbu: Yeah.
Dave Jones: Okay.
Chris Gammell: Gotcha.
Dave Jones: I haven't looked at the ST ARM processors.
Evin Yanbu: No, I mean, they have a lot of different versions. And some of them are low power and some of them are not. But I think, of course, the cortex itself is important. And I mean, say, a lot of people, including ourselves, mentioned like microamps per megahertz or some benchmarks saying current consumption or energy consumption or something per frequency. Or whatever. Yeah. But in a lot of cases, that's not where the battery's energy goes, right?
Dave Jones: It'll be in sleep mode or something. It'll be in sleep mode. Power down idle, real-time clock running in the background.
Evin Yanbu: Yes. Yeah. I mean, whether or not you have this. Like, for instance, we have a low board rate serial port that can actually be active in a one microamp current consumption and move data via DMA, etc. I've seen that. While you're actually in this extreme low power rate.
Speaker ?: It's pretty remarkable.
Evin Yanbu: So how much battery do you save by that? Well, of course, it depends on the application, right? Of course. But if you actually have the use for this, then it could save you a thousand times. I mean, if you don't, then, of course, it's not going to save you anything. Exactly.
Dave Jones: I mean, I've seen you've got a chip. Sorry. You've got a chip there that actually – well, one of your modes is that you can do direct memory transfer from an analog to digital converter straight to the memory without even using the – without even powering up the ARM core. Yeah. Is that right? I mean, that's a complete data logger right there without actually running your processor.
Evin Yanbu: So – Actually, we have something called Le Sense, which is low energy sense. Yeah. Oh.
Chris Gammell: It's not like a French version of sensing.
Evin Yanbu: No, but actually, that's where the name came from. It came up with a joke. Like, you know, in – what's that – in Pulp Fiction, we have the Le Big Back, right? Oh, yeah. We have the Le Sense. Royale with cheese. Yes. But actually, the name just kind of stuck. Nice. That's awesome. And probably no one knows – See, that's the kind of mythology we like hearing about. That's awesome. So – and actually, you can do, like, sensor excitation and measurement and, like, do touch sensing with about a microamp per button, even with a good response time.
Dave Jones: Wow.
Evin Yanbu: That's awesome.
Dave Jones: And that's all without using the processor, you know.
Evin Yanbu: It's all without using the processor, yeah. Fantastic. What we've seen is that, I mean, every time that we do something – of course, we, as everyone else, also look at our competitors, right? Okay, so what did this competitor think of this time? Or what does our customers tell us that our competitors does, which is, say, a good idea? Of course, we also do that. But I think that a lot of times when we've seen that there's something that came up with ourselves, right? That we actually made something that we didn't hear about before. We just thought this would be a great idea. That's when we really make a difference. And that's where we can really, say, make a big difference when it comes to the customer needs, right? And to really solve – perhaps even solve the issues that the customers didn't know that they had or actually didn't know how to solve.
Chris Gammell: Yeah, it's like revolutionary versus evolutionary innovation, right? Yeah. That's like the buzzword bingo right there. Yeah. Yeah. That's great. That's really cool. I mean, that's –
Evin Yanbu: So I think these kind of peripherals and power modes, those are actually, I mean, really killer features. So certainly the Cortex-M3 and what it can do and, I mean, high processing power versus low power consumption and ease of use and everything is great. But I think the main differentiator that makes our customers select energy micro is still – I think this first point is just something they need. And then the additional point is the stuff that makes us be selected.
Dave Jones: Right. So I've got a question from Heinrich here. What is it like running a semiconductor company from Norway? Is it hard sourcing expertise, people? And have you considered – did you ever consider moving to Silicon Valley where the action is in quote marks? Yeah. Yeah.
Evin Yanbu: Well, I think – well, first of all, actually, Norway has a fairly good semiconductor industry. I mean, fairly good meaning there's a reasonable amount of companies, meaning that there's a reasonable amount of experienced people and also education-wise. So, I mean, we do have challenges hiring the right people and we don't just have – sometimes we're not able to hire, I mean, even though we need people. But in reality, right, we have, of course, NG Micro and we have the old, say, ChipCon team, which is also a good-sized team in Oslo. And in Trondheim, you have Nordic Semiconductor that you might know of. Yeah. And also the part of ARM that designs their graphics course is in Trondheim. Oh, interesting. Right. And there's also a division of Omnivision, previously Photobit, located in Oslo. And, of course, not to forget the Atmo. So all the AVR controllers are designed in Trondheim.
Dave Jones: Oh. Interesting. I didn't know that.
Evin Yanbu: And also the AVR32 controllers. And I think even the manager for the whole micro-troller division of Apple is in Trondheim, or at least he's from there. So actually the semiconductor industry in Norway has been growing a lot. And could I actually – could I tell you my boss's favorite joke? Of course. Ah, thanks. So it's – he typically tells this in customer visits. I mean, so Norway is, of course – or not of course, but it is a fairly rich country. And the reason for this is because of the oil, right? Like, we have had oil pumped up since the 70s, right? And it's produced a lot of money for us. And the second largest export part is fish. Right. So – but actually, I mean, it's clear that the oil is going to go away, right? Because it's – The hit peak oil and all that sort of stuff. And then Norway is just going to export fish and chips.
Dave Jones: Ah! Yes. That's a good one. Yes. Very good. I like it. I'll pay that one.
Evin Yanbu: Yeah. So – but to answer the question, I think also, I mean, Norwegians, we do love our country and enjoy being in Norway, which is a – I mean, it's a fantastic country to live in, as long as you don't care about the weather, at least. Right.
Chris Gammell: So, yes, there's a song by one of my favorite groups called Of Montreal. They have a song called Oslo in the Summertime. And it's a – it's an interesting song. Yeah, exactly.
Evin Yanbu: Yeah. Oh, boy. Yeah, it's not necessarily stable, at least. Right. But – so, I think Norway is a good place to be for a semiconductor company. I mean, the costs of having an engineer in Norway is actually lower than the costs of having an engineer in Silicon Valley. Right. So, living costs – That makes sense, yeah. Yeah. So, Norway is an expensive country, but we're a social democracy. So, I mean, people with low wages still earn more than in Silicon Valley, of course. I mean, working at McDonald's isn't so much lower than being an engineer at Engine Micro.
Dave Jones: Oh, really? Interesting.
Evin Yanbu: I mean, there's certainly a difference, but – Right, right. Right. Yeah, of course.
Dave Jones: Yeah. Yeah. Right.
Evin Yanbu: Interesting. Interesting. Wow.
Dave Jones: We've got a question from Eric. Can you tell us more about your radio system on chip stuff? Yeah, I was wondering about this too. Yeah, because you not only do – you do two products, effectively. You do the Gecko microcontrollers and you do these radio devices.
Evin Yanbu: Yeah, that's true. So, we call this EFR. So, it's called Energy Friendly Radio. Yeah. And we have a family coming – or actually, it's multiple families of radios coming this year. Okay.
Dave Jones: So, they're not actually out yet? They're in beta silicon?
Evin Yanbu: They're not in the market yet.
Dave Jones: Right.
Evin Yanbu: But it's quite actually a flexible family. I mean, both when it comes to support for different frequency bands. I mean, both for 2.4 GHz and a lot of sub-GHz frequency bands.
Dave Jones: Yep.
Evin Yanbu: And also, a lot of different radio communication protocols like 802.15.4, I mean, the IEEE standard. And Bluetooth LE and wireless MBUS and the sub-GHz range. And, well, it's a lot of different standards. So, basically, what we did was to try to leverage on the experience that we had from – both from ChipCon and from other companies. I mean, trying to avoid that you have to make a new radio every time there's a new standard coming.
Dave Jones: Yep.
Evin Yanbu: Right. Trying to make it flexible enough from the first generation that you can still make it – I mean, there's never going to be something called forward compatible, I mean, in real life. But at least we try. Yeah. We try.
Dave Jones: So, how do these compare in terms of energy consumption to, say, Bluetooth LE? Is it in that league or is it down compatible to Ant? The Ant, you know, is it super low power like that or?
Evin Yanbu: It's going to be – or it is really super low power, yeah. So, we want to really benchmark against the best. And I don't think there's any point coming out to the market with something which is just a little bit better than what's already out there.
Dave Jones: Sure.
Evin Yanbu: So, certainly, we will be making a major step down in energy consumption.
Dave Jones: So, who would be your major – who would you be targeting there? Would you be targeting Ant? Because I think they're probably the lowest power RF at the moment on the market, are they?
Evin Yanbu: Well, I think Ant has a good traction in certain markets, right? For like your heart rate monitors. Heart rate monitors, yep. And your watches and things like that. Yeah, typically. I think there's – and then there's tons of protocols for various both applications and user scenarios. But, I mean, Ant's definitely one of the good standards when it comes to providing a low power solution. I mean, a real life low power solution. Yep. I think Bluetooth LE – I mean, I would – I think whether or not Bluetooth LE is lower power than Ant or the other way around. Oh, I don't think it is. I don't think it's even twice. Well, I think it's more about the silicon implementation than – and on the configuration of everything. Because even Bluetooth LE isn't just one thing. It's a configurable standard where you can set this hook or you can – depending on, for instance, like latency. Like your heart rate monitor, it doesn't need to – you don't need – you want it real life but not – I mean – Not instantly, right?
Dave Jones: Yeah, you only need to transmit a couple of times a second or something, you know.
Evin Yanbu: Yeah, or perhaps even slower. Yeah. So I don't think there's a single answer to this. I think that's probably more of what people will believe than what is actually real life. And of course, even Bluetooth LE is still quite early days, right? There are very few products on the market. And I think there's going to be a big change also. I mean, also when, of course, we come onto the market with our solutions for this.
Chris Gammell: So do you see – I mean, so first off, it's definitely not core-based. Because you're not buying these cores then, right? I mean, you're actually doing the silicon design?
Evin Yanbu: Yes, yes. Okay.
Chris Gammell: So, I mean, do you see the same kind of thing happening that happened with ARM cores and other – I mean, because before, if some of our listeners don't know, I mean, there were many cores and a lot of people were rolling their own. But now everyone's kind of coalescing around ARM and these bigger solutions. Do you think the same kind of thing will happen with RF solutions and more standardized silicon eventually?
Evin Yanbu: I don't think it's going to happen with standardized silicon when it comes to RF. No, I don't think so. Okay. But I do think that RF communication standards are going to – I mean, there are very many out there. And I think that not all of them will be, I mean, around forever and ever. I mean, I don't know which ones are going to be really successful and which ones are going to, say, die slowly. But for sure, I think having standard-based solutions is going to be key to be successful in this market in RF communication. Yeah.
Dave Jones: We've got a question from George Hahn, and he asked, what influenced your decision to release so much software as open source? I mean, how much of your software as open source and have you benefited or do you expect big benefits from doing that?
Evin Yanbu: One of our four company core values is simplicity. And actually, we're probably the only company in the world that has a VP of simplicity.
Chris Gammell: Right. I did see that on your site. Really? I was wondering about that. I was wondering if that was just a typo or what that was.
Dave Jones: So is his job really simple? Does he actually sit there and go, I don't have to do much because I'm the vice president of simplicity?
Evin Yanbu: But his task is to make it simple for our users and the customers. Got it. So we're not trying to make it easy for ourselves necessarily. Right. So basically, releasing our driver libraries, et cetera, as open source is part of just making it simple, right? I think it's not that uncommon either.
Dave Jones: No, it's not.
Evin Yanbu: But I think it's just something you should do just to make it simple. And also, we've recently changed the licensing scheme of this to just make it more simple and less, say, restrictive for our users. And perhaps we even do more over time.
Dave Jones: Because Eric Smith had a question about this. So it's a rather complex multi-part question. But he talked about GPL and how that can be an issue. GPL license can be a problem for some customers and things like that.
Evin Yanbu: Yeah. And I think he asked whether or not it would be possible with a dual license, right?
Dave Jones: Yes. That's right.
Evin Yanbu: So, yeah. That's actually something we – I mean, I forwarded that question to our VP of Simplicity. And he said, yeah, that's a good point and we should probably take a discussion on it. But it's something we should definitely consider to do. I can't promise that we'll do it right here and now. We should discuss it. But in general, we want to just make it simple for our customers to go with our solutions. And, of course, we won't be making our money based on the software, right? The software is – Of course. Only indirectly, of course, since the software is key to people actually selecting our parts.
Dave Jones: That's correct.
Chris Gammell: Right. Making it easy to pull into your ecosystem is very important.
Dave Jones: Because I've seen other companies get caught out with this microchip and I think Atmel as well. But microchip specifically, they claim that all this stuff is open source and everything. But if you read the licenses like the USB library or the Ethernet library might not be because it's based on something else that's actually proprietary. So you develop your project around all their nice libraries for USB and Ethernet and everything else. And then you find, oops, I can't use the Ethernet because it's actually proprietary. Oops.
Chris Gammell: That door's shut. Yeah.
Dave Jones: And that can come and bite you as a designer later on. Yeah. So, you know, that's – Sure. Hmm.
Chris Gammell: Yeah. And that's a really interesting focus, the whole simplicity thing. I mean, I think a lot of companies talk about that but I don't think it's in there. None of them have a VP about that. So that's pretty cool.
Speaker ?: Right.
Chris Gammell: Yeah. What about – so from the software side, you know, some of the people in our comment section asking questions were mentioning like communities and, you know, getting help with software and stuff like that. Obviously, a small company can't just directly answer questions. But, I mean, are there resources out there? So if our users wanted to try out a chip and they wanted to, you know, talk to others about getting up and running, is there a resource for that kind of thing or even just a starting point on your site? Yeah.
Evin Yanbu: Yeah. I mean, we do have a website on support.ngmicro.com where you can actually just submit your questions and you'll get an answer. But we are going to set up a forum as well but I'm not sure about what the timing of this will be. But we certainly have discussed this internally as well. And, again, it's part of making it easier. So I think it's a good point and something we should definitely be doing.
Chris Gammell: Okay. So maybe an enterprising engineer or hobbyist out there could start up an easy site for now and then it will get pulled in later.
Evin Yanbu: Yeah. Actually, even there are some localized support forums. But typically, like in China or in Germany, there are some pages that are set up for EFM support. But probably not worldwide. Okay. Got it.
Dave Jones: I've got a question on the ARM core. I don't expect you to answer directly or know the figures. But how much of the final chip cost roughly would be the license fee for the ARM core? Is it a big percentage or is it like a small percentage compared to actually manufacturing the chip plus profit and everything else? Yeah.
Evin Yanbu: It is, of course.
Dave Jones: I'm sure it's very proprietary how much license fee you...
Evin Yanbu: And it's very confidential. So I can't really answer. Right. Oh, yeah. I can't really answer. Sorry.
Chris Gammell: I do know that on ARM's site, they talk about... I've seen presentations before because I was looking at investing in ARM at one point. But I have seen stuff and people can go look at that. Maybe that's a better place for people to go look at it. Probably. But it's pretty low. I mean, I think in general, it's a lot lower. I was very shocked. It was fractions of pennies for chips, at least when I saw it. Okay. Interesting. I'm sure there's a big NRE cost and everything else. But it is an interesting model. I mean, what's it like working with them? I mean, when you guys were starting up, did you guys get like a catalog and were you like... No. We'll take that one. It actually was kind of hard.
Evin Yanbu: It was kind of hard to really get in touch with them even, right? Really? Right. Because we were no one. And who do you call? Right. Ghostbusters. Yeah. Who do you call? ARM wasn't, at least at the time, set up to cover a broad market, right? They have a relatively limited amount of both customers and potential customers. Right. So it's not like they have a lot of contact points. But we were able to basically get in touch with the right people. I think we had to go through some back doors to find out who we're supposed to be talking to.
Chris Gammell: Yeah. And that's got to be a tough proposition too. I mean, you approach a company being like, we'd like to buy all of your source code, please. You know, that's basically what a core is, right? It's like source code and pulling it in. Yeah.
Evin Yanbu: But, I mean, ARM has been fantastic to us and really supported us. And so we've had a great relationship with them. So, I mean, after we got the right person in contact there and they came over for a meeting to Oslo like a couple of weeks later. And since then, we've been working quite closely with them. So they've been great to us.
Dave Jones: So what does the code come in? Is it VHDL? Verilog? It's Verilog.
Evin Yanbu: It's Verilog. Right.
Dave Jones: Okay. And have you modified that or do you just don't touch the ARM core? Did you find that you needed to modify it for some reason?
Evin Yanbu: We have had reasons where we have had wanted to, from a technical perspective, to modify things. Got it. I mean, typically then in some very low details or like to allow some clock gating or something. But we're not allowed to.
Dave Jones: Oh, right. You're not allowed to or it's just too dangerous and silly to do that? Not allowed. You're not allowed to. Okay. Not allowed.
Chris Gammell: How would they know? Come on. They sound like you're on a radio show talking about it.
Dave Jones: And how do you actually design these chips? What EDA tools do you actually use?
Evin Yanbu: So we're using cadence tools. Right. So, I mean, they basically have a tool for everything, right? Of course. Yep.
Dave Jones: At very high prices. Yes.
Evin Yanbu: At a quite high price, yeah. Yeah. But actually, they've also been, I mean, I have to say quite good to us. And they've also been, they also have like special programs to support startups. And they understand that you can't have, you can't pay. Yeah. And they have some, say, models where you can, yeah. Anyway.
Dave Jones: Sort of, you can use now and pay later maybe.
Evin Yanbu: Well, at least payment terms is certainly one thing. It's flexible. Right. It's possible to talk to them about.
Dave Jones: If you're a low-cost startup.
Evin Yanbu: Yeah. Yeah. So we're using cadence tools all over. But of course, there's a lot of scripting involved, a lot of stuff that we have made around this ourselves as well.
Chris Gammell: Got it. What about future stuff? I mean, we had a question on here about, what did the person ask? Jean-Luc asks about, do you plan to use the new ARM Cortex M0 Plus core in your next generation MCUs? And just kind of, for me, would be what is the future beyond radios and everything else? I mean, do you guys have a roadmap that you're allowed to talk about? Or is there, you know, what's next?
Evin Yanbu: Yeah. So to answer the specific question, we're going to use the M0 Plus in our Siri Echo family. I mean, this is the latest, say, upgrade of the M0 from ARM. Beyond this, of course, we have a lot of products coming on the radio side. And we have a lot of, I mean, it's fairly obvious that we're going to be expanding both the number of microcontroller parts and radio parts in the years to come. Of course, with variations on peripherals and, well, everything. Beyond this, actually, we had a very interesting internal process going on last spring, I think it was, where the whole company was encouraged to come up with these kind of ideas. What should be next? Oh, excellent. And we had a lot of, say, crazy ideas and a lot of, say, small ideas and incremental features. And, I mean, it was really, really interesting to see all the things people were thinking about. I mean, from, say, energy harvesting to, well, battery technology to, yeah. But I think we do not have a public roadmap going beyond microcontrollers and radios. And it's probably at least going to take a little while. But I would say it's quite likely there's more stuff coming from Energy Micro in the future as well. Excellent.
Chris Gammell: I wouldn't expect any less. I mean, only all these processors and all these radios in, what, a couple of years? Jeez. I mean, yeah.
Dave Jones: Well, that raises the question I wanted to ask. Once you've designed your first device, like it took you like 18 months, two years to get your first one out, how easy is it to then produce variations of that, you know, the tiny gecko and other variations of the gecko family?
Evin Yanbu: Yeah. So, like the tiny gecko, there was a certain amount of new functionality. But, of course, the rest is a variation, like you say. Yeah. And the whole design flow that we made from the beginning was targeted at making it easy to make these variations. So, we have like a chip description format, kind of similar to XML, where we can describe a chip, like how many URs, memory maps. Run a script. And in theory, out of pops, yes.
Dave Jones: Right. Oh, excellent.
Evin Yanbu: But, of course, there's more to it, right? Of course. And not only out pops the RTL code, but the documentation and everything. Fantastic.
Dave Jones: Because a lot of, I mean, if you look at microchip or somebody like that, they've got like how many thousands of different devices do they have? I mean, it almost borders on crazy. Are you planning on having lots of variations or do you think it's better just to have, you know, just a couple and that's it? And, you know, even if it's not tailored to your individual application, it's better to have just a few for support, easier support.
Evin Yanbu: Yeah. I think it's necessary to have a relatively large amount of variants. Yeah. Okay. Right. I think it's necessary. I mean, both because, I mean, sometimes we have this discussion internally, right? Should we or should we not make this kind of variant, right? Yep. And sometimes we say that, okay, no, let's not make it because, I mean, we have this other variant. It has more. But so it's still going to satisfy the customers. And then like a couple of weeks later, there's an email from the sales guy. He's been to this and this customer visit, right? And they asked, why did you not make this part? Right. Of course. Of course. I think it's quite typically human as well, right? We don't want to pay for something we don't use.
Dave Jones: You don't use. Yeah, exactly.
Evin Yanbu: Because we feel cheated, right? Or whatever.
Dave Jones: But how hard is it to support, you know, hundreds of devices or whatever? I can imagine it'd be a nightmare.
Evin Yanbu: It is quite hard, actually, to be honest. Yeah. But at least it's not trivial. But as long as we build the right systems around it, it's definitely something we were able to do without sacrificing on quality or…
Dave Jones: Got it.
Evin Yanbu: Yeah.
Dave Jones: Because that's, as a designer, that's often a scary thing. Oh, you know, Atmel come out with a new variant or Microchip come out with a new variant or Energy Micro come out with a new variant. And it hasn't, you know, it doesn't have trust, you know, because you haven't used it before. Are there silicon bugs in it, you know? I'm very squeamish about that kind of thing. And some of the major ones are filled with silicon bugs, you know? It's not unusual for whole things in the chip not to work. Yeah.
Chris Gammell: The errata sheet is a very scary thing, right?
Evin Yanbu: It's crazy. Yeah. So, of course, that's a challenge. But it's something we just have to deal with and make sure that we… I mean, if we have bugs, that at least they're described and being fixed. Got it. Yeah.
Chris Gammell: Yep. So, another thing that always scares me and actually something you guys address right on your website is longevity, especially with like a startup. Yes. You don't know… I don't know if you guys are going to be around tomorrow, right? I mean, no offense, I mean, but, you know, your history is only so long, right? Yeah. So, that's interesting, though, that, you know, you put guarantees on here, which is a big thing. We talked to Tom Lomens from the auto industry and he was talking about 10-year lifetimes. Yeah. And so, yeah, it's an interesting thing. Can you tell us a little more about the longevity stuff?
Evin Yanbu: Yeah. So, I mean, the reason why we made this and the reason why we put it on the webpage is just to put this question to rest because it's typically something that comes from at least industrial-style stuff. Oh, yeah. You bet.
Dave Jones: I've asked it myself. And it's often next to impossible to get them to give it to you in writing because I've worked in, you know, military industries and other industries that we need this sort of stuff in writing. And it's like extracting teeth from them. It's next to impossible. But you guys have put it right out there on your webpage. We'll support these chips for 10 years.
Evin Yanbu: Yeah.
Dave Jones: It's great.
Chris Gammell: Simplicity. I'm printing this out right now. Okay. Well, there you go. This is a legally binding document now. Legally binding HTML. It's being indexed by Google. Yeah. That's interesting. It's good, though. It's a good sign. I mean, it's long-term thinking, all that kind of stuff is very important for silicon because it is such a big investment, not just from your side, but also from a design side. If I'm deciding, well, I'm going to put an energy micro into my design. I don't know how long my product is going to last, but I can be damn sure that if I'm making it in 10 years, I'm going to be wanting to use the same chip. That's a very important thing to me.
Evin Yanbu: And like if you move into industrial or medical applications, you may have to run through a whole new cycle of governmental approval or FDA approval. You can't just replace a part without going through this cycle again. I know.
Chris Gammell: It's very expensive and it takes a long time.
Evin Yanbu: Yeah. Yeah.
Chris Gammell: Well, speaking of simplicity, I was thinking about how I had found out about you guys. It was actually through DigiKey and just the whole – you know, a lot of people find new stuff that way, right? I mean, you're looking for maybe low cost or low power. You're doing like a parametric search and you're like, who the heck are these guys, right? No offense. No, no. And so I'm just wondering, though, like is that how you guys find a lot of new business? How does that whole thing work with getting set up with those guys too? Because, I mean, at least for the hobbyist side of things, a lot of our listeners are even smaller producers of hardware, like in a professional capacity. That is the first step is going straight to distribution, seeing what's available today and seeing, you know, what kind of parts I can get.
Evin Yanbu: Yeah. So actually, I mean, we've been working almost from day one with distribution and making a good setup there. I mean, worldwide. So actually, we started signing up distributors, I think also back in 2007 before we had any products. Nice. Also to be able to, I mean, get the relations with their customers to make sure that we address the right customer needs, right? And make sure that we make the products that people want. And then going to, I mean, to like DigiKey or Mouser has been important for us as well. To make it easy for people to get samples or to just get a few parts without a big hassle. So it's very important for us to, I think, both to be able to support the kind of hobbyists or students or people who just want to play with stuff and, I mean, have fun. And, of course, I mean, realistically, we're going to make the majority of our money on companies that are medium to large. Right. But still a fair amount of our revenue will likely come from the smaller customers because there are more of them. And, of course, we're very happy to, I mean, get into small designs as well as the big designs. And the more people, I mean, you probably know more about this than I do, but the way Microchip was able to grow from basically nothing to a lot was basically to be able to spread the technology widely.
Dave Jones: It was, yes, the hobbyist market. They were the first low-cost, easy-to-get micro. Yeah. And that's what cemented their position.
Evin Yanbu: Yeah. And Motorola at the time, they didn't care.
Dave Jones: No, that's right.
Evin Yanbu: And then they lost.
Speaker ?: Yeah, that's right.
Dave Jones: Big time.
Evin Yanbu: Yeah. Yeah. So, of course, we're inspired by their thinking and the way they've been able to build their business. So, we want to be able to support this in a good way. And then, like you say, DigiKey and their likes like Mouser or others are extremely important.
Dave Jones: And from a designer point of view, as Chris said, that's the first thing we do. We go do our parametric search and we use the chips that we can actually buy on DigiKey and Mouser. Yeah. If we can't buy from them. If we can't buy from them.
Chris Gammell: I was walking down the aisle of the cubes at my office the other day and I was just kind of like peeking in. And I saw probably, you know, five screens open to just, you know, distributor websites. It was easy. Yeah. You know, like you're just seeing what's out there because that is the first step. And I've told that to distributors before, you know, like that is the first step and those guys want to be the first step. You know, like. Yeah.
Dave Jones: And that's not just for a small player, small designer, small companies. That's for, I've worked in big companies where that's the case too. You look for what's available because you need a prototype next week. And, you know, and if you can't get the part, you're screwed.
Evin Yanbu: Yeah.
Dave Jones: Oh, we've got a question from Seb. I won't try and pronounce his last name. He says that a lot of the features in your simplicity software environment are really nice. And he asked, where did the software and the features in that, where did they come from? Did you plan that from the very start that you'd have these easy to use software tools? Or did that come later when you thought, oh, this would be cool if we had.
Evin Yanbu: I think a lot of it came later. I remember, I mean, so we have one tool called the Energy Aware Profiler, which has been great to us. I mean, having this tool and it's basically where you can see the energy consumption or current consumption live.
Dave Jones: Yeah. Per individual subroutine. I've done a video on this. Yeah. It's quite excellent.
Evin Yanbu: And actually, I remember that we talked about this internally, that this would actually be possible. But we thought that, nah, I mean, we'll just leave this stuff up to the kind of IDE suppliers and we don't want to step on their toes and so forth. But I think the truth is that the way I remember it, at least, is that one of the guys basically just sat down over the weekend and just made it still. Awesome. Yes. That is great. That is what we want to eat. Yeah. Oh, that's pretty cool. And then we were able to demo this before. The IR guys, they also have a plugin similar to this. I mean, the basic same functionality. But we made the prototype initially and just basically made it to a product later on. So some of this, I guess, has been a little bit planned and a little bit better planned than this one. But apart from this, I think it's a combination of planning and just doing stuff. Actually, we have another good thing in the company as well. I guess inspired by companies such as Google or others where a little bit different from different departments in the country, in the company. But like once a month or something, you get a day to just do whatever you want.
Dave Jones: Great.
Evin Yanbu: Like a blue sky kind of day, right? Yeah. We call it the Hacker Gecko Day. Hacker Gecko.
Dave Jones: Where did the gecko name come? Where did you choose the... How did you choose the gecko as your symbol?
Evin Yanbu: Yeah, that's a good question. So actually, it was just before the launch in 2009 where we're going to go public with our products.
Dave Jones: Just before the launch? Of course. It was a last-minute thing. Of course. Oh, man. I bet marketing love that. It's a startup, right? Yeah.
Evin Yanbu: And our CEO was watching a BBC documentary late Sunday evening with Sir David Attenborough. Nice. Brilliant. He was talking about how reptiles and amphibians... I mean, sometimes you could think of them as dumb and slow. But in reality, they're extremely fast. And they can actually have energy consumption, which is 10% of a mammal of a similar size.
Dave Jones: They are very energy efficient. It's very true.
Evin Yanbu: They are. Yeah. So that's how this came about.
Dave Jones: At the last minute. That's great. That's great. Quick, we're going to fab. We need a name for our chip. Yeah. Everyone looks around. Yeah. Oh, that's great. And we've got another question here from Kevin that relates to the software that we're talking about before. He says, how are you able to measure the power use per function call? Is it an actual measurement or is it just a calculated estimation?
Evin Yanbu: Well, it is an actual estimate, but of course it's an estimate. Right. But, okay. What we do is two things. We start off by having this live current consumption estimate. No, sorry. Not estimate, but current consumption measurement. Right. And additionally, there's some features in the Cortex-M3 core, which allows us to output the program counter. Either, I mean, it depends on which chip family you're talking about, but either on a serial interface or also in some cases on a semi-parallel interface with more trace functionality. But anyway, on this output, we get the program counter. And on the outside, we have the linker file, or not the linker file, but the mapping file, which tells us, so if you have a certain program counter value, which function is this actually inside? Got it. Yeah. So, but for sure, there's some weaknesses to this. It's like, it's possible sometimes that you have a function which is called, but you don't get the program counter sample still of this function. So, it will tell you-
Dave Jones: Right, it can be slightly off, yeah.
Evin Yanbu: It will tell you a fair description of the real life, but it will never be able to be, say, perfect. Right.
Dave Jones: Also- It won't ever be cycle by cycle, kind of.
Evin Yanbu: And even you couldn't measure like the, I mean, just imagine even that the execution inside the cortex is pipelined, right? Yeah, I know. It's crazy. Yeah. So, you can't really extract cycle accurate information, but you get a good trend. And typically, you catch a lot of these kind of busy waiting loops where you see that you're actually busy waiting for a long time where you thought there was nothing or, yeah. Got it.
Dave Jones: So, are there any other competitors out there that have a similar sort of functionality in their own tools?
Evin Yanbu: Well, I'm not aware of any.
Dave Jones: Yeah, I'm not either. I think it's fairly unique. So, that's almost a killer feature, you know? Yeah. And I think it's so obvious. I mean, you have these low energy power micros and you expect to have this capability to measure this sort of stuff almost. Yeah, yeah.
Chris Gammell: I know there's some third-party tools that allow you to do a lot of code analysis and see where you're sticking around in different routines and stuff. True, true. But you probably have to extrapolate that to actual power or whatever you're putting it on eventually.
Dave Jones: Well, I've done that thing before. Yeah, there's lots of manual processes. You have to estimate how much time you spend in that routine and then measure the average consumption and then divide it by that. And it's, you know, it's just not very nice.
Chris Gammell: All right. Yeah. Yeah. All right. Well, I think we may have overdone our amp hour, but it was definitely worth it, I think.
Dave Jones: It was definitely worth it. If we got any last-minute questions we haven't answered, I think we got through a good lot of them.
Chris Gammell: About 30, yeah.
Dave Jones: Oh, 30. Oh, wow. Okay. Wow. That always amazed me.
Chris Gammell: It was very good. Yes. Oivin, thank you so much for being on the show. Thank you very much, Oivin. It was awesome. You can find Energy Micro at energymicro.com. I'm not sure if you guys are on Twitter or not, but- Yes, they are. Oh, they are.
Dave Jones: At Energy Micro, yes. All right.
Chris Gammell: So you can treat your questions there. I'm sure you'll have people listening to this show hearing about your internal stuff and wanting to come work there too.
Evin Yanbu: Actually, also, from our marketing department, they told me they're going to give away some kits to some of the people who have asked questions.
Dave Jones: Asked questions. There was 10 Tiny Gecko kits they're giving away.
Chris Gammell: Yeah, great. Yes. Great. So we'll get in touch with those people. That's awesome.
Dave Jones: That's great. Because development kits are, you know, everyone loves getting a development kit. That's great. What's your philosophy on the development kits? Do you keep them as low cost as possible? Or do you want to actually make a bit of money on them?
Evin Yanbu: We're not making money. I think perhaps we're losing a little bit of money. But we're not making money on the kits. Make it up on the back end, yeah. Yes.
Dave Jones: But you certainly don't want to give them away, do you? Because people like Texas Instruments, you know, like $4.30 for their little development kit delivered. You know, crazy. They're just, you may as well give it away for free, you know? Yeah, you're getting there. So you don't want to go in that direction?
Evin Yanbu: Well, I mean, sometimes, of course, on a case-by-case basis, we may give away or even our distributors may give away. We sell it to distributors and they give it away. Of course. There's a lot of different variants. And sometimes we have promotional activities, right? But I think the only thing we don't want is to give it away and then it just ends up in some drawer, right? Of course. Yep. I've got that drawer. Yep.
Dave Jones: And do you actually sell any software, any development software or is all the software free?
Evin Yanbu: No, all our software is free, yeah.
Dave Jones: Excellent.
Evin Yanbu: Yes, it is.
Dave Jones: Because I was talking to the microchip CEO a year or two back and he said their philosophy is that they don't want to give away their software. Well, some of it they give away for free, but the high-end stuff, they don't want to give it away because then if they give it away, because it's such a huge corporation, the bean counters within the company, the finance people will see that that division is not making money and they'll want to shut it down. Yes. And the CEO, even though he's the CEO, won't have the power to stop them shutting down that whole division because it's not profitable. It's crazy, you know?
Chris Gammell: Which is why it's important to have a technical CEO to even recognize that. Yeah.
Dave Jones: So what are the plans for Energy Micro? Do you plan on growing into a big company or staying lean and small and fast and agile?
Evin Yanbu: We plan on staying an independent, say, small to medium-sized company. Yep. And, I mean, basically growing our business worldwide. So probably, I mean, growing the stock exchange in some years. That's the plan.
Dave Jones: Oh, okay. So you will list on what, the local Norway?
Evin Yanbu: Yeah, probably, yeah.
Dave Jones: Or the American?
Evin Yanbu: I'm guessing Norway, but I guess this is something that I'm just a CTL, right?
Dave Jones: Yeah, right. Exactly. You don't care about money, right? As long as you're making cool stuff and hacking things. As long as it's fun, yeah. Yeah, that's right. That's great. Oh, I love it.
Chris Gammell: All right. Well, thank you again, Oivind. It was awesome talking to you.
Evin Yanbu: Yeah, it was great talking to you.
Dave Jones: Fantastic insight into the company. I hope it goes well for you.
Chris Gammell: Yes. And thanks again to Oivind for being on the show. It was really great. It was. We'll see you next week. Bye. Cheers.
Dave Jones: All right. So we'll see everyone next week, and you can catch us on. You normally do the outro, Chris. I do. I already did it, Dave. Oh, right. Oh, and then I jumped in with more questions. There you go.
Archived Discussion (6)
Comments are closed. Archived from the original site.
Show archived discussion (6)Hide discussion
Keep current
Every episode, plus the occasional job post, in your inbox.


This excellent interview made me think - I wonder if Steve Furber might be interested in chatting? He hasn't been with ARM for quite a few years, but he has many stories from the early days, and is active in academic research now.
I also checked the EM website. I found out, that some of the dev kits are only available through global distributors (Digikey, Mouser) or local distributors, but not directly from EM. This would give some sort of personal touch to it. Not all DVKs are available from distribution (for example: EFM32GG-STK3700) unfortunately (no info using EM's website, I'm from Germany).
On the other side, I checked for available realtime OSs to support EFM's features. While there are some to support the general ARM Cortex-M3, the features for energy management are supported only in some special cases:
1) using commercial compilers (like the IAR) and commercial RTOSs or
2) specially trimmed RTOS (Ref. tickless RTOS: great master thesis on that here: http://www.freertos.org/Interactive_Frames/Open_Frames.html?http://interactive.freertos.org/entries/20291196-energy-optimized-port-of-freertos-6-for-efm32) also using IAR.)
For a successful microcontroller, there is much more than the hardware itself, it's the whole ecosystem.
What made me really thinking about EM was the whole company credo which Øyvind explained in a some detail. I guess, that's a great vision which in needed for being a successful and passionate company.
Thank you very much for such a great episode. Maybe you can invite Øyvind back some time later.
Thanks for a great show, thanks for the good questions and also for the feedback afterwards! :)
David: Regarding modifications to the ARM source code, I can also only speculate, but of course ARM runs a huge amount of verification on their cores, and don't want their customers to introduce bugs into their IP. :)
Thomas: Regarding kit availability, I know that the GG kits will show up at distributors very shortly. :)
Again, thanks for your time and feedback!
Cheers,
Øyvind