I'm DONE with u-boot!

preview_player
Показать описание


Рекомендации по теме
Комментарии
Автор

Embedded development is a shitshow in general. Nothing else in life ages you faster

darylfortney
Автор

This is the most hilarious April Fools Day video I have seen 🤣 absolutely hilarious 😆 well done, Tomaz!

joerobinson
Автор

Fun story about the erratum
A couple of years back I worked on a LX2160A, and needed to disable some erratum since they were used for parts on the CPU that we disabled thorough the RCW, so some errata would cause the CPU to crash.
I found a bunch of other erratum that were made by ARM themselves and some undocumented ones that were copyrighted by NXP
So we contacted NXP asking about about those in order to make sure that they wouldn't cause issues and if we needed to disable them.
NXP told us that they had they indeed did not write those erratum, even though we saw the NXP copyright in the code itself lol

awesomefacepalm
Автор

I thought the video title was clickbait, like "I'm DONE with trying to make U-Boot work and I want to use something different." 🤣

klfjoat
Автор

A µC we use at work has a wonderful erratum: "The SATA module on this chip does not work. Do not use it." That is it.

nullplan
Автор

The pleasures of getting a busybox shell from your NFS rootFS & TFTP Kernel/device tree on your own PCB after getting RAM and networking up in uboot is such a great experience. Especially if it took a long time to get working :P
I followed a very similar trajectory in 2017 to end up with a custom Android OS for embedded use, running on an OEM iMX6 based board normally used for industrial applications.

DriesBE
Автор

20:30 I didn't expect the sudden gore
It is a rule of the universe that if there are two signal lines (Rx/Tx or SCL/SDA), you will get them swapped somewhere on a new PCB. All you can do is plan for it and put some traces and vias where you can fix it without soldering wires to a QFN chip. At the very least, don't route them under the chip (or an inner layer!), because that tempts the universe to cause the chip to break the I2C bus on the way to another chip.

bitwiz_
Автор

On every first Saturday of the Month, the Fan should at noon run for 30 seconds at full speed. Dedusting feature.

_miranHorvat
Автор

I don't need this device, got the Banana Pi R4. But watching your videos, I guess I'll pre-order anyhow. The effort that went into the board and now SW... Amazing, thanks a lot for all you do.

rklauco
Автор

Ahh Uboot and ARM device trees - got to love ARM - thank the high one I am now using Intel embedded CPU's, PCI Express and UEFI.

tibbydudeza
Автор

We implemented acpi for aarch64 back when I was still into embedded stuff at rh. Because device tree is crazy for enterprise gear.

JonDisnard
Автор

Not gonna say "I called it" but I DID call it - apparently they need those asinine I2C multiplexers because they decided to go with the specific variant of the fan controller that has not enough pins to set a distinct address, as opposed to the other variant in the same family WHICH DOES. Although I seriously wonder why one would need more than one dual fan controller in a router, and if they don't then only Murphy knows why they would...

AttilaAsztalos
Автор

Tomaž welcome to Youtube. Your font might look large on your screen but for the Yt audience the font should min. 22 be.

Turjak_art
Автор

I misread the video title - it came across as pretty hostile.

hikingpete
Автор

Oh, the hardware issues are a real pain during the bring-up, sometimes you start to question your life choices... Especially when you are working on the engineering sample from a third party and after trying everything you switched to the hardware debugging just to find out that the pull-ups/pull-downs were miscalculated and an uninitialized SOC pin switches the data lines from the Ethernet to DSL by default so nothing working.... Oh man... 😂

dexvovich
Автор

Wow, The usb bug is also on the raspberry pi. The webcam stopped working after a while. I just yank the kernel module and slap it back in after the ffmpeg process failed to exit.

陳冠維-fi
Автор

I spent 5 years of my life doing "board bring up" and tailoring uboot is a PITA which may include doing assembly to get memory timing correct for multiple temperatures(outdoor device). Makes MOSI and MISO look like childs play. Anyway misery loves company and I'm happy to hear your misery!

jjdawg
Автор

I just wanted to say thank you for not participating in april fools. At least some sanity on Earth remains.

pahnazd
Автор

Well it could be worse like discovering a broken SPI driver (BSP) that works on some SPI nands and not on other.
The crash was during kernel load and we spent too much time thinking the issues was in the compressed image.
As uboot was small it was working fine... more SPI access more probable to have a full lock of the bus.

tuttocrafting
Автор

Man this project is so interesting and great, but I have absolutely zero use for a 10 Gbit router lol

tobimai