On 06/01/14 18:42, Simon Glass wrote:
Hi Martin,
On 30 May 2014 04:33, Martin Ertsås martiert@gmail.com wrote:
Hi.
I'm trying to use u-boot as a payload to coreboot. Problem is that when coreboot starts u-boot, it fails with panic("No tick base available");
When looking at the backtrace this gives a recursive error, as panic calls __udelay and get_ticks, which again panics. I heard this was because u-boot overwrote the memory location of coreboot, and that there have been some patches going around that fixes this issue, but have not made it upstream. As far as I can tell, chromebook v2 uses these patches to make their stuff boot. Can anyone point me in the right direction for those patches? I have tried finding them myself, but can't seem to find them.
It probably means that Coreboot is not passing its timing data to U-Boot. You need to enable a timestamp option in Coreboot to do this.
You could patch it to remove this panic and just use 0 in this case.
Regards, Simon
Thanks. I'll look into the timestamp option. So using 0 as the tick value should work?
- Martin