I apologize for the nearly 4 months long hiatus but outside of general work stuff, I ran into issues with the openocd and shakthi which slowed progress until that got resolved. See here for more details if interested.
Warning: If you have are following instructions from Part-1 where we built the processor, DONOT use the bit file I’ve uploaded in the pre-built repo here; this has been updated in the shakthi repo here; grab that and program it and you should be good to go.
I’ve decided to use PlatformIO with VSCode for evaluating the Shakti to start with although I will give Zephyr a shot when I can. …
While I was randomly perusing through my LinkedIn feed(we’ve all done it) I’ve recently discovered the Swadeshi Microprocessor Challenge and was extremely curious as to what the Shakti platform offered.
This article is Part-1 of the steps I did to get started with the platform. Part-2 will cover the software development ecosystem and my thoughts on it.
An excerpt from the Shakti website
Shakti is an Open Source processor development program based on RISC-V ISA. There are many classes of processors in the Shakti ecosystem with varying compute capabilities.
There are a couple of different classes of processors available for evaluation, the E-Class and the C-Class processors. …
After a seeing a few posts on show up on my LinkedIn, I decided to take a peek and see what the fuss was about. And since the whole ‘work-from-home’ thing is making my weekend indistinguishable from a normal wrkday, this was a happy medium.
Let me preface by saying, Pigweed isn’t a fancy new embedded target OS. Pulling straight from the Readme,
Pigweed is an open source collection of embedded-targeted libraries — or as we like to call them, modules. …
The Internet-of-Things(IoT) is steadily progressing from a buzzword to an attractive, mature market. A few years ago, people scoffed at the idea of everyday objects being connected to the internet but today, you would be hard pressed to walk through a retail store without running into an aisle stocked with these ‘smart’ devices.
Unsurprisingly, hackers aren’t far behind. Just google “IoT security breaches” and you will get well over a million hits with a plethora of information on how someone could get access to your devices.
While part of the problem is simply growing pains of a new market segment, the real challenge exists in finding a cost-effective way to implement (traditionally) ‘enterprise-grade’ security in a ‘consumer-grade’…
The recent flurry of media attention on the ESP32 IoT device attack piqued my interest in secure boot on IoT devices. Espressif has already announced CVE-2019–17391(here) and published a Security Advisory from Espressif here which can protect against future devices but existing designs in the field will remain vulnerable.
The purpose of this article isn’t a comment on Espressif or it’s secure boot design but it a look at what would happen if one piece of the secure boot chain is compromised.