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. -- 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/165f9e23-9329-4585-9b12-921a7ce094f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
