Hello,
According to "README" in /board/freescale/p2041rdb there are 2 files I
should burn except uboot.bin:
rcw.bin
ucode.bin
I tried to google those file names and found nothing.
1. Can you tell (a link will be great) what is the purpose of those files ?
How should I create them ?
Using
Hello,
I built u-boot-2010.09 for Freescale's P2020-RDB.
It works great !!!
The setup I used for SW4 is according to the startup guide. SW4[7] is on.
When SW4[7] is off u-boot hangs. It means:
"boot sequencer enabled and configuration information loaded from I2C ROM. A
valid ROM must be prese
Hello,
I built u-boot-2010.09 for Freescale's P2020-RDB.
It works great !!!
The setup I used for SW4 is according to the startup guide. SW4[7] is on.
When SW4[7] is off u-boot hangs. It means:
"boot sequencer enabled and configuration information loaded from I2C ROM. A
valid ROM must be presen
Hello,
I want to boot vxworks with uboot 1.3.4 using nfs.
After I got the prompt I wrote + and then +
and vxworks was launched.
How can I do it upon completion of countdown after running uboot like with
"tftpboot".
I tried the following:
#define CONFIG_BOOTDELAY 3
#define CONFIG_BOOTCOMMAND
Hello,
Is it possible to boot an X86 machine (with ATOM or Core2Duo) using uboot ?
If yes, how uboot is loaded to the master boot record of the disk from which
the machine is booted ?
What file in include/configs fits to x86 board ?
Thanks.___
U-Boot
Hello,
I'm using u-boot on PPC405 (ML405) for about 3 years.
It is a great boot loader !
On my next project, the target is Core2Duo (AMPRO's COM840).
Is it a wise decision to use u-boot on this target ?
I prefare u-boot over grub or vxworks bootloader because it has many
features.
If I unders
Hello,
Upon 'ping', u-boot is trying to initialize PHY.
In my case, the PHY is initialized by external hardware, not by MDC\MDIO.
In menuconfig, there is no option to exclude CONFIG_PHYLIB
-*- Ethernet PHY
How should I modify u-boot so that the CPU will not try to initialize PHY ?
Thank you,
Zv
Hello,
I'm using u-boot for xilinx zcu102.
In order to create ramdisk image I used the command:
genextfs -d $ROOTFS -b 65536 -D rootfs_devices.tab ramdisk
But during linux boot, linux writes many message:
mdev: can't create '': No space left on device
I tried to use 262144 instead of 65536 a
Hello,
Can you tell if this is possible ? How ?
Thank you,
Zvika Vered
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
9 matches
Mail list logo