Marc Jones Marc.Jones@amd.com writes:
Arne Georg Gleditsch wrote:
Marc Jones Marc.Jones@amd.com writes:
This was my fault. I missed reviewing the abuild config.
This is now the same as serengeti_cheetah_fam10.
A little background information. The fam10 initialization is a bit larger than the K8 code. To make more room in the same 512K ROM that most platforms have the normal image was dropped. The other change is the use of failover. This makes the XIP CAR code live in only one place instead of in the fallback and normal images.
Arne, please test a s2912_fam10 abuild and ack this.
I'll do so. However, once I start digging into this -- would it make sense to fix it properly so that the target builds a full 1024K ROM (as the board is equipped with) and actually includes both the normal and failover image?
Sure, That would be great.
Sorry about the delay, I was sidetracked by other stuff. Here's a patch towards r3690 upping the ROM size for the S2912 Fam10 target to 1M. Both regular and abuild images have been boot tested successfully. (Not having a proper abuild infrastructure set up, the abuild image fails on not having a real payload available, but otherwise looks correct.)
Signed-off-by: Arne Georg Gleditsch arne.gleditsch@numascale.com