Thanks. I'm doing that now. Board one (Red black board) boots to login.
HDMI is working. Yay. Now I've got to figure out where the USB ports go.
This custom break-out board has 4 USB ports but none of them connect to the
main USB-A port. That goes to a 4-pin header that of course are a different
pitch than that connector I have on-hand. I've another one somewhere in
this mess. I'll just plug it into the network and use ssh.

For the other board (Seeed Beaglebone) what are the chances the LCD
touchscreen goes to the pins and will work once flashed?
Green board in the pictures:
https://photos.app.goo.gl/y85CDxPYzyg2s7yS9

I should have 2 more units to play with tomorrow. Now I just need to figure
out what I'm going to do with them.

On Mon, Feb 15, 2021 at 2:19 PM Dennis Lee Bieber <[email protected]>
wrote:

> On Sun, 14 Feb 2021 11:30:19 -0800 (PST), in
> gmane.comp.hardware.beagleboard.user Don Kiser
> <[email protected]> wrote:
>
> >I acquired a unit from work that has the following (decommissioned
> >machines):
> >
> >Board 1 - Seeed Studio BeagleBoard green - with LCD and touchscreen
> attached
>
>         I'm not up-to-date on BBG, so can't help with recommended images...
>
> >Board 2 - BeagleBoard Black industrial - headless breakout board but it
> has
> >a HDMI port (nothing happens when I boot with it connected)
> >
>         Presuming this is equivalent to a regular BBB but with extended
> thermal
> range, then...
>
> >I'm used to working with Raspberry Pi and Arduinos but the beaglebone
> >tweaked my interest. I'd like to get these units to a
> >'usable'/understandable graphical interface before I develop uses for
> them.
> >I have no idea how to do this.
>
> >As I understand it the BeagleBoard has a built in eMMC that can hold the
> >software image to boot. In my attempts to get them back to stock I may
> have
> >overwritten them. \
> >
>
>         Simplest is probably to start with a current /flasher/ image to
> overwrite the eMMC. The IoT Flasher image at
> http://beagleboard.org/latest-images is a bit old, but also established as
> a "production release" image. Otherwise you are looking at something like
> the "bone-emmc-flasher" image at
> https://rcn-ee.net/rootfs/bb.org/testing/2021-02-08/buster-iot/
>
> NOTE: make sure you have a board with a 4GB eMMC -- some of the earliest
> BBB boards had only a 2GB eMMC and most modern images won't fit that.
>
>         Burn the image to a uSD card of 4+GB.
>         Insert card in BBB
>         HOLD DOWN the Boot Select button (the one nearest to the uSD slot)
> and
> (while holding the button down) apply 5V power to the barrel connector (do
> NOT rely upon USB power when flashing the eMMC)
>
>         Ideally, the board should start a Larson scanner (cylon/Knight
> Rider)
> pattern on the blue LEDs. Wait for that to stop and the board shuts down.
>
>         Remove uSD card, reapply power (this time, the power button --
> next to
> Ethernet connector -- itself should be enough to turn the card back on). It
> should boot with the new image.
>
>         Note that the flasher images tend to Internet-of-Things oriented
> -- no
> graphical interface. The images with a graphical interface will have LXQT
> in the file name. It IS possible to turn those images into flasher images
> (just requires editing one line in the /boot/uEnv.txt file -- but you need
> a Linux system to mount the uSD card on, Windows doesn't handle EXTn file
> systems) -- however, putting an LXQT image on a 4GB eMMC leaves barely
> enough room on which to run apt update/apt upgrade (and, if the image is
> too old, apt will fail as there isn't enough free space to buffer the new
> stuff). Better to install the LXQT image on an 8+GB uSD card, insert the
> card, and reboot the BBB (flashing with a new image should update u-Boot
> enough to no longer need the boot select button to load an OS from uSD card
> -- if the card is present, it will use it instead of the OS on eMMC). Then
> run the scripts to "expand" the 4GB image to use the entire uSD card space.
>
>         The BBG may use the same procedure, and maybe even the same
> images. I
> can't confirm.
>
> >Goal: Get them back to running a 'stock' graphical interface or similar.
> >I'm at a bit of a loss on what needs to be done as these are foreign
> >devices to me. I kind of understand what they are capable of but I don't
> >have a specific project for them, yet. I'm wandering aimlessly trying to
> >get them back to stock.
> >
> >I'll bring my serial adapter from work on Monday 2/15/2021 to see what
> that
> >gets me.
> >
> >Help me get back to 'square 1' and I'll go from there.
>
>
> --
> Dennis L Bieber
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/85hl2gtb2q973965ocln17q1t84pdlq18t%404ax.com
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAC6886Mjf6r7%2BiaiTt3LCO6W9XgSVM%2BKXTvtobWfqqsghy-zUA%40mail.gmail.com.

Reply via email to