Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can follow instructions pretty good but I'm not perfect.
Is it possible to brick one of these sbc if a procedure step were skipped or something was entered incorrectly?
I'd say it was highly unlikely (for example, with the Raspberry Pi 4 in terms of flashing the EEPROM) but it would certainly be possible by putting too much current into the device or shorting the GPIO pins. I once saw a YouTube video where a guy using a variable power supply made a mistake with the power setting and smoked his Raspberry Pi.
I can follow instructions pretty good but I'm not perfect.
Is it possible to brick one of these sbc if a procedure step were skipped or something was entered incorrectly?
For amlogic and rockchip devices, with an incorrect bootloader or writing/erasing the bootloader in SPI/eMMC, this is possible, but on the developer boards there is a button or contacts that put the device into the (MASKROM) firmware mode using the otg cable.
I'd say it was highly unlikely (for example, with the Raspberry Pi 4 in terms of flashing the EEPROM) but it would certainly be possible by putting too much current into the device or shorting the GPIO pins. I once saw a YouTube video where a guy using a variable power supply made a mistake with the power setting and smoked his Raspberry Pi.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
