With these patches applied, I use the following script to build an image for chainloading or flashing:ġ) if then allow_dirty=true else usage fi BTW, the LED support in this version is hard-wired, not configurable via environment variables like Jeff's version. They didn't get accepted, but it looks like there's hope. If you want to compare, I submitted a set of patches against the current (v2010.06) u-boot sources to support the DockStar. > I've been digging into this so that I can compile u-boot on the dockstar. DATA 0xFFD0150C 0x00000000 # CSn Size, window disabled DATA 0xFFD01410 0x0000000d # DDR Address Control Here's the diff against the original git version for board/Marvell/sheevaplug/kwbimage.cfg Here's the diff against the patched version for board/Marvell/sheevaplug/kwbimage.cfg Make sheevaplug_config (configure u-boot)ĭd if=u-boot.kwb of= ibs=512K conv=sync (pad it to 512K) (don't need the sed command as the file board/Marvell/sheevaplug/config.mk already has TEXT_BASE as 0x00600000) So with kwbimage.cfg file setup correctly you can then just do the following: I went ahead and matched it up with the values from dramregs_pp128_A.txt and it now produces a file with the correct header just like the doimage does. If the file board/Marvell/sheevaplug/kwbimage.cfg is setup correctly then make u-boot.kwb will work. So instead of doing a make u-boot.kwb it could have been a make u-boot.bin. In the case of the mkDockstar.mtd0 it ends up deleting it since it is later produced by using doimage and dramregs_pp128_A.txt files. The ultimate goal here is to produce a u-boot.kwb file. Though I don't know why what I produce does not work yet. I've been digging into this so that I can compile u-boot on the dockstar.
0 Comments
Leave a Reply. |