Install barebox on target
Hi,
i'm working on a project with a Freescale i.MX35 3-Stack board and try to use barebox as bootloader.
My problem is that i don't know how to install barebox to NAND memory or better directly to a sd-card.
Is there any documentation about this really basic stuff?
regards
Thomas
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Hi Thomas,
Quoted 7 lines · Thomas Mayer
Hi,
i'm working on a project with a Freescale i.MX35 3-Stack board and try to use barebox as bootloader.
My problem is that i don't know how to install barebox to NAND memory or better directly to a sd-card.
Is there any documentation about this really basic stuff?
According to the schematics the i.MX35 3-stack is without modifying it only able to boot in external boot mode, that is nand or nor flash. First step should be starting barebox as a second stage loader from the existing bootloader. For this the defconfig for the 3stack should be suitable. If you are using redboot you can use the following (replace 0x100000 with some valid sdram address):
load -r -b 0x100000 barebox.bin
run 0x100000
The same for u-Boot:
tftp 0x80100000 barebox.bin
go 0x80100000
If this works you should check if networking works:
dhcp; tftp barebox.bin /dev/ram0
or, if you use the smc9117 on the debug board:
ethact eth1; dhcp; tftp barebox.bin /dev/ram0
you can then flash barebox to either nand or nor flash:
erase /dev/nor0.barebox; tftp barebox.bin /dev/nor0.barebox
or:
erase /dev/nand0.barebox.bb; tftp barebox.bin /dev/nand0.barebox.bb
I suggest that you first try to flash barebox to the flash that does not contain your original bootloader (if you haven't got jtag)
For getting a barebox suitable for starting from NAND you should enable CONFIG_NAND_IMX_BOOT in your config.
The 3stack should be able to work in internal boot mode if TP41/42 on the personality board are adjusted.
You also might want to apply the boot mode cleanup patch I just posted which makes it a bit clearer what boot modes are actually supported by barebox.
Hope that helps,
Sascha
Quoted 8 lines
regards
Thomas_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
MX35 U-Boot > go 0x80100000
## Starting application at 0x80100000 ...
h�
barebox 2011.02.0 (Feb 25 2011 - 09:49:05)
Board: Freescale MX35 3Stackcfi_probe: cfi_flash base: 0xa0000000 size: 0x04000000 mc13892-i2c@mc13892-i2c0: PMIC ID: 0x000045d0 [Rev: 2.0a]register_device: already registered eth0
Have you any idea what the problem is?
regards
Thomas
Am 24.02.2011 17:04, schrieb Sascha Hauer:
Quoted 52 lines
Hi Thomas,
Quoted 8 lines · Thomas Mayer
Hi,
i'm working on a project with a Freescale i.MX35 3-Stack board and try to use barebox as bootloader.
My problem is that i don't know how to install barebox to NAND memory or better directly to a sd-card.
Is there any documentation about this really basic stuff?According to the schematics the i.MX35 3-stack is without modifying it only able to boot in external boot mode, that is nand or nor flash. First step should be starting barebox as a second stage loader from the existing bootloader. For this the defconfig for the 3stack should be suitable. If you are using redboot you can use the following (replace
0x100000with some valid sdram address):load -r -b
0x100000barebox.bin
run0x100000The same for u-Boot:
tftp
0x80100000barebox.bin
go0x80100000If this works you should check if networking works:
dhcp; tftp barebox.bin
/dev/ram0or, if you use the smc9117 on the debug board:
ethact eth1; dhcp; tftp barebox.bin
/dev/ram0you can then flash barebox to either nand or nor flash:
erase
/dev/nor0.barebox; tftp barebox.bin/dev/nor0.bareboxor:
erase
/dev/nand0.barebox.bb; tftp barebox.bin/dev/nand0.barebox.bbI suggest that you first try to flash barebox to the flash that does not contain your original bootloader (if you haven't got jtag)
For getting a barebox suitable for starting from NAND you should enable
CONFIG_NAND_IMX_BOOTin your config.The 3stack should be able to work in internal boot mode if TP41/42 on the personality board are adjusted.
Quoted 20 lines
You also might want to apply the boot mode cleanup patch I just posted which makes it a bit clearer what boot modes are actually supported by barebox.
Hope that helps,
Sascha
Quoted 9 lines
regards
Thomas_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Quoted 6 lines · Thomas Mayer
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 3 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hi Sasha,
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.
Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -
06:24:35)
CPU: Freescale i.MX35 at 532
MHz
Board: MX35 3STACK 2.0
[RST]
I2C:
ready
DRAM: 128
MB
Flash: 64
MB
NAND: Manufacturer : Samsung
(0xec)
Device Code :0xd7
Cell Technology :
MLC
Chip Size : 4
GiB
Pages per Block :
128
Page Geometry :
4096+218
ECC Strength : 8
bits
ECC Size : 512
B
Data Setup Time : 20
ns
Data Hold Time : 10
ns
Address Setup Time: 25
ns
GPMI Sample Delay : 6
ns
tREA :
Unknown
tRLOH :
Unknown
tRHOH :
Unknown
Description :
K9LBG08U0D
Bad block table found at page 524160, version0x01
Bad block table found at page 524032, version0x01
2048
MiB
In:
serial
Out:
serial
Err:
serial
PMIC@0x08:0x7 is
45d0
i.MX35 CPU board version
2.0
Net: FEC0 Hit any key to stop autoboot: 0
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)
Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe: cfi_flash base: 0xa0000000 size: 0x04000000 mc13892-i2c@mc13892-i2c0: PMIC ID: 0x000045d0 [Rev: 2.0a]
smc911x: no smc911x found on 0xb6000000 (byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision: 0x45d0
i.MX35 PDK CPU board version 1.
Malloc space: 0x86f00000 -> 0x87f00000 (size 16 MB) Stack space : 0x86ef8000 -> 0x86f00000 (size 32 kB) Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment running /env/bin/init...
regards
Thomas
Am 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 12 lines · Thomas Mayer
Quoted 8 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 11 lines
Quoted 4 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Quoted 10 lines · Thomas Mayer
Hi Sasha,
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.
Quoted 8 lines
Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -Page Geometry :
4096+218
This will cause problems. I never had a nand with 4k block size and I doubt it will work out of the box. I don't know if that's the reason barebox does not find no nand device at all though.
Sasha
Quoted 57 lines
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe:cfi_flashbase:0xa0000000size:0x04000000mc13892-i2c@mc13892-i2c0: PMIC ID:0x000045d0[Rev: 2.0a]
smc911x: no smc911x found on0xb6000000(byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision:0x45d0
i.MX35 PDK CPU board version 1.
Malloc space:0x86f00000->0x87f00000(size 16 MB) Stack space :0x86ef8000->0x86f00000(size 32 kB) Open/dev/env0No such file or directory
no valid environment found on/dev/env0. Using default environment running /env/bin/init...regards
ThomasAm 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 12 lines · Thomas Mayer
Quoted 8 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 11 lines
Quoted 4 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hi Sascha, Thomas,
Quoted 15 lines · Sascha Hauer
Quoted 14 lines · Thomas Mayer
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -
Quoted 6 lines
Quoted 2 lines
Page Geometry :
4096+218This will cause problems. I never had a nand with 4k block size and I doubt it will work out of the box. I don't know if that's the reason barebox does not find no nand device at all though.
I'm also seeing problems with a 4k page size (+218 OOB) SLC NAND flash of Micron on i.MX25. Barebox does identify the flash chip, but can't read it correctly. I'm investigating the issue. So far I've found that the OOB area is read as 0x00s instead of 0xffs, even for good blocks. This makes Barebox to mark the whole flash as bad blocks.
The Linux kernel, however, seems to work correctly with this flash when applying a small fix to use the correct(?) nand_ecclayout.
baruch
Quoted 46 lines
Quoted 46 lines
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe:cfi_flashbase:0xa0000000size:0x04000000mc13892-i2c@mc13892-i2c0: PMIC ID:0x000045d0[Rev: 2.0a]
smc911x: no smc911x found on0xb6000000(byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision:0x45d0
i.MX35 PDK CPU board version 1.
Malloc space:0x86f00000->0x87f00000(size 16 MB) Stack space :0x86ef8000->0x86f00000(size 32 kB) Open/dev/env0No such file or directory
no valid environment found on/dev/env0. Using default environment running /env/bin/init...regards
ThomasAm 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 20 lines · Thomas Mayer
Quoted 8 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 4 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
Signature · 8 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [email protected] - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/bareboxHi Sascha, Thomas,
Quoted 23 lines · Baruch Siach
Quoted 15 lines · Sascha Hauer
Quoted 14 lines · Thomas Mayer
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -Quoted 6 lines
Quoted 2 lines
Page Geometry :
4096+218This will cause problems. I never had a nand with 4k block size and I doubt it will work out of the box. I don't know if that's the reason barebox does not find no nand device at all though.
Quoted 8 lines
I'm also seeing problems with a 4k page size (+218 OOB) SLC NAND flash of Micron on i.MX25. Barebox does identify the flash chip, but can't read it correctly. I'm investigating the issue. So far I've found that the OOB area is read as 0x00s instead of 0xffs, even for good blocks. This makes Barebox to mark the whole flash as bad blocks.
The Linux kernel, however, seems to work correctly with this flash when applying a small fix to use the correct(?)
nand_ecclayout.
I should also add the booting from this NAND with Barebox works perfectly. I used the kernel to program Barebox into the flash.
baruch
Quoted 46 lines
Quoted 46 lines
Quoted 46 lines
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe:cfi_flashbase:0xa0000000size:0x04000000mc13892-i2c@mc13892-i2c0: PMIC ID:0x000045d0[Rev: 2.0a]
smc911x: no smc911x found on0xb6000000(byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision:0x45d0
i.MX35 PDK CPU board version 1.
Malloc space:0x86f00000->0x87f00000(size 16 MB) Stack space :0x86ef8000->0x86f00000(size 32 kB) Open/dev/env0No such file or directory
no valid environment found on/dev/env0. Using default environment running /env/bin/init...regards
ThomasAm 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 20 lines · Thomas Mayer
Quoted 8 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 4 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
Signature · 8 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [email protected] - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/bareboxHi,
good know, I will try that.
regards
Thomas
Am 28.02.2011 09:19, schrieb Baruch Siach:
Quoted 35 lines
Hi Sascha, Thomas,
Quoted 31 lines · Baruch Siach
Quoted 16 lines · Sascha Hauer
Quoted 14 lines · Thomas Mayer
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -Quoted 7 lines
Quoted 3 lines
Page Geometry :
4096+218This will cause problems. I never had a nand with 4k block size and I doubt it will work out of the box. I don't know if that's the reason barebox does not find no nand device at all though.
I'm also seeing problems with a 4k page size (+218 OOB) SLC NAND flash of Micron on i.MX25. Barebox does identify the flash chip, but can't read it correctly. I'm investigating the issue. So far I've found that the OOB area is read as 0x00s instead of 0xffs, even for good blocks. This makes Barebox to mark the whole flash as bad blocks.
Quoted 62 lines
Quoted 3 lines
The Linux kernel, however, seems to work correctly with this flash when applying a small fix to use the correct(?)
nand_ecclayout.I should also add the booting from this NAND with Barebox works perfectly. I used the kernel to program Barebox into the flash.
baruch
Quoted 52 lines
Quoted 52 lines
Quoted 52 lines
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe:cfi_flashbase:0xa0000000size:0x04000000mc13892-i2c@mc13892-i2c0: PMIC ID:0x000045d0[Rev: 2.0a]
smc911x: no smc911x found on0xb6000000(byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision:0x45d0
i.MX35 PDK CPU board version 1.
Malloc space:0x86f00000->0x87f00000(size 16 MB) Stack space :0x86ef8000->0x86f00000(size 32 kB) Open/dev/env0No such file or directory
no valid environment found on/dev/env0. Using default environment running /env/bin/init...regards
ThomasAm 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 25 lines · Thomas Mayer
Quoted 10 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 5 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Hi Thomas,
Quoted 1 line · Thomas Mayer
good know, I will try that.
Further investigation shows that the Linux kernel doesn't read (or write) the OOB area correctly. This is not a problem if all you do is program the barebox image into the NAND flash. However, since the kernel uses the OOB area to identify the BBT (bad block table), the BBT gets corrupted. When that happens, the mxc_nand .probe fails at nand_scan_tail().
I suspect that the nandv2_hw_eccoob_largepage is wrong for 4K+218B. I'm still investigating.
baruch
Quoted 97 lines
Am 28.02.2011 09:19, schrieb Baruch Siach:
Quoted 96 lines
Hi Sascha, Thomas,
Quoted 25 lines · Baruch Siach
Quoted 16 lines · Sascha Hauer
Quoted 14 lines · Thomas Mayer
thanks, I will try that.
Today I got our real hardware. It consists of the freescale cpu board, a custom baseboard with a different display.
With that I was able to start barebox completely. Network works fine, but I can't access the nand memory, because barebox doesn't find it at startup. I added all possible nand drivers to barebox, but it still doesn't work.Any idea?
--------------------------------------- u-boot output
-----------------------------------------
U-Boot 2009.08 (Jan 13 2010 -Quoted 7 lines
Quoted 3 lines
Page Geometry :
4096+218This will cause problems. I never had a nand with 4k block size and I doubt it will work out of the box. I don't know if that's the reason barebox does not find no nand device at all though.
Quoted 9 lines
I'm also seeing problems with a 4k page size (+218 OOB) SLC NAND flash of Micron on i.MX25. Barebox does identify the flash chip, but can't read it correctly. I'm investigating the issue. So far I've found that the OOB area is read as 0x00s instead of 0xffs, even for good blocks. This makes Barebox to mark the whole flash as bad blocks.
The Linux kernel, however, seems to work correctly with this flash when applying a small fix to use the correct(?)
nand_ecclayout.I should also add the booting from this NAND with Barebox works perfectly. I used the kernel to program Barebox into the flash.
baruch
Quoted 52 lines
Quoted 52 lines
Quoted 52 lines
--------------------------------------- barebox output
------------------------------------------
barebox 2011.02.0 (Feb 25 2011 - 16:35:47)Board: Freescale MX35 3Stack
No NAND device found!!!cfi_probe:cfi_flashbase:0xa0000000size:0x04000000mc13892-i2c@mc13892-i2c0: PMIC ID:0x000045d0[Rev: 2.0a]
smc911x: no smc911x found on0xb6000000(byte_test=0x00f000f0) imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver mc13892-i2c@mc13892-i2c0: revision:0x45d0
i.MX35 PDK CPU board version 1.
Malloc space:0x86f00000->0x87f00000(size 16 MB) Stack space :0x86ef8000->0x86f00000(size 32 kB) Open/dev/env0No such file or directory
no valid environment found on/dev/env0. Using default environment running /env/bin/init...regards
ThomasAm 25.02.2011 16:06, schrieb Sascha Hauer:
Quoted 25 lines · Thomas Mayer
Quoted 10 lines
Hi Sascha,
That's not quite correct. When you use the debug + personality board you can boot directly from a mmc-card which contains bootloader, kernel and rootfs without modifications. Only if you use the single personality board, you have to modify die board a little bit.
Ah, ok. I didn't know that.
Quoted 5 lines
Thanks for your short introduction. I tried to run the barebox image with u-boot and it seems to work. But after I get the following output barebox stops and do nothing.
That's a bug in the support for multiple network devices. Please pull the -next branch again, then it should work.
Sascha
Signature · 8 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [email protected] - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox