[microblaze-uclinux] Re: [microblaze-uclinux] u-boot 1.2.0 petalogix patch.

[Monstr@xxxxxxxxx]

> Perhaps a solution here is to commit a stripped version of auto-config.h
> into the u-boot tree, on the understanding that it is dynamically
> generated for each new system anyway?

Yes. I do the similar BSP files but only for U-BOOT tree. You can look at my last
development version at www.monstr.eu section Das U-BOOT. (latest version is 1_00_d)
But be aware that I don't have tutorial howto writing TCL for xilinx EDK. Have you got any
tuturial for this?
Our BSP was very helpful for me. Thanks.


> I think all that's really needed is the RAM and FLASH settings, CPU
> configuration, and any network device support (emac / emaclite).

Yes. I know about it. ML401 use FLASH and RAM configuration and I add the small assembler code
for relocation all U-BOOT code (start.S) that is why you can store U-BOOT anywhere and your
first stage bootloader only jump to first address. But be aware because if you are used fs_boot for
copying U-BOOT (srec format) - the reset command don't work. The problem is deep in malloc function, which
use the sbrk_base address and for only reset without relocation and the sbrk_base is set to old value from
the previous instance of U-BOOT.
If you are use fs_boot your U-BOOT code will be placed on TEXT_BASE and RESET command don't work
If you are build U-BOOT with TEXT_BASE for example 0x3800_0000 and your RESET_ADDRESS is 0x3600_0000
(or 0x2800_0000 in Flash) and your first stage of bootloader copy U-BOOT to RESET_ADDRESS
(if you will use system without flash) and/or jump to RESET_ADDRESS (U-BOOT stored in flash) your code
will be relocate to TEXT_BASE address.

For RAM based storing U-BOOT you must protect U-BOOT in RAM (RESET_ADDRESS + U-BOOT size). I plan to design
and incorporate U-BOOT code to structure of top of memory.

EMAC, EMACLITE and Xilinx drivers.
Current week I sent to U-BOOT mailing list the request about xilinx drivers and conclusion is simple.
Xilinx drivers flowing from Xilinx standalone drivers isn't allowed and only one way is rewrite this drivers to
compress form (best one file). I plan to do rewrite minimally EMAC and EMACLITE drivers.

> I concede that much (most?) of auto-config.h contents are not required
> by u-boot.  In PetaLinux it's actually a symlink to the kernel's
> autoconf.h, but understand that nothing will go into the main u-boot
> repository that imposes a dependency on PetaLinux.

Yes.

Best regards,
Michal Simek
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/