Well, Dave, you might have to consult the experts who know a whole lot more 
about the low level details of how the BBB boots, but I think you need to 
understand the following:

1.) UART0 is not required for the BBB to boot, but when the BBB does not 
boot, UART0 is the place that has the information about why it is not 
booting. So not a good idea to try to bring up a new piece of hardware 
without access to the debug port.

2.) You might note that the same software distribution runs on five or six 
very different pieces of hardware. Multiple variants of the BeagleBone and 
PocketBeagle with different hardware sets and capabilities.  The 
information that UBoot and probably the kernel, too, needs to figure out 
what they are dealing with, is in the EEPROM. So, if you are not going to 
provide that information, you are in for some rewriting and recompiling of 
probably both uBoot and maybe the kernel, so you can hard code the 
information somewhere that they expected to get from the EEPROM.  It is not 
as simple as providing a new device tree.

--- Graham

==



On Saturday, January 12, 2019 at 7:32:53 PM UTC-6, Dave wrote:
>
> I am working to bring up a BBB "clone". 
>
> There are two significant differences that are/may be causing problems. 
>
> 1). UART0 is not accessible. 
> 2). The device does not have the BeagleBoard 32K I2C eeprom. 
>
> Anyone have pointers for building a U-Boot that Uses any other UART 
> besides 0 ?
>
> Is U-Boot going to have an issue because of the missing eeprom ?
> Linux ?
>
>
> Do I just need to change uEnv.txt to force a specific device tree ?
>
> Thank you
>
>
>
>
>
>

-- 
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/b8598e22-1db9-47e4-b906-66ba59ec3ffa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to