qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
camus has joined #u-boot
tsraoien has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
tsraoien has quit [Ping timeout: 240 seconds]
umbramalison has quit [Quit: %So long and thanks for all the fish%]
umbramalison has joined #u-boot
thopiekar_ has joined #u-boot
thopiekar has quit [Killed (erbium.libera.chat (Nickname regained by services))]
thopiekar_ is now known as thopiekar
mmu_man has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
thopiekar has quit [Ping timeout: 255 seconds]
sukbeom has quit [Quit: WeeChat 3.5]
thopiekar has joined #u-boot
mkennedy has joined #u-boot
mkennedy is now known as hurricos
<hurricos>
I have a JTAG driving an mpc85xx board. I don't have NOR, only NAND; I'm trying to undertsand the separation between SPL, TPL and main u-boot.
<hurricos>
I ask this because I think I can do everything SPL and TPL do using the JTAG (RAM init, mostly)
<hurricos>
I'm trying to read config variables to understand where TPL loads the main u-boot, and what configuration it sets (e.g. where does it set CCSRBAR, and how can I tell)?
<hurricos>
I'm trying to more generally understand how SPL to u-boot hand-off is done, too. Nothing special about TPL, it's just used because mpc85xx has init issues
<hurricos>
I think that once I understand enough of this, I will be able to run minimal code that I've compiled, at which point I can trace my way to a more complete understanding
<hurricos>
it's just that as it stands I can't do that, because there is zero documentation for booting from RAM :(
<hurricos>
The JTAG in question is a BDI2000, which I've gotten comfortable with tonight
<hurricos>
The board is a P1020-based one. I have gotten RAM init working great :^)
<hurricos>
Just not in u-boot.
<hurricos>
Not that that matters.
<hurricos>
Is SYS_LOAD_ADDR the default address that U-boot tries to get copied to, or the default address that U-boot tries to copy what it's booting to?
<hurricos>
Thanks to boot/Kconfig, it's SYS_TEXT_BASE.
<hurricos>
Oh, that'd explain my issue. My RAM isn't quite right.
persmule has quit [Remote host closed the connection]
sukbeom has joined #u-boot
Patater has quit [Ping timeout: 276 seconds]
apritzel_ has joined #u-boot
apritzel_ has quit [Ping timeout: 272 seconds]
GNUtoo has quit [Remote host closed the connection]
flyback has quit [Ping timeout: 272 seconds]
GNUtoo has joined #u-boot
flyback has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
mmu_man has joined #u-boot
<sjg1>
apalos: Yes Tom is right, should probe the rand device, not the TPM. Since the rand device is a child of the TPM, the TPM will be probed automatically