I design hardware for a living. You need to throw this back at the hardware designer and have him/her present you with a workable board.
They took a SIP designed to take all the hard work out of making a BeagleBoard clone and managed to mess things up enough so that it won't boot and you can't even tell how. At the very least, I would insist on having them wire up UART0 so you can have a console. Unless they royally f**ked up the PCB layout, this should be possible by soldering a few "flying wires" to some via pads. If they didn't fanout all the SIP pads to vias, you have my permission to shoot them! :) <just kidding> Best of luck! ...and if you don't want to get confrontational with the HW guys, you should be able to fairly easily compile U-Boot to use a different serial port. That ought to get you any console info printed except for the character(s) printed by the actual ROM boot loader. And once you have console output, debugging gets a *LOT* easier. :) On 1/14/2019 5:06 PM, Dave wrote: > I have been searching arround all day and gathering more information. > > The "Clone" board appears to be an Octavo SIP and is partly patterned after > an PocketBeagle. > There is also a display similar to that of the BB 4.3 Cape. > The SIP eeprom is unlikely programmed, there is no eeprom to tell linux > about the display. UART0 is not accessible, and there is no networking - > beyond g_ether. > > Even if I resolve the SIP eeprom - the display is not going to come up, and > I am not going to have a serial console and I am not going to have network > access to the board. > > And at this point I do not actually know that the board is good. > > To me that means I really need to rebuild u-boot - and assign the console > to one of the other uarts. > I might as well at the same time address the SIP eeprom. > > This board has a USB A and a USB B connector, so I can for development > purposes attach a USB NIC to gain network access to the board. > But I still probably need the serial console until I have the net fully > configured. > > I pulled your "Bootloader-Builder" Github repository as there was a patch > there to address the eeprom issue. > > But just running build.sh ran for hours, failed, and is probably not what I > wanted. > > I commented out most of the builds at the end of build.sh. > > I am guessing that I want am335x_bone_flasher enabled. > But I also want to enable a patch to assume a pocketbeagle > as well as to change UART0. -- Charles Steinkuehler [email protected] -- 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/e79d25e7-b910-e5c3-3f2c-72fa675d617f%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
