EEPROM Загрузчик для MIK32 (K1948BK018)

В данном тексте я написал про то, как я написал загрузчик для российского микроконтроллера MIK32 ( K1948BK018 ). Это, пожалуй, первый случай, когда столько функционала мне пришлось утрамбовать всего в 8kByte ROM памяти.

https://habr.com/ru/articles/806275/

#mik32 #K1948BK018 #BOOTLOADER #EEPROM #Загрузчик #STARTMIK32V1 #terminal_19b #SPIFlash #UART #W25Q32JV

EEPROM Загрузчик для MIK32 (K1948BK018)

"Если дом начинается с двери, то прошивка начинается с загрузчика." Пролог В этом тексте написано про то, как я написал загрузчик для российского микроконтроллера MIK32 (K1948BK018). Определения Чтобы...

Хабр
Wow- recovering #data from a broken board from a crashed rocket.
https://dontvacuum.me/rocketflashrecovery/index.html #hardware #rockets #raven3 #spiflash
Crashing rockets and recovering data from damaged flash chips

Enabling Intel AMT For BIOS-over-WiFi

Intel ME, AMT, SMT, V-Pro… All of these acronyms are kind of intimidating, all we know about them is that they are tied to remote control technologies rooted deep in Intel CPUs, way deeper th…

Hackaday

As a proof-of-concept, changing 3 lines made our pmOS image "just work" using tow-boot!
https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2870

We're ready for #SPIflash on the #PinePhonePro @Pine64, just waiting for you ;)

pine64-pinephonepro: switch to UEFI booting (!2870) · Merge requests · postmarketOS / pmaports

This removes u-boot from our image and allows booting via an UEFI-compatible platform firmware instead. So to flash pmOS on the PPP now we will require the user...

GitLab
Modules like #SPIflash are really important to achieve the goal we've set at #postmarketOS: device support for 10 years and more. Once a device is fully mainlined and can boot using a generic #UEFI image we no longer have to put any effort in supporting this particular device. Everything will "just work". Just like no distro put any effort in making it boot with my particular desktop and laptop.
Flashing so-called "platform firmware" which implements #UEFI, like u-boot, to this #SPIflash would allow the user to boot generic UEFI images not made specifically for the device in question. Finally you'd be able to properly live-boot a distribution through e.g. sdcards, USB sticks, etc. And you no longer have to wonder if your distro supports your particular device, you just have to download their generic UEFI image!

https://is-spi-on-pine64-devices-used-yet.site/

Did you notice that rather than on PC where you download a generic image which you can just live boot from USB, on ARM every distro needs to support every device individually? It's not just lacking mainline Linux support, it's also lacking a generic way to boot these devices like x86 has. #SPIflash can solve this perfectly by implementing UEFI on a dedicated chip but current new @PINE64 devices are lacking this. Let's get loud to make them add this again in new devices!

Is SPI used on PINE64 devices yet?

Router liberation!

#openwrt #spiflash