Re: i.MX RT1050 toolchain
Giulio wrote… Perfect, I suggest you to test it on a EVK before than going with your custom board if you can, and after port your board, that should make it easier. I certainly will do! One supplementary question… what did you use U-Boot to boot? I’m looking to get uClinux running on it. As a starting point I have only been able to find the BSP from EmCraft[1] but at kernel version 4.5 it is quite old. -Andy. 1 - https://www.emcraft.com/products/979
Re: i.MX RT1050 toolchain
Giulio wrote... Is there a preferred / recommended toolchain for building U-Boot for the i.MX RT10xx platforms or should any recent ARM cross compiler work? It should compile fine with any recent ARM cross-compiler. Please let me know if it builds correctly I used the arm-linux-gnueabi-gcc v10.1.0 compiler available from www.kernel.org and it has built fine. Now I have a working toolchain I can start adding the new board. -Andy.
i.MX RT1050 toolchain
Hi Giulio, Is there a preferred / recommended toolchain for building U-Boot for the i.MX RT10xx platforms or should any recent ARM cross compiler work? -Andy.
Re: u-boot saveenv corrupted other MTD parttions
JH wrote... gpmi-nand:1m(boot),1m(ubootenv),-(storage) The saveenv does not take any parameters, how did it work to write to the NAND 1m(ubootenv)? => saveenv Saving Environment to NAND... Erasing NAND... Erasing at 0x5e -- 100% complete. Writing to NAND... OK It looks like that saveenv overwritten to the storage, is 0x5e RAM or NAND address? Where was that address defined? What U-Boot uses for the storage of the environment is controlled through configuration options. In recent versions this is all handled through the options defined in env/Kconfig. In older versions these may have been defined in the include/configs/myboardname.h file. CONFIG_ENV_IS_IN_NAND tells U-Boot that the environment is to be stored in the NAND flash device CONFIG_ENV_OFFSET defines how far into the NAND device the environment will be stored (in your case this is probably 0x5e) CONFIG_ENV_SIZE defines how big it is Your definition of the mtd partitions doesn’t match. Your “ubootenv" partition starts at offset 0x10 and your “storage” partition starts at offset 0x20. When you run the saveenv command you are writing somewhere in the middle of the “storage” partition. -Andy.
Re: Support UBI u-boot
JH wrote... I added NAND and UBIFS support to my Yocto layer machine config file: UBOOT_CONFIG = "nand" UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config" UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config" UBOOT_CONFIG[nand] += "ubi" UBOOT_CONFIG[nand] += "ubifs" But my u-boot.imx-nand still could not support ubi: => ubi part rootfs Unknown command 'ubi' - try ‘help’ You need to start to read through the various sources to figure out for yourself what is going on! Starting from the bottom, in U-Boot 2017.03 all of the command sources are in the “cmd” directory. The “ubi …” command are all in ubi.c. Reading cmd/Makefile shows that file gets added into the build if CONFIG_CMD_UBI is enabled. The next place to look is whether or not that is set in your defconfig for U-Boot or overwritten somewhere in a recipe in your Yocto build environment. -Andy.
[U-Boot] SAMA5D2x and falcon boot mode
Hello! Does anyone know if U-Boot for the Microchip (Atmel) SAMA5D2x devices supports the Falcon (SPL -> Linux) boot mode? -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] how many (few?) supported boards don't specify SYS_VENDOR?
Robert wrote... i'd never thought about it so, as a quick check, i just tried this to see how many board files actually lived directly under board// and got: $ ls board/*/board.c board/sunxi/board.c $ i thought that was interesting -- all of one board For most boards the primary source file is not called board.c but is .c. E.g. board/cobra5272/cobra5272.c -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] [PATCH] Enable expression support for CONFIG_BOARD_SIZE_LIMIT
Fabio wrote... $ /bin/sh --version /bin/sh: 0: Illegal option -- In my system /bin/sh points to bash: $ ls -al /bin/sh lrwxrwxrwx 1 root root 4 mai 2 2018 /bin/sh -> dash Just to pick up on the obvious… /bin/sh is showing as linked to dash not bash! Using (( … )) for arithmetic expansion is a bashism [1] [1] https://wiki.ubuntu.com/DashAsBinSh -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Booting into winCE .nb0 without access to source files
Michael wrote... I have an awkward situation, short of it is we have a custom i.MX53 board, the nk.nb0 and eboot.nb0 files to boot into windows (with no source code), and an Ubuntu VM with the source code and compiled files of uboot from august 2009 (as well as some flavour of linux that I'm not 100% sure on). I need to figure out a way to boot into either the nk.nb0 or eboot.nb0 so that we can run our software. eboot.nb0 is the Windows CE bootloader and probably needs to be executed first. The nk.nb0 file is the actual Windows CE image itself. Depending on the hardware configuration it may be that these are images that are copied as-is to RAM or could be XIP images for execution directly from flash if the hardware supports it and is configured that way. Based on my research so far, I am hopeful that I may be able to have uboot start either eboot.nb0 or nk.nb0, and it won't crash the hardware in the process (we don't have the resources to do more in depth troubleshooting of the board design or re-write our software for the linux version). This may not be successful. One or both of the .nb0 files will contain hardware initialisation code and it may be that the initialisation provided by U-Boot causes a conflict. If you want to contact me off list to discuss Windows CE specifics then we have the expertise to maybe help you move this forward. -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] hwmon in current uboot
Joe wrote... Apologies in advance if this is answered somewhere else, but I had no luck finding information about it. I'm moving from an older version of u-boot (2016) to a current one. Some of the patches I had against the old uboot included work in the hwmon subdirectory. These patches now obviously fail as this whole set of functionality appears to have been removed. Am I missing something, or does u-boot no longer support any of these devices? Alternatively, is there a way I should reintroduce it for my board. Looking at the git log for some of the files that were in the drivers/hwmon directory (git log — path/to/filename) then they were removed in May 2017 in favour of the driver model and UCLASS_THERMAL which is located in drivers/thermal. Unfortunately, it doesn’t look as though those I2C based devices got converted. -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] [PATCH v2 0/6] board: atmel: Add new board SAMA5D27-SOM1-EK board.
Wenyou wrote... > On 2017/7/31 14:57, Wenyou Yang wrote: > > The SAMA5D27-SOM1-EK board embeds a SAMA5D27 SOM1 module, which includes > > a SAMA5D27-SiP chip and QSPI flash, Phy and MAC EEPROM. The SAMA5D27 SiP > > integrates the SAMA5D2 with 1Gbit DDR2-SDRAM in a single package. > > It is based on > > 1./ [PATCH v2 0/8] sf: improve support of (Q)SPI flash memories > > https://lists.denx.de/pipermail/u-boot/2017-July/298806.html > > 2./ [PATCH v2 0/3] board: atmel: Set the ethernet mac address from > > eeprom > > https://lists.denx.de/pipermail/u-boot/2017-July/300527.html > > 3./ [PATCH 0/7] board: atmel: Convert to support DM_VIDEO > > https://lists.denx.de/pipermail/u-boot/2017-July/300533.html Do we assume that these aren't now going to make it into 2017.09 and we have to wait for the 2017.12 tagged release? -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] SAMA5D2 series
Hello Wenyou, We are looking at using one of the SAMA5D2 family in an upcoming design and I have a couple of questions... In a recent U-Boot patch set you mentioned the SAMA5D27 SOM1 SiP module. Is this something that is available yet as I can't find it on the Microchip website? If we choose to use the processor, memory, etc. as discrete devices is the boot process still AT91Bootstrap -> U-Boot -> Linux or does it now support U-Boot SPL and Falcon boot mode? The current mainline implementation of arch/arm/mach-at91/spl.c seems to suggest that booting from a QSPI device isn't supported. Which of the supported boot devices will give the fastest boot time? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] AM335x Falcon Mode
Heiko wrote... > > Thanks for the answer, I figured out what the problem is, in the fact I > > was using a zImage, using an uImage format solve the problem :-) > > It should maybe added to the documentation ;-) > > Patches are welcome! I don't know that part of the code well enough to know whether it is a bug that needs fixing so that it will support zImage files or whether, as Ayoub said, we just put in the docs that it doesn't! -Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] AM335x Falcon Mode
Ayoub wrote...
> => run args_mmc
> => run loadimage
> 8942296 bytes read in 610 ms (14 MiB/s)
> => run loadfdt
> 58129 bytes read in 56 ms (1013.7 KiB/s)
> => spl export fdt ${loadaddr} - ${fdtaddr}
I have AM335x Falcon mode running with SPI flash (albeit an old 2014.xx U-Boot
version) and the commands for settings it up look the same as the ones you have
used.
Do you get any more information about where the data abort is coming from if
you build and run U-Boot with #define DEBUG?
-Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] [PATCH v3 0/6] board: sama5d3: convert boards to support DM/DT
Wenyou Yang wrote... > The purpose of patch set is to convert the board to support device > tree and driver model, and enable the early debug UART as well. > It is based on the patch set: > [PATCH v8 0/2] pinctrl: at91: Add pinctrl driver > https://lists.denx.de/pipermail/u-boot/2017-March/284577.html I was going to test these out on my SAMA5D31EK but it appears to be bricked as the only output I get at power-on is a single "RomBOOT" and SAM-BA doesn't seem to want to connect. Is there any way I can de-brick the board so I can test these patches? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] [PATCH v3 2/2] rockchip: rk3288: use spl_early_init() instead of spl_init()
Simon wrote...
> diff --git a/arch/arm/mach-rockchip/rk3288-board-spl.c b/arch/arm/mach-
> rockchip/rk3288-board-spl.c
> index e51e19bb2d..f494843663 100644
> --- a/arch/arm/mach-rockchip/rk3288-board-spl.c
> +++ b/arch/arm/mach-rockchip/rk3288-board-spl.c
> @@ -185,7 +185,7 @@ void board_init_f(ulong dummy)
> debug_uart_init();
> #endif
>
> - ret = spl_init();
> + ret = spl_early_init();
> if (ret) {
> debug("spl_init() failed: %d\n", ret);
Shouldn't the function name used in the debug statement be changed to
spl_early_init()?
-Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] UBI issues with DM355 and Micron NAND flash
Hello,
I am working on an update to a Linux configuration for a custom TI DM355
based hardware platform which uses a Micron MT29F4G08ABADAWP NAND flash
device and U-Boot 2013.07 (which I can't change). The boards have been
deployed in the field over a number of years using the NAND flash to store
the Linux kernel and a CramFS partition and all works well with the
following settings in the board config file:
#define CONFIG_NAND_DAVINCI
#define CONFIG_SYS_NAND_CS 2
#define CONFIG_SYS_NAND_USE_FLASH_BBT
#define CONFIG_SYS_NAND_4BIT_HW_ECC_OOBFIRST
#define CONFIG_SYS_NAND_PAGE_2K
#define CONFIG_SYS_NAND_LARGEPAGE
#define CONFIG_SYS_NAND_BASE_LIST { 0x0200, }
#define CONFIG_SYS_MAX_NAND_DEVICE 1
#define CONFIG_SYS_NAND_MAX_CHIPS 1
As part of the update we are moving to a UBI root file system and this is
where problems are starting. As an initial test I am using the following
commands in U-Boot to create the UBI partition:
U-Boot> nand erase.part rootfs
U-Boot> ubi part rootfs
All appears to be well but if I reset the hardware and then rerun the "ubi
part rootfs" command then I am bombarded with errors of the following type
which never seem to end but just change in the PEB being referenced:
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 0:0, read
64 bytes
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 0:512,
read 512 bytes
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1:0, read
64 bytes
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 1:512,
read 512 bytes
The datasheet for the flash device says that in 8-bit mode a page size is
2048 + 64 bytes and as far as I can tell doesn't mention subpages and so I
am confused by the output from the "ubi part rootfs" command that states
that there are 512 byte sub-pages available:
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
I have had a look through the source but can't find anyway to disable
sub-page support or to tell it that a sub-page is the same size as the
smallest flash I/O unit. Then again, I could be looking in completely the
wrong place.
Any thoughts...
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode for TI DM355
Hi Tom, > So, git commit 6761946f is what removed the board in question. Now, > looking in mainline today (and also looking at 6761946f) I see that we > had and have support for CONFIG_TARGET_OMAPL138_LCDK and that uses SPL > which is a prerequisite for falcon mode. So there's nothing too low > level that would need to be done for the DM355, just the board specific > portions. The current implementation for the target hardware is based on 2013.07. Can we make it work with that or should we look to move to something more recent? Not wanting to make too many changes unnecessarily. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Falcon mode for TI DM355
Hello TI experts, I appreciate that all of the TI DM355 support long since (August 2015) landed in the great board scrap yard in the sky or wherever it is git chooses to hide it! I may have an upcoming project to reduce boot time on a pre-existing custom platform using the DM355 and wondered if anyone had implemented SPL and Falcon mode for it that didn't make it into mainline or whether this is actually possible at all for this device? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 1/3] x86: ifdtool: Support checking region overlap before U-Boot
Bin wrote... We have the capability to check regions written after U-Boot that do not overlap. Since regions can also be written before U-Boot, add such check for these too. Signed-off-by: Bin Meng bmeng...@gmail.com --- This fixes the issue I raised this morning with building the .rom file for Galileo with the latest master, so: Tested-by: Andy Pont andy.p...@sdcsystems.com Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ROM build failure on Galileo
Hi Bin, Please check http://patchwork.ozlabs.org/patch/511333/ which should fix this issue. The compilation of the .rom file for Galileo now succeeds with the application of this patch. Not sure this is the official and proper way to do it but: Tested-by: Andy Pont andy.p...@sdcsystems.com Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] ROM build failure on Galileo
Hello, Following the latest merges to the Master branch the ROM build now appears to fail on Galileo (built with gcc v4.8.4). The build output terminates with: OBJCOPY u-boot.srec OBJCOPY u-boot.bin OBJCOPY u-boot-x86-16bit.bin CAT u-boot-dtb.bin IFDTOOL u-boot.rom U-Boot image overlaps with region './board/intel/galileo/rmu.bin' U-Boot finishes at offset 7025a, file starts at 0 make: *** [u-boot.rom] Error 1 Any ideas why? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [ANN] git server, FTP server
Wolfgang wrote...
{snip}
2. For some time now, we provide not only the classic FTP server for
download of the U-Boot release tarballs, but also a public
directory in the Amazon Cloud Drive [1]. The ACD is supposed to
provide much better connectivity (especially for non-european
users) and much higher download rates.
So far, I have received zero feedback about this. I would like to
hear about your experiences (good and bad), and what you think
about dropping the FTP server completely.
Today it took about 5 seconds of manual effort to copy the classic FTP URL
from the announce email and use it with wget which then took just under 6
seconds to download it.
So far, two attempts at using the Amazon Cloud web interface have failed.
Clicking on the Download button result in the message Download starting
but no file appears. It is probably just Chrome being a PITA but I know
which one currently gets my vote!
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 09/11] dma: ti-edma3: Add BIT(x) macro definition
Vignesh wrote... [snip] +#define BIT(x) (1 (x)) + Is this not something that would be better in a global header file somewhere rather than it starting a trend of a per-driver, per-arch, etc. definitions? Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] mx6_common: Fix LOADADDR and SYS_TEXT_BASE for MX6SL and MX6SX
Hello, [snip] #ifndef CONFIG_SYS_TEXT_BASE -#define CONFIG_SYS_TEXT_BASE 0x1780 #endif Doesn't this also leave an empty, and therefore meaningless #ifndef...#endif that could be removed completely? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] x86: Fix regression build issue of coreboot-x86_defconfig
Hi Bin, I just found u-boot.rom created from u-boot-x86/testing branch does not have working network any more on QEMU. It is working on the u-boot-x86/master branch. = set serverip 10.10.0.100;set ipaddr 10.10.0.108;set netmask 255.255.255.0;set gatewayip 10.10.0.100 = run ramboot *** ERROR: `serverip' not set *** ERROR: `serverip' not set But 'print' says the env indeed has the 'serverip'. I think there should be something in the upstream that caused this after the u-boot-x86/testing branch rebase. Do you know where might be the problem? This looks very similar to an issue that got patched on the i.MX6 yesterday by Stefano which said: commit fd3056337e6fcc140f400e11edd33f6f1cb37de1 Use env callbacks for net variables has a side effect on i.MX6 boards because they do not set CONFIG_NET: the ip address results not set, but it is stored in the environment. Might be something to check... Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v3 4/4] x86: minnowmax: initialize the pin-muxing from device tree
Hi Gabriel,
soc_gpio_s5_0@0 {
gpio-offset = 0x80 0;
pad-offset = 0x1d0;
mode-gpio;
output-value = 0;
direction = PIN_OUTPUT;
};
soc_gpio_s5_1@0 {
gpio-offset = 0x80 1;
pad-offset = 0x210;
mode-gpio;
output-value = 0;
direction = PIN_OUTPUT;
};
soc_gpio_s5_2@0 {
gpio-offset = 0x80 2;
pad-offset = 0x1e0;
mode-gpio;
output-value = 0;
direction = PIN_OUTPUT;
};
And after, you can use the GPIO commands:
= gpio set E0
gpio: pin E0 (gpio 128) value is 1
= gpio clear E0
gpio: pin E0 (gpio 128) value is 0
= gpio set E2
gpio: pin E2 (gpio 130) value is 1
= gpio clear E2
gpio: pin E2 (gpio 130) value is 0
E0 E1 and E2 correspond to the GPIO0 1 and 2.
Is there, or can someone add, some documentation somewhere as to how to
convert between the device tree definition and the value used for pin in
the gpio commands as it doesn't seem intuitive or obvious to me that what
you have defined translates to E0, E1 and E2.
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Quark compile errors
Hi Bin,
Can you post your full configuration here?
I have attached the autoconf.mk and U-Boot .config files. Hopefully they tell
you what you need.
Also, if anyone can tell me what $TERM setting I need to get the rogue b
characters to actually display bold/bright then that would be great too!
I am using xterm, not sure if this helps.
$ echo $TERM
xterm
That is what I have too. I guess it might be down to the way SecureCRT is
interpreting what it is being sent rather than the Linux machine itself.
Regards,
Andy.
CONFIG_PHYSMEM=y
CONFIG_SPI_FLASH_WINBOND=y
CONFIG_CMD_FAT=y
CONFIG_MMC_SDMA=y
CONFIG_SHOW_BOOT_PROGRESS=y
CONFIG_DESIGNWARE_ETH=y
CONFIG_X86_OPTION_ROM_FILE=sm750.bin
CONFIG_BOOTM_NETBSD=y
CONFIG_SYS_ISA_IO_BASE_ADDRESS=0
CONFIG_BOARD_EARLY_INIT_F=y
CONFIG_CMD_ITEST=y
CONFIG_CMD_FPGA_LOADMK=y
CONFIG_BOOTM_VXWORKS=y
CONFIG_X86_SERIAL=y
CONFIG_CMD_EDITENV=y
CONFIG_CMD_PART=y
CONFIG_CMD_ENV_EXISTS=y
CONFIG_SYS_LONGHELP=y
CONFIG_CMD_ZBOOT=y
CONFIG_SYS_LOAD_ADDR=0x2000
CONFIG_SYS_SCSI_MAX_SCSI_ID=2
CONFIG_CMD_XIMG=y
CONFIG_TPM=y
CONFIG_SPI_FLASH=y
CONFIG_SYS_HELP_CMD_WIDTH=8
CONFIG_PCI_PREF_SIZE=0x2000
CONFIG_NR_DRAM_BANKS=y
CONFIG_EFI_PARTITION=y
CONFIG_FS_FAT=y
CONFIG_BOOTM_RTEMS=y
CONFIG_SYS_CBSIZE=512
CONFIG_SYS_MONITOR_LEN=(1 20)
CONFIG_SDHCI=y
CONFIG_BOOTM_LINUX=y
CONFIG_DW_ALTDESCRIPTOR=y
CONFIG_CMD_CONSOLE=y
CONFIG_MMC=y
CONFIG_ROOTPATH=/opt/nfsroot
CONFIG_CMD_MISC=y
CONFIG_FIT=y
CONFIG_ENV_OFFSET=0
CONFIG_USB_MAX_CONTROLLER_COUNT=2
CONFIG_ENV_OVERWRITE=y
CONFIG_CMD_NET=y
CONFIG_ZBOOT_32=y
CONFIG_ENV_SIZE=0x01000
CONFIG_CMD_PING=y
CONFIG_SYS_MALLOC_LEN=0x20
CONFIG_TPM_TIS_BASE_ADDRESS=0xfed4
CONFIG_SYS_BOOTM_LEN=(16 20)
CONFIG_ATAPI=y
CONFIG_CMD_SAVEENV=y
CONFIG_ICH_SPI=y
CONFIG_ENV_SECT_SIZE=0x1000
CONFIG_MD5=y
CONFIG_BOOTM_PLAN9=y
CONFIG_SYS_64BIT_LBA=y
CONFIG_SYS_CONSOLE_INFO_QUIET=y
CONFIG_STD_DEVICES_SETTINGS=stdin=vga,serial0stdout=vga,serial0stderr=vga,serial0
CONFIG_SYS_X86_TSC_TIMER=y
CONFIG_BOOTARGS=root=/dev/sdb3 init=/sbin/init rootwait ro
CONFIG_CMD_MEMORY=y
CONFIG_SYS_MAXARGS=16
CONFIG_CMD_RUN=y
CONFIG_SYS_PBSIZE=(CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16)
CONFIG_DISPLAY_BOARDINFO_LATE=y
CONFIG_PCI_IO_PHYS=$(CONFIG_PCI_IO_BUS)
CONFIG_BOOTP_HOSTNAME=y
CONFIG_BOARDDIR=board/siliconmotion/osprey
CONFIG_PCI_MEM_BUS=0x9000
CONFIG_SYS_USB_EVENT_POLL=y
CONFIG_CRC32=y
CONFIG_CMD_GETTIME=y
CONFIG_OF_LIBFDT=y
CONFIG_SUPPORT_VFAT=y
CONFIG_PCI_MEM_PHYS=$(CONFIG_PCI_MEM_BUS)
CONFIG_PHYLIB=y
CONFIG_INTEL_ICH6_GPIO=y
CONFIG_CMDLINE_EDITING=y
CONFIG_CMD_USB=y
CONFIG_SYS_CONSOLE_IS_IN_ENV=y
CONFIG_CMD_EXT2=y
CONFIG_CMD_EXT4=y
CONFIG_USB_EHCI=y
CONFIG_BOOTCOMMAND=ext2load scsi 0:3 0100 /boot/vmlinuz; zboot 0100
CONFIG_ISO_PARTITION=y
CONFIG_CMD_SETGETDCR=y
CONFIG_SYS_BOOT_RAMDISK_HIGH=y
CONFIG_LOADADDR=0x100
CONFIG_LIB_UUID=y
CONFIG_BOOTP_BOOTFILESIZE=y
CONFIG_CMD_BOOTD=y
CONFIG_SYS_NS16550=y
CONFIG_CMD_IO=y
CONFIG_SYS_STDIO_DEREGISTER=y
CONFIG_CMD_SF_TEST=y
CONFIG_SYS_BARGSIZE=$(CONFIG_SYS_CBSIZE)
CONFIG_AUTO_COMPLETE=y
CONFIG_CONSOLE_MUX=y
CONFIG_SYS_SCSI_MAX_LUN=y
CONFIG_DOS_PARTITION=y
CONFIG_COMMAND_HISTORY=y
CONFIG_TPM_TIS_LPC=y
CONFIG_CMD_SF=y
CONFIG_USB_ETHER_SMSC95XX=y
CONFIG_CMD_FPGA=y
CONFIG_I8042_KBD=y
CONFIG_SYS_BAUDRATE_TABLE={300, 600, 1200, 2400, 4800, 9600, 19200, 38400,
115200}
CONFIG_USB_EHCI_PCI=y
CONFIG_SYS_HUSH_PARSER=y
CONFIG_VIDEO=y
CONFIG_IMAGE_FORMAT_LEGACY=y
CONFIG_SYS_PCAT_INTERRUPTS=y
CONFIG_CFB_CONSOLE=y
CONFIG_RAMBOOTCOMMAND=setenv bootargs root=/dev/ram rw
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftpboot $loadaddr
$bootfile;tftpboot $ramdiskaddr $ramdiskfile;zboot $loadaddr 0 $ramdiskaddr
$filesize
CONFIG_SYS_USB_EHCI_MAX_ROOT_PORTS=12
CONFIG_CMD_SPI=y
CONFIG_CMD_DHCP=y
CONFIG_USB_ETHER_ASIX=y
CONFIG_CMD_ECHO=y
CONFIG_GENERIC_MMC=y
CONFIG_CMD_CBFS=y
CONFIG_SYS_SCSI_MAX_DEVICE=(CONFIG_SYS_SCSI_MAX_SCSI_ID *
CONFIG_SYS_SCSI_MAX_LUN)
CONFIG_HOSTNAME=x86
CONFIG_LAST_STAGE_INIT=y
CONFIG_CMD_TIME=y
CONFIG_BOOTP_GATEWAY=y
CONFIG_SYS_MONITOR_BASE=$(CONFIG_SYS_TEXT_BASE)
CONFIG_EXTRA_ENV_SETTINGS=CONFIG_STD_DEVICES_SETTINGS
netdev=eth00consoledev=ttyS00othbootargs=acpi=off0ramdiskaddr=0x2000ramdiskfile=initramfs.gz0
CONFIG_BOOTFILE=bzImage
CONFIG_TFTP_TSIZE=y
CONFIG_SYS_STACK_SIZE=(32 * 1024)
CONFIG_BAUDRATE=115200
CONFIG_PARTITION_UUIDS=y
CONFIG_ENV_IS_IN_SPI_FLASH=y
CONFIG_PCI_IO_SIZE=0xe000
CONFIG_SPI_FLASH_GIGADEVICE=y
CONFIG_SYS_NUM_IRQS=16
CONFIG_CMD_PCI=y
CONFIG_USB_HOST_ETHER=y
CONFIG_PARTITIONS=y
CONFIG_PCI_PREF_PHYS=$(CONFIG_PCI_PREF_BUS)
CONFIG_SYS_MEMTEST_END=0x0100
CONFIG_CONSOLE_SCROLL_LINES=5
CONFIG_PCI_MEM_SIZE=0x2000
CONFIG_CMD_ELF=y
CONFIG_LIBATA=y
CONFIG_RTC_MC146818=y
CONFIG_MAC_PARTITION=y
CONFIG_CMD_DATE=y
CONFIG_SYS_NO_FLASH=y
CONFIG_SYS_DEF_EEPROM_ADDR=0
CONFIG_FS_EXT4=y
CONFIG_SPI=y
CONFIG_SYS_EARLY_PCI_INIT=y
CONFIG_X86_OPTION_ROM_ADDR=0xfff9
CONFIG_VIDEO_SW_CURSOR=y
CONFIG_CMD_SOURCE=y
Re: [U-Boot] [PATCH 2/4] x86: Document irq router device tree bindings
Hi Bin, + pci: IRQ routing is controlled by PCI configuraiton registers ^^^ One small typo to correct. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Quark compile errors
Hello, I am trying to create a configuration for the Silicon Motion Osprey board which is a Quark SoC and their SM750 graphics controller. I have cloned the Intel Galileo files and changed them accordingly and have defined the options for the VBIOS for the graphics controller but when I try to compile I get the following build failure: CC arch/x86/lib/bios.o arch/x86/lib/bios.c: In function bint_exception_handlerb: arch/x86/lib/bios.c:61: error: unknown field beaxb specified in initializer arch/x86/lib/bios.c:61: warning: missing braces around initializer arch/x86/lib/bios.c:61: warning: (near initialization for breg_info.anonymousb) arch/x86/lib/bios.c:62: error: unknown field becxb specified in initializer arch/x86/lib/bios.c:63: error: unknown field bedxb specified in initializer arch/x86/lib/bios.c:64: error: unknown field bebxb specified in initializer arch/x86/lib/bios.c:65: error: unknown field bespb specified in initializer arch/x86/lib/bios.c:66: error: unknown field bebpb specified in initializer arch/x86/lib/bios.c:67: error: unknown field besib specified in initializer arch/x86/lib/bios.c:68: error: unknown field bedib specified in initializer make[1]: *** [arch/x86/lib/bios.o] Error 1 Could you advise what setting I have missed that is causing this build issue or is it the case that the bios.c file is defined for x86 capabilities beyond those of Quark? Also, if anyone can tell me what $TERM setting I need to get the rogue b characters to actually display bold/bright then that would be great too! Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Quark compile errors
Hi Bin, BTW, so you are working on this board? http://www.siliconmotion.com/EW_Pages/Osprey.html Looks like a quark based board with graphics support! Are you planning to submit patches to enable it? It is indeed for one of those boards, as an off-radar task to get my head back into x86 after lots of time spent playing with ARM! At the moment I am still waiting for some physical hardware but once I have some and have tested everything then yes, I will submit the patches for it. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Quark compile errors
Hi Simon, I am using xterm, not sure if this helps. $ echo $TERM xterm That is what I have too. I guess it might be down to the way SecureCRT is interpreting what it is being sent rather than the Linux machine itself. You might be able to set that terminal program to support 'xterm' emulation, or perhaps change TERM to whatever it does support. I have figured this bit out... By default the terminal emulation in SecureCRT is set to strip the 8th bit of the data it receives. Having set it to use the 8th bit and also to interpret things with UTF-8 encoding all is good with the world. Turns out that they aren't commands for bold/bright as I thought, they are in fact the leading and trailing single quotes around the error. Now to try and fix the issue with the code not building... Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Quark compile errors
Hi Bin, Can you post your full configuration here? I have attached the autoconf.mk and U-Boot .config files. Hopefully they tell you what you need. Looks OK. What gcc version are you using? It seems that your compiler does not understand the macro DOWNTO8 and DOWNTO16 in arch/x86/lib/bios.h It is using the standard version of gcc that comes as part of the CentOS 6.6 installation which is 4.4.7. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Quark compile errors
Hi Bin, It is using the standard version of gcc that comes as part of the CentOS 6.6 installation which is 4.4.7. I have been using 4.6.1 and 4.7.2, and both work. Can you please try some newer gcc? Good call. Having found a gcc version 4.8.4 then it has all compiled successfully! Thanks for your help! Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v2] spi: omap3: Fix timeout handling
Hi David,
snipped for brevity
for (i = 0; i len; i++) {
/* wait till TX register is empty (TXS == 1) */
+ start = get_timer(0);
while (!(readl(ds-regs-channel[ds-slave.cs].chstat)
OMAP3_MCSPI_CHSTAT_TXS)) {
- if (--timeout = 0) {
+ if (get_timer(start) SPI_WAIT_TIMEOUT) {
printf(SPI TXS timed out, status=0x%08x\n,
readl(ds-regs-channel[ds-
slave.cs].chstat));
return -1;
I have a couple of questions...
Firstly, when in SPL is there access to the get_timer() function?
Secondly, when using Falcon mode to load Linux directly from SPI (Falcon
mode) then we want to maximise the throughput and save every CPU cycle we
possibly can. Adding yet another function call into the for loop and hence
calling it a couple of million times seems, on the face of it, like it is
going to slow things down.
Regards,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Kernel to U-boot messaging and vice versa.
Dev wrote... I am new to U-boot development. We are using U-Boot 1.1.4 on a MIPS 74Kc QCA 9557 processor, which is running Linux Kernel 2.6.32.27. Is there a reason why you have to be running a kernel from 2010 and a version of bootloader that is even older? It makes life much easier to provide support if you can update to more recent versions and you never know they may already have fixed your problems! We have a situation were our firmware keeps hanging due to some issues. What is your firmware in this context? As you rightly said, once the Linux kernel is running U-Boot is no more and if U-Boot is hanging then you aren't going to get to the kernel anyway! We are looking into a solution where U-boot and Kernel keep communicating with each other every some minutes. If U-boot finds that there is no communication, it will reset the board. This sounds like it is the territory of watchdog timers. I don't know that CPU to know whether it has one built in though, nor if the kernel supports it. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Automatic download and flash programming with UART boot
Hello, The documentation [1] for the AM335x defines a manual process for UART booting as including the steps... When '' appear select XMODEM - Send u-boot-spl.bin, and then... When '' appear select YMODEM - Send u-boot.img Is there a pre-existing tool or script around that will automate this process which can then be used with a U-Boot debrick script to program the on-board flash devices? Thanks, Andy. [1] http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Unused video drivers
Hi Nikita, CONFIG_EXYNOS_PWM_BL CONFIG_L5F31188 CONFIG_SED156X CONFIG_VIDEO_COREBOOT CONFIG_VIDEO_IMX25LCDC CONFIG_VIDEO_SED13806 CONFIG_VIDEO_SMI_LYNXEM CONFIG_AM335X_LCD I believe that Hannes Petermaier recently posted some board updates that use the CONFIG_AM335X_LCD option and I guess they are still under review and haven't been merged yet. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] omap3_spi performance issues
Hello (and a belated happy new year to all),
I am working on a custom hardware platform where I need to pull the Linux
kernel from a Spansion SPI NOR flash device connected to a 600MHz TI AM3354
processor. The McSPI is configured to run at its maximum speed with a 48MHz
clock and the datasheet for the S25FL164K states that the throughput for a
read with a 50MHz clock rate should be 6.25MB/s.
Running the command time sf read ${loadaddr} 0x0020 ${loadsize} gives
the following output:
SF: 2900472 bytes @ 0x20 Read: OK
time: 1.676 seconds
This equates to around 1.7MB/s which I have managed to achieve principally
by adding the OMAP3_MCSPI_CHCONF_TURBO flag to the channel configuration but
also by moving things out of the read loop that only need to be performed
once rather than for each byte read.
Does anyone have any idea as to whether there is more performance that can
be got from this or is that about the limit?
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode boot support
Hi Tom, I suspect that this might be related to the general problem on these part families where SPL isn't as fast as we expect it to be, perhaps cache related. I did a bit of digging around following this line of thought and found an old discussion on the mailing list (http://lists.denx.de/pipermail/u-boot/2013-June/156949.html) regarding someone who had a very similar problem with SPL/Falcon and NAND flash. I have emailed Bas van den Berg to see if he is willing to share his final implementation as adding the code that adds the SRAM to the MMU and enables the caches to the end of am33xx_spl_board_init() hangs within the enable_caches() function. Unfortunately this getting well out of my comfort zone with the ARM cores and so I'm not sure where to go next and how to debug it further. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode boot support
Hi Tom,
Following the experiment that yielded the following results:
U-Boot time sf read ${loadaddr} 0x20 ${loadsize}
I get the following back:
SF: 2541352 bytes @ 0x20 Read: OK
time: 2.447 seconds
I have done some reading and poking around and have added the
OMAP3_MCSPI_CHCONF_TURBO flag to the SPI channel enablement in the
omap3_spi_read() function within omap3_spi.c and now the same command takes
1.279 seconds to execute.
I have also added a couple of printf() statements around the call to read
the flash device that loads the kernel image in spi_load_image_os() and the
timestamps on the output to the serial console consistently show that it is
taking around 3.5 seconds to load the same kernel image.
I haven't fully looked into what is going on as I haven't yet found the full
call path from spi_flash_read() in spi_flash.h to when it eventually results
in the call to omap3_spi_read() and so it may be doing more and I'm not
actually comparing apples with apples.
Could you (or maybe Jagannadha as SPI custodian) point me in the right
direction?
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode boot support
Hi Tom, How big is the args file? We default to placing the args at 0x8800 in ti_am335x_common.h (see CONFIG_SYS_SPL_ARGS_ADDR) to make sure that we don't have an overlap between the DT and the kernel which is quite possible with a reasonably sized DT and placing it at 0x8100. Changing the CONFIG_SYS_SPL_ARGS_ADDR to be the same as the value in the ti_ am335x_common.h header file seems to have fixed the issue. Unfortunately it hasn't improved the boot time by much - the bulk of the time seems to be in reading and decompressing the kernel from SPI flash device (Spansion S25FL164). The only other storage medium on the board is an eMMC flash device - would putting the kernel in there give a faster boot time? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode boot support
Hi Tom,
eMMC is likely to be faster, yes. You may also want to see what can be
trimmed from the kernel binary, in either case, and if going with an
uncompressed kernel ends up being quicker.
There are I think two issues going on here one with decompression time
which, as you say, I can resolve by using an uncompressed kernel. The other
is with the SPI transfer time and some testing has shown that if I boot to
U-Boot and then run:
U-Boot time sf read ${loadaddr} 0x20 ${loadsize}
I get the following back:
SF: 2541352 bytes @ 0x20 Read: OK
time: 2.447 seconds
The Spansion datasheet states that in read mode it can transfer 6.25Mbytes/s
in standard read mode at 50MHz clock. I have the clock at 40MHz as the
device on the other SPI interface won't support anything faster.
When I tested this on the Starter Kit reference board and again on the
target hardware I had to increase the value of SPI_WAIT_TIMEOUT in
driver/spi/omap3_spi.c from 300 by adding an extra '0' in order to stop
getting read failures with sf read commands with more than about 2MB of
data as per the discussion on the TI E2E community here:
http://e2e.ti.com/support/arm/sitara_arm/f/791/p/366019/1293837.aspx#1293837
.
Regards,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Falcon mode boot support
Hello,
I am currently setting up the Falcon mode support for a custom AM3354 based
platform that has U-Boot and the Linux kernel in an SPI NOR flash.
Following the instructions I have loaded the kernel to ${loadaddr} and
device tree to ${fdtaddr} from the SPI flash device and then have run:
U-Boot spl export fdt ${loadaddr} - ${fdtaddr}
Which seems to have executed correctly as the output ends:
Argument image is now in RAM: 0x8fb3d000
I now need to save this generated data into the SPI ROM but can't figure out
how much I need to write. Could someone let me know how to work it out?
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Falcon mode boot support
Hi Tom, So first, take a look at drivers/mtd/spi/spi_spl_load.c as that's what will be doing falcon mode work on your SPI flash. Second, take a look at board/ti/am335x/README, you're looking for the lines that read like: Using Device Tree in place at 80f8, end 80f85928 I have managed to make some progress and I think I have got what I think is the right data stored in the flash. Unfortunately when I try to boot it locks up at: spl: payload image: Linu load addr: 0x80007fc0 size: 3893360 Jumping to Linux Entering kernel arg pointer: 0x8100 I'm guessing the kernel arg pointer value is incorrect either that or it has ignored the boot arguments and not picked up the console parameter. Could you advise? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Controlling write protect pin on SPI flash
Hello, Is there, or is anyone working on, code for controlling the write protect pin of SPI flash devices using a GPIO? In effect an sf protect on|off command? I have had a look in 2014.07 which is on the platform we are using but can't see anything. Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] AM335x Ethernet pin mux confusion
Hello Mugunthan, There is no relation between pinmux and phy attached to the slave. Is your cpsw slave structures are populated with proper phy ids? Thanks for giving me the steer on this. I hadn't updated the slave structure. Having updated the slave structure it is now correctly detecting both PHYs and I can communicate with the network. :-) Now to fix all the issues I am having with the Linux kernel... Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Bare x86 support is merged to u-boot-x86
Hi Simon (and Bin), I've applied the remaining x86 patches to u-boot-x86. It runs on chromebook_link (Pixel) with support for most hardware relevant to a boot loader: SDRAM, SPI, PCI, USB (and USB Ethernet), SATA (internal 32GB SSD), SD card, LCD, UART, keyboard, EC. Bin this should be a good base for you to send patches for your Atom platform and I have no major work pending now so should not get in your way. Thanks for all of your efforts on getting some x86 support into U-Boot. Hopefully in the new year when project work is back under control I will have some time to get involved with this - I have almost 20 years experience porting commercial BIOS and UEFI solutions for x86 hardware and possibly a bunch of Atom C2750 hardware arriving in January. Other than the list of missing features, what are your long term goals/ambitions/desires with x86 support in U-Boot? From what I can see on the Coreboot mailing list it isn't the friendliest of people and doesn't seem to know how to deal with the binary blobs that both Intel and AMD seem to mandate for their chipsets now. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] AM335x Ethernet pin mux confusion
Hello,
I am working on porting U-Boot 2014.07 to a custom TI AM3354 based hardware
platform and am confused trying to set the pin mux for the two Ethernet
interfaces that are on the board.
RGMII1_ pins are connected to an ATHEROS AR8031 PHY (PHY ADDR 04) and the
pins GPMC_A0 .. GPMC_A11 are connected to a Micrel KSZ8041NL (PHY ADDR 01).
The output of the mii info command looks OK so the MDIO interface looks to
be OK as it gives:
PHY 0x00: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX
PHY 0x01: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX
PHY 0x04: OUI = 0x1374, Model = 0x07, Rev = 0x04, 1000baseX, FDX
However, with debug enabled, it is reporting the PHYs incorrectly as it
gives:
cpsw connected to Micrel KSZ804
cpsw connected to Micrel KSZ804
cpsw
The AR8031 provides a connection to the outside world and the KSZ8041
connects to an Ethernet switch which then connects on to other devices on
the board to form a private network. The DHCP command just sits in a loop
waiting for PHY auto negotiation to complete but timing out!
In the SPL code I am setting up the pin mux as follows:
static struct module_pin_mux rgmii1_pin_mux[] = {
{OFFSET(mii1_txen), MODE(2)}, /* RGMII1_TCTL */
{OFFSET(mii1_rxdv), MODE(2) | RXACTIVE},/* RGMII1_RCTL */
{OFFSET(mii1_txd3), MODE(2)}, /* RGMII1_TD3 */
{OFFSET(mii1_txd2), MODE(2)}, /* RGMII1_TD2 */
{OFFSET(mii1_txd1), MODE(2)}, /* RGMII1_TD1 */
{OFFSET(mii1_txd0), MODE(2)}, /* RGMII1_TD0 */
{OFFSET(mii1_txclk), MODE(2)}, /* RGMII1_TCLK */
{OFFSET(mii1_rxclk), MODE(2) | RXACTIVE}, /* RGMII1_RCLK */
{OFFSET(mii1_rxd3), MODE(2) | RXACTIVE},/* RGMII1_RD3 */
{OFFSET(mii1_rxd2), MODE(2) | RXACTIVE},/* RGMII1_RD2 */
{OFFSET(mii1_rxd1), MODE(2) | RXACTIVE},/* RGMII1_RD1 */
{OFFSET(mii1_rxd0), MODE(2) | RXACTIVE},/* RGMII1_RD0 */
{OFFSET(mdio_data), MODE(0) | RXACTIVE | PULLUP_EN}, /* MDIO_DATA
*/
{OFFSET(mdio_clk), MODE(0) | PULLUP_EN},/* MDIO_CLK */
{-1},
};
static struct module_pin_mux rmii2_pin_mux[] = {
{OFFSET(gpmc_a0), MODE(2)}, /* RMII2_TXEN */
{OFFSET(gpmc_a1), MODE(2) | RXACTIVE}, /* RMII2_RXDV */
{OFFSET(gpmc_a2), MODE(2)}, /* RMII2_TXD3 */
{OFFSET(gpmc_a3), MODE(2)}, /* RMII2_TXD2 */
{OFFSET(gpmc_a4), MODE(2)}, /* RMII2_TXD1 */
{OFFSET(gpmc_a5), MODE(2)}, /* RMII2_TXD0 */
{OFFSET(gpmc_a6), MODE(2)}, /* RMII2_TXCLK */
{OFFSET(gpmc_a7), MODE(2) | RXACTIVE}, /* RMII2_RXCLK */
{OFFSET(gpmc_a8), MODE(2) | RXACTIVE}, /* RMII2_RXD3 */
{OFFSET(gpmc_a9), MODE(2) | RXACTIVE}, /* RMII2_RXD2 */
{OFFSET(gpmc_a10), MODE(2) | RXACTIVE}, /* RMII2_RXD1 */
{OFFSET(gpmc_a11), MODE(2) | RXACTIVE}, /* RMII2_RXD0 */
{OFFSET(mdio_data), MODE(0) | RXACTIVE | PULLUP_EN}, /* MDIO_DATA */
{OFFSET(mdio_clk), MODE(0) | PULLUP_EN},/* MDIO_CLK */
{-1},
};
Any help would be much appreciated?
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Linker errors with SPL and FAT
Hello, I am trying to build U-Boot SPL (2014.07) for a custom TI AM3354 based board with MMC support. Mostly I have cloned the settings from the am335x_evm.h config file but am getting linker errors with SPL... common/spl/built-in.o: In function `spl_register_fat_device': .../common/spl/spl_fat.c:28: undefined reference to `fat_register_device' common/spl/built-in.o: In function `spl_load_image_fat': .../common/spl/spl_fat.c:55: undefined reference to `file_fat_read' .../common/spl/spl_fat.c:61: undefined reference to `file_fat_read' When I look at spl/fs/built-in.o it is 257 bytes and spl/fs/fat/built-in.o is 8 bytes. I have been staring at this for most of the morning and would appreciate it if someone could tell me what option I am missing. Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Device tree for Atmel SAMA5D31
This isn't strictly a U-Boot issue but I am hoping that there are
appropriately knowledgeable people here who will be able to help!
I am working on a Linux driver for an I2C RTC device and need to add the
correct definitions into the device tree for the SAMA5D31 to be passed to
the kernel at boot time. I have added:
i2c0: i2c@f0014000 {
status = okay;
rv8523c3@68 {
compatible = mc,rv8523c3;
reg = 0x68;
};
};
This sets up enough to allow the basic clock functions within the RTC to
work correctly and the hwclock command within Busybox to work correctly. I
need to add in the definitions for a GPIO (PE31) to be used as the alarm
interrupt pin and can't get my head around the definitions needed within the
device tree. I have tried adding the following
interrupt-parent = pioE;
interrupts = 31;
When the RTC driver is loaded by Linux the client-irq variable in the probe
function doesn't contain a value 0 and so doesn't setup an interrupt.
Any ideas on the correct definitions needed?
Thanks (and apologies for the noise),
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH V3 2/3] usb: eth: add ASIX AX88179 DRIVER
Hello Rene, Subject: [U-Boot] [PATCH V3 2/3] usb: eth: add ASIX AX88179 DRIVER changes in v3: -added all compatible devices from linux driver -fixed issues from review changes in v2: -added usb_ether.h to change list -added 2nd patch to enable driver for arndale board Following the additional comments that came from Marek do you know when you will be submitted a v4 of this patch? Thanks for your effort on this. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] UBI issues on SAMA5D31 NOR flash
Hello Heiko, UBI error: vtbl_check: reserved_pebs 81, ubi-good_peb_count 80 UBI error: vtbl_check: too large reserved_pebs, good PEBs 80 Use of UBI is new to me so where are the PEBs configured? Good question ... looking into vtbl_check(), the reserved_pebs value is read from the record in the volume table: reserved_pebs = be32_to_cpu(vtbl[i].reserved_pebs); @reserved_pebs: how many physical eraseblocks are reserved for this volume I have changed the size of the partition as defined in U-Boot and also reduced the maximum image size when creating the UBI image and have found a combination that moves me on to the next error: U-Boot ubi part rootfs UBI: attaching mtd2 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size:130944 bytes UBI: smallest flash I/O unit:1 UBI: VID header offset: 64 (aligned 64) UBI: data offset:128 - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! - Warning: 1 protected sectors will not be erased! UBI error: ubi_io_write: error -5 while writing 64 bytes to PEB 0:0, written 0 bytes UBI error: erase_worker: failed to erase PEB 0, error -5 UBI error: erase_worker: bad physical eraseblock 0 detected UBI warning: ubi_ro_mode: switch to read-only mode UBI error: do_work: work failed with error code -5 UBI error: autoresize: cannot auto-resize volume 0 UBI error: ubi_init: cannot attach mtd2 UBI error: ubi_init: UBI error: cannot initialize UBI, error -30 UBI init error 30 Hopefully this may be the last hurdle to overcome but somehow I think maybe not! Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] UBI issues on SAMA5D31 NOR flash
Hello Heiko, What says flinfo ? It seems you have protected sectors on your nor flash ... you must unprotect them before using it ... flinfo says that all sectors are read only as the flash device supports block locking and powers up with all sectors in their locked state. The board configuration file includes CONFIG_SYS_FLASH_PROTECTION in order to allow the protect off command to work prior to manual updates of the flash content. Cheer up! I'll try! :-) Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] UBI issues on SAMA5D31 NOR flash
Hello Heiko, What says flinfo ? It seems you have protected sectors on your nor flash ... you must unprotect them before using it ... flinfo says that all sectors are read only as the flash device supports block locking and powers up with all sectors in their locked state. The board configuration file includes CONFIG_SYS_FLASH_PROTECTION in order to allow the protect off command to work prior to manual updates of the flash content. Running protect off on the UBI area before ubi part rootfs makes the command work without any issues. Now just have to figure out why the Linux kernel isn't detecting the partition and mounting it... Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] UBI issues on SAMA5D31 NOR flash
Hello Heiko, Using the patches from Bo Shen to support the NOR flash on the Atmel which patches? I can't find the references in Patchman but they were sent to the mailing list on 18th July 2014 in a series called ARM: atmel: sama5d3xek: enable NOR flash support. The patches basically just add the board features to enable the IO pins for the NOR flash and to map it into the memory map at 0x1000. U-Boot ubi part rootfs UBI: attaching mtd2 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size:130944 bytes UBI: smallest flash I/O unit:1 UBI: VID header offset: 64 (aligned 64) UBI: data offset:128 UBI error: vtbl_check: volume table check failed: record 0, error 9 seems ubi does not find the volume table ... could you activate ubi error messages ubi_err() ? Adding: #define DEBUG #define CONFIG_MTD_UBI_DEBUG #define CONFIG_MTD_UBI_DEBUG_MSG #define CONFIG_UBIFS_FS_DEBUG Gives the following output: U-Boot ubi part rootfs ---mtdparts_init--- last_ids : nor0=physmap-flash.0 env_ids : nor0=physmap-flash.0 last_parts: mtdparts=physmap-flash.0:128k(bootstrap)ro,768k(u-boot)ro,128k(fdt),4m(kerne l),10m(rootfs) env_parts : mtdparts=physmap-flash.0:128k(bootstrap)ro,768k(u-boot)ro,128k(fdt),4m(kerne l),10m(rootfs) last_partition : nor0,0 env_partition : nor0,0 --- find_dev_and_part --- id = rootfs --- find_dev_and_part --- id = rootfs Creating 1 MTD partitions on nor0: 0x0050-0x00f0 : mtd=4 UBI: attaching mtd2 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size:130944 bytes UBI: smallest flash I/O unit:1 UBI: VID header offset: 64 (aligned 64) UBI: data offset:128 UBI error: vtbl_check: volume table check failed: record 0, error 9 UBI error: ubi_init: cannot attach mtd2 UBI error: ubi_init: UBI error: cannot initialize UBI, error -22 UBI init error 22 Command failed, result=22 Did the ubi partition work under linux? Did you tried current ML U-Boot (there MTD/UBI and UBIFS is synced with linux 3.15) ... I haven't booted to Linux yet. If I try to boot with the kernel that is in the NOR flash then I get the following output from the console messages: 0.nor_flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x89 Chip ID 0x00899a Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method Using auto-unlock on power-up/resume cfi_cmdset_0001: Erase suspend on write enabled UBI error: ubi_init: UBI error: cannot initialize UBI, error -19 Is there something that I need to do in order to tell U-Boot and the kernel that the base address of the NOR flash device is 0x1000 rather than 0x0? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] UBI issues on SAMA5D31 NOR flash
Hello Heiko, Hmm.. I thought to see something like this: too large reserved_pebs %d, good PEBs %d I am not familiar with this HW ... I think, you have to debug into it Changing the dbg_err() to ubi_err() and also adding a bit more output then I get: UBI error: vtbl_check: reserved_pebs 81, ubi-good_peb_count 80 UBI error: vtbl_check: too large reserved_pebs, good PEBs 80 Use of UBI is new to me so where are the PEBs configured? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] UBI issues on SAMA5D31 NOR flash
Hello, Using the patches from Bo Shen to support the NOR flash on the Atmel SAMA5D31EK hardware platform I am trying to get a UBI root file system within the NOR flash, at offset 0x1000 in the memory map, to work but get errors from the ubi part command using U-Boot 2014.04: U-Boot mtdparts device nor0 physmap-flash.0, # parts = 5 #: namesizeoffset mask_flags 0: bootstrap 0x0002 0x 1 1: u-boot 0x000c 0x0002 1 2: fdt 0x0002 0x000e 0 3: kernel 0x0040 0x0010 0 4: rootfs 0x00a0 0x0050 0 active partition: nor0,0 - (bootstrap) 0x0002 @ 0x defaults: mtdids : nor0=physmap-flash.0 mtdparts: mtdparts=physmap-flash.0:128k(bootstrap)ro,768k(u-boot)ro,128k(fdt),4m(kerne l),10m(rootfs) U-Boot ubi part rootfs UBI: attaching mtd2 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size:130944 bytes UBI: smallest flash I/O unit:1 UBI: VID header offset: 64 (aligned 64) UBI: data offset:128 UBI error: vtbl_check: volume table check failed: record 0, error 9 UBI error: ubi_init: cannot attach mtd2 UBI error: ubi_init: UBI error: cannot initialize UBI, error -22 UBI init error 22 The UBI settings are: (2048) Image Size (130944) Logical Erase Block Size (1) Minimum I/O Size [ ] mkfs.ubifs Space Fixup ()mkfs.ubifs Options *** UBI Image Properties *** [*] Create UBI Volume (10MiB) Root File System Volume Size (128 KiB) Physical Erase Block Size (1) Sub-page Size () ubinize Configuration File () ubinize Options Any ideas as to what I have missed? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Spansion SPI flash read timeout with AM335x
Hello,
I am doing some work with the TI AM3358 Starter Kit and a Spansion S25FL164K
SPI NOR flash.
Trying both U-Boot 2013.10, which ships with the TI kit, and 2014.04 I have
made the changes to board configuration file to enable SPI0 and disable I2C1
in the board pin mux, have included Spansion flash support and have added
the following entry into the Spansion devices listed in sf_params.c
{S25FL164K, 0x014017, 0x0140, 4 * 1024, 2048, RD_FULL,
SECT_4K},
Using the am335x_evm_spiboot configuration I have MLO and u-boot.img files
which I can program to the SPI flash successfully and also boot the board
from. I have a problem with read timeouts in the omap3_spi_read() function
in drivers/spi/omap3_spi.c trying to read the Linux kernel.
Having run some more tests (results below) it appears that with an sf read
command requesting more than about 0x16E000 bytes will fail. On occasion,
typically the first failed attempt, the status returns 0x0002 rather
than 0x0007.
U-Boot# sf read ${loadaddr} 0xE 0x10
SF: 1048576 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x14
SF: 1310720 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x15
SF: 1376256 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x16
SF: 1441792 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x17
omap3_spi_read SPI RXS timed out, status=0x0007
SF: 1507328 bytes @ 0xe Read: ERROR
U-Boot# sf read ${loadaddr} 0xE 0x168000
SF: 1474560 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x16C000
SF: 1490944 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x16E000
SF: 1499136 bytes @ 0xe Read: OK
U-Boot# sf read ${loadaddr} 0xE 0x16F000
omap3_spi_read SPI RXS timed out, status=0x0007
SF: 1503232 bytes @ 0xe Read: ERROR
Can anyone give me some guidance on how to resolve this?
Thanks,
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MMC interfaces on AM335x
Hello, I am working on a port of U-Boot to a custom hardware platform based on the TI AM3354. According to the schematics from the hardware design company, the AM3354 has a 4bit MMC interface (MMC0) which has been connected to a uSD card connector. There is a second interface (8bit) connected to GPMC signals which is connected to a Micron eMMC device labelled as MMC1. U-Boot and the Linux kernel will be stored in a separate SPI flash device and the eMMC card will hold the root file system and the uSD card for removable storage. Am I correct in thinking that if U-Boot boots with no uSD card installed the eMMC device will be accessed as device 0 e.g. U-Boot fatload mmc 0 ... but if it boots with a uSD card fitted then the eMMC device will be device 1, e.g. U-Boot fatload mmc 1 ... Is there any way to force U-Boot always to map the eMMC device as device 0? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Falcon boot mode
Hello, Does Falcon boot mode only support raw NAND devices as described in the README.falcon file will it also work with SPI NOR devices and eMMC NAND, SDC card as well? Thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] SPL and an LCD splash screen on AM335x
Hello! We are currently working on the specification for a project using the TI AM335x where the overall system boot time has to be reduced as far as possible. In order to achieve that I am proposing that we implement a board specific spl_start_uboot() function which under normal circumstances U-Boot SPL will load the Linux kernel directly. One of the other requirements is to display a splash screen logo on the LCD as early in the boot process as possible. Is it possible to get U-Boot SPL to do that or will we always have to boot through U-Boot or see if we can get the Linux kernel to do it as early as possible? Thoughts and ideas welcome. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 2/2] ARM: atmel: sama5d3xek: enable NOR flash support
Hi Bo, -/* No NOR flash */ +/* NOR flash */ +#define CONFIG_CMD_FLASH + +#ifdef CONFIG_CMD_FLASH +#define CONFIG_SYS_FLASH_CFI +#define CONFIG_FLASH_CFI_DRIVER +#define CONFIG_SYS_FLASH_BASE0x1000 +#define CONFIG_SYS_MAX_FLASH_SECT0x2 +#define CONFIG_SYS_MAX_FLASH_BANKS 1 +#else #define CONFIG_SYS_NO_FLASH +#endif The NOR flash device on the SAMA5D3x CPU modules supports hardware sector protection and according to the flash datasheet: All blocks power-up in a locked state to protect array data from being altered during power transitions. In order to make your patch set work: #define CONFIG_SYS_FLASH_PROTECTION needs adding into the include/configs/sama5d3xek.h file. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 2/2] ARM: atmel: sama5d3xek: enable NOR flash support
Hi Bo, +#ifdef CONFIG_CMD_FLASH +#define CONFIG_SYS_FLASH_CFI +#define CONFIG_FLASH_CFI_DRIVER +#define CONFIG_SYS_FLASH_BASE 0x1000 +#define CONFIG_SYS_MAX_FLASH_SECT 0x2 Is this the correct value for CONFIG_SYS_MAX_FLASH_SECT? Shouldn't it be 127 (if we ignore the top boot block) or 131 if they are included? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Atmel SAMA5D31 NOR boot - sanity check required
Hi Bo, I think you should check more detail in section 12 Standard Boot Strategies. It needs more things to do. I will give a picture in following answer. snip As the code execute on NOR flash, so, the SPL configure the CPU clock will cause SMC access abortion. So, a brief guide as following: The datasheet says the user software in external memory should: a) Enable the 32768 Hz oscillator if best accuracy is needed. b) Reprogram the SMC setup, cycle, hold, mode timing registers for EBI CS0, to adapt them to the new clock. c) Program the PMC (Main Oscillator Enable or Bypass mode). d) Program and start the PLL. e) Switch the system clock to the new value. So my current thinking is that: - I am not so worried about (a), as I don't think accuracy is essential at this point in time. - (b) needs to be taken care of in the steps that you outline below. - (c) ??? - The function at91_pmc_init() in board\atmel\sama5d3xek\sama5d3xek.c takes care of items (d) and (e) It has been a while since I have done this much low level code so I may be a little rusty :-) 1. Write a ram function, which do as the datasheet says. 2. Add copy function (copy the ram function into sram) at the begin of the SPL code. 3. After the step 1, finished to execute, then, you can jump back to NOR to execute. I'm not sure I follow how to do this. Are there any similar implementations elsewhere in U-Boot that I could use as a reference. I should say that ARM assembler isn't my strongest skill as most of my previous experience has been gained with x86 and MIPS. Thanks for all your help. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Atmel SAMA5D31 NOR boot - sanity check required
Hello! I am currently working on an implementation of NOR boot support for the Atmel SAMA5D31-EK reference platform as a precursor to a custom hardware platform. When tested and working I will push the support back to the community but what I have at the moment doesn't appear to do anything so I would appreciate a sanity check on the work done so far. For reference the documentation for the Atmel SoC says: If BMS signal is tied to 0, BMS_BIT is read at 1. The ROM code allows execution of the code contained in the memory connected to Chip Select 0 of the External Bus Interface (J828F128P33TF70A) and then goes on to detail the startup mode and changes that need to be made to the PLL and SMC. For simplicity sake, I have taken the standard SAMA5D31-EK configuration of SPL+U-Boot and have added NOR boot support to SPL based on one of the other boards. The board header file has the following configuration: #define CONFIG_SPL_NOR_SUPPORT #define CONFIG_SYS_FLASH_CFI1 #define CONFIG_FLASH_CFI_DRIVER 1 #define CONFIG_SYS_FLASH_BASE 0x #define CONFIG_SYS_MONITOR_BASE CONFIG_SYS_FLASH_BASE As per the standard SPL build for this hardware platform the CONFIG_SYS_INIT_SP_ADDR value is set to 0x31 but I haven't found a definitive statement that confirms that the internal SRAM is mapped to that location when in this boot mode. So my questions are... Is the SPL+U-Boot implementation the best way for NOR booting or should it all just be built as a single U-Boot image? Do the settings above look correct, particularly the value for the initial stack pointer? How best do I debug SPL to determine where it is getting lost in the weeds? Many thanks, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Micron PC28F00AP30 flash support
Hello Stefan, I am looking at porting U-Boot to a board that is being designed with a Micron PC28D00AP30 NOR flash device and can't work out whether this is something that is already supported by U-Boot or whether it is work that I will need to undertake. I have had a good grep through the code and can't find any specific references to the device but don't know the CFI code well enough to know whether it will just detect it and work. According to the Micron datasheet, the device itself is 1Gb in density and has symmetrical 64Kword erase blocks. Any guidance would be much appreciated. Thanks in advance, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] RFC - PatchTrack Specification (revised)
Wolfgang wrote... A revised version of the spec (sorry, I would have used reply-to but something went amiss with gmail and I've lost the original) http://www.denx.de/wiki/U-Boot/ToolsPatchTracking updated. I have been and had a look at the specification that you have posted and am happy to get my hands dirty helping with implement and test this. I know that a good proportion (possibly even all of it) could be implemented in Python but is there a preference or consensus on what would be the best language to do it in? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12
Marek wrote loads of stuff then wrote... But then, how shall we go about it? Any python gurus around? I wouldn't class myself as a guru as that should be a title that is bestowed on you by others but I know a fair amount of Python and might be able to have a go at implementing some of this stuff once we know exactly what we are after. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 0/5] Various x86 patches
Hi Graeme, Graeme Russ (5): x86: Fix compilation on 64-built built machines Shouldn't this be 64-bit build machines? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Missing ethernet
Gary wrote... I'm trying to update U-boot on my board from v2011.06 to v2011.12 It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking. So not a BeagleBoard then but something different. Is the board you are using one of the boards supported in the mainline U-Boot tree or is it an out-of-tree port? If it is in mainline then have you chosen the correct configuration to use? I've looked through the 'bootm' path and I can't see what might have changed that would cause such behaviour. As far as I can tell, everything else is working in Linux with the new U-Boot, just not the SMSC device. If you try to use TFTP in U-Boot does that work? If not then I would guess there is a configuration issue with the devices that you have enabled in U-Boot rather than it being an issue with the bootm command. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 0/9] Fix a few warnings that bug me
Hi Simon, snip arch/powerpc/cpu/mpc5xxx/usb_ohci.c | 79 -- arch/powerpc/cpu/ppc4xx/usb_ohci.c | 81 -- arch/powerpc/lib/board.c snip The two PowerPC ones apparently only happen with the 4.4 toolchain, so I think we are going to drop those and I am going to upgrade my toolchain instead :-) This has just grabbed my attention with the comment regarding the 4.4 toolchain as I know that MontaVista ship a version of the 4.4.0 toolchain for PowerPC with one of their embedded Linux products. Is there a generic issue with 4.4.x versions or just a rogue board or two? Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Problems with all boot-possibilties
David wrote... I have a Freescale MPC8313E and want to boot with u.-boot 1.3.0 (there is no newer version avaiable, see also other thread). Version 1.3.0 is only a month away from celebrating its 4th birthday and it is highly unlikely that anyone here has the inclination to support it. Having had a look in the boards.cfg file in the current git repository there are several MPC8313ERDB based configurations and I have a much later version of u-boot on my MPC8313ERDB board and when I have some time free I will upgrade to the 2011.09 version when it is released. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] coldfire, bad program counter on rte
Hello Angelo, U-Boot 1.1.6 (May 27 2011 - 00:09:24) I suggest that you have two options: 1. Create a time machine and set it for November 2006 when 1.1.6 was current. 2. Try the latest code base for U-Boot. :-) Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] coldfire, bad program counter on rte
Angelo wrote... U-Boot 1.1.6 (May 27 2011 - 00:09:24) I suggest that you have two options: 1. Create a time machine and set it for November 2006 when 1.1.6 was current. 2. Try the latest code base for U-Boot. :-) the current sourceforge link of u-boot offer this package, so i considered as almost stable. http://sourceforge.net/projects/u-boot/ I think it is a long time since the sourceforge.net page was current. The home for the project is at http://www.denx.de/wiki/U-Boot. If you think there could be some issue related to this, i certainly update to last source. If nothing else, you might want the last four years worth of feature enhancements, bug fixes, etc. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [STATUS] WARNING: huge ARM board removal pending
Hi Wolfgang, this is a * W A R N I N G * message to maintainers / users / owners of ARM boards. If your board fails to build in the current release, it will be subject to a big cleanup action which is going to remove all old, unmaintained and broken boards in the next merge window. According to our current schedule, this is in 10 days from now. Although I'm not the board maintainer I do have an omap5912osk board sat on the shelf and am happy to do the necessary work to get the current code release to work but it would have to wait until some current project work is completed which may take the rest of June. Is that OK? Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [STATUS] U-Boot v2011.03 released - Merge Window OPEN
Wolfgang wrote... - The cleanup after the reorganization of the ARM code has not been completed yet. At the moment, some 100+ RM boards are *broken* and *do not compile*. Do you have an easily accessible list of these boards that are currently still broken? If there is anything in the list for hardware that I have lying around I may have a little time to take a look. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot for x86 Core2Duo target
Zvi wrote... On my next project, the target is Core2Duo (AMPRO's COM840). Is it a wise decision to use u-boot on this target ? Probably not! Ampro will already have invested a lot of time and effort in porting the BIOS to that board and are giving you a device that works out of the box. If there is a specific issue that you have with their board then talk to Ampro and they may look into it for you. Is it a huge project to port it to another x86 target that has a different ethernet controller ? In the first instance it will rely on you being able to get all of the information that you need in order to initialise all of the respective hardware and some of the x86 CPU and chipset vendors limit who they make it available to. There are other questions you will need to ask, for instance. Are you using the VGA display? If so, will your operating system device driver work without the video BIOS having done the initialisation or some of the other services provided by it? The u-boot image is loader by the BIOS from compact flash via SATA. As Graeme Russ said, U-Boot would replace the BIOS. I haven't looked at the board but I would assume the BIOS can be in-situ updated. In the first instance you could try the flash update utility that goes along with the BIOS to see if it will reprogram it with an arbitrary binary. It may not do as it may have a write protected boot block that you can't replace. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] WinCE image load/boot cmd support
Hello! Does anyone know what happened to the patches for loading and booting Windows CE image suggested here: http://lists.denx.de/pipermail/u-boot/2008-August/039202.html Did they get included and have subsequently been removed from U-Boot or did they never make it into the mainline code? Thanks and regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] WinCE image load/boot cmd support
Graeme wrote... Did they get included and have subsequently been removed from U-Boot or did they never make it into the mainline code? I doubt it. The fact that it used the GPL incompatible BSD license (the one with 'obnoxious advertising' clause) probably didn't help ;) If they were rewritten to fit in with the ethos and licensing of U-Boot is it something that would be a worthwhile addition? Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] WinCE image load/boot cmd support
Michael wrote... If they were rewritten to fit in with the ethos and licensing of U- Boot is it something that would be a worthwhile addition? I have rewritten them, but they are lack of same part. Physical, Virtual mapping and parameter passing Are you prepared to share them and I will see if I can figure out how to add the support that is missing. Thanks and regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH V2] Fix misc spelling errors found by lintian
Loic wrote...
snip
diff --git a/common/cmd_usb.c b/common/cmd_usb.c
index b04a8df..7fcc61a 100644
--- a/common/cmd_usb.c
+++ b/common/cmd_usb.c
@@ -580,7 +580,7 @@ int do_usb(cmd_tbl_t *cmdtp, int flag, int argc,
char * const argv[])
break;
}
if (dev == NULL) {
- printf(*** NO Device avaiable ***\n);
+ printf(*** NO Device available ***\n);
Should this be further amended to be all upper case or all words starting with
an upper case character rather than the current random looking collection?
snip
Andy.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] powerpc: do not fixup NULL ptrs
Joakim wrote... Sure, but until freescale or someone else with eq. and motivation researches it, we are stuck. I am not sure anyone else has tried 83xx based boards yet. If someone has please report. Also include weather booted from NAND or NOR, CPU type(e300cX) and what reset vector is used. I have a couple of Freescale reference boards here (8313ERDB and 8349-MITX-GP). I'm not a powerpc expert by any means but if there are some (simple) tests you would like me to run on them then I will see if I can find some time. Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] x86 Custodianship
Hi Graeme, One quick question - Since I am currently the only x86 developer, how do you want to handle the SOB + Ack'd for x86 patches? I feel that to date be applying my patches you have implied your own Ack'd By. Should I wait for you (or somebody else) to Ack them before I apply them to the x86 repo? I have been doing x86 firmware development for more years than I am prepared to admit to! As and when time allows then I am happy to muck in with the x86 development anywhere that I can. Regards, Andy. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] HOSTCC version
Hello, What version of host gcc is needed for building the tools such as mkimage.exe? My embedded Linux development environment is Cygwin (1.3.22) based and includes gcc 3.4.4 which gives compiler errors for versions of U-Boot 1.3.3 and later. make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-2008.10/tools' gcc -g -Wall -idirafter /home/andy/bootloaders/uboot/u-boot-2008.10/include -idi rafter /home/andy/bootloaders/uboot/u-boot-2008.10/include2 -idirafter /home/and y/bootloaders/uboot/u-boot-2008.10/include -DTEXT_BASE=0xFE00 -DUSE_HOSTCC - O -c -o mkimage.o mkimage.c In file included from ../include/libfdt.h:54, from fdt_host.h:25, from mkimage.h:36, from mkimage.c:25: /home/andy/bootloaders/uboot/u-boot-2008.10/include/libfdt_env.h:50: error: conf licting types for 'uintptr_t' /usr/include/cygwin/types.h:167: error: previous declaration of 'uintptr_t' was here In file included from fdt_host.h:25, from mkimage.h:36, from mkimage.c:25: ../include/libfdt.h: In function `fdt_set_magic': ../include/libfdt.h:162: warning: implicit declaration of function `__cpu_to_be3 2' In file included from mkimage.c:26: /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h: At top level: /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:193: error: parse error before ulong /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:195: error: parse error before load /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:197: error: parse error before '}' token /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:211: error: parse error before ulong /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:231: error: parse error before os /home/andy/bootloaders/uboot/u-boot-2008.10/include/image.h:231: error: conflicting types for 'os' And so it goes on! If I remove mkimage from the BIN_FILES line of tools/Makefile then the rest builds OK. Thanks in advance, A. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] HOSTCC version
Dear Wolfgang, What version of host gcc is needed for building the tools such as mkimage.exe? My embedded Linux development environment is Cygwin (1.3.22) based and includes gcc 3.4.4 which gives compiler errors for versions of U-Boot 1.3.3 and later. Do you also get these errors for the current code, i. e. top of tree from git repository? I have downloaded the code from the git using the command: git clone git://git.denx.de/u-boot.git The errors that I see are now slightly different. It is complaining that endian.h and byteswap.h don't exist - and that appears to be correct for the system that I have. The error regarding 'uintptr_t' has been fixed based on the patch from Jerry Van Baren but I still get an number of parse errors regarding image.h. Your thoughts and comments would be much appreciated. Compiler output is shown below. Thanks and regards, Andy. In file included from ../include/libfdt.h:54, from fdt_host.h:25, from mkimage.h:36, from image.c:71: /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:27:20: endian.h: No such file or directory /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:28:22: byteswap.h: No such file or directory In file included from ../include/libfdt.h:54, from fdt_host.h:25, from mkimage.h:36, from mkimage.c:25: /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:27:20: endian.h: No such file or directory /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:28:22: byteswap.h: No such file or directory make[1]: Leaving directory `/home/andy/bootloaders/uboot/u-boot-git/tools' make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-git/tools' make[1]: Nothing to be done for `_depend'. make[1]: Leaving directory `/home/andy/bootloaders/uboot/u-boot-git/tools' make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-git/examples' make[1]: Leaving directory `/home/andy/bootloaders/uboot/u-boot-git/examples' make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-git/examples' make[1]: Nothing to be done for `_depend'. make[1]: Leaving directory `/home/andy/bootloaders/uboot/u-boot-git/examples' make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-git/api_example s' make[1]: Nothing to be done for `_depend'. make[1]: Leaving directory `/home/andy/bootloaders/uboot/u-boot-git/api_examples ' Generating include/autoconf.mk make -C tools all make[1]: Entering directory `/home/andy/bootloaders/uboot/u-boot-git/tools' gcc -Wall -pedantic -ansi -idirafter /home/andy/bootloaders/uboot/u-boot-git/inc lude -idirafter /home/andy/bootloaders/uboot/u-boot-git/include2 -idirafter /hom e/andy/bootloaders/uboot/u-boot-git/include -DTEXT_BASE=0xFE00 -DUSE_HOSTCC -O -c -o img2srec.o img2srec.c gcc -Wall -pedantic -ansi -idirafter /home/andy/bootloaders/uboot/u-boot-git/inc lude -idirafter /home/andy/bootloaders/uboot/u-boot-git/include2 -idirafter /hom e/andy/bootloaders/uboot/u-boot-git/include -DTEXT_BASE=0xFE00 -DUSE_HOSTCC -O -o img2srec.exe img2srec.o strip img2srec.exe gcc -g -Wall -idirafter /home/andy/bootloaders/uboot/u-boot-git/include -idiraft er /home/andy/bootloaders/uboot/u-boot-git/include2 -idirafter /home/andy/bootlo aders/uboot/u-boot-git/include -DTEXT_BASE=0xFE00 -DUSE_HOSTCC -O -c -o mkim age.o mkimage.c In file included from ../include/libfdt.h:54, from fdt_host.h:25, from mkimage.h:36, from mkimage.c:25: /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:27:20: endian.h: No such file or directory /home/andy/bootloaders/uboot/u-boot-git/include/libfdt_env.h:28:22: byteswap.h: No such file or directory In file included from mkimage.c:26: /home/andy/bootloaders/uboot/u-boot-git/include/image.h:195: error: parse error before ulong /home/andy/bootloaders/uboot/u-boot-git/include/image.h:197: error: parse error before load /home/andy/bootloaders/uboot/u-boot-git/include/image.h:199: error: parse error before '}' token /home/andy/bootloaders/uboot/u-boot-git/include/image.h:213: error: parse error before ulong /home/andy/bootloaders/uboot/u-boot-git/include/image.h:266: error: parse error before '}' token /home/andy/bootloaders/uboot/u-boot-git/include/image.h:384: error: parse error before image_get_data /home/andy/bootloaders/uboot/u-boot-git/include/image.h: In function `image_get_ data': /home/andy/bootloaders/uboot/u-boot-git/include/image.h:386: error: `ulong' unde clared (first use in this function) /home/andy/bootloaders/uboot/u-boot-git/include/image.h:386: error: (Each undecl ared identifier is reported only once /home/andy/bootloaders/uboot/u-boot-git/include/image.h:386: error: for each fun ction it appears in.) /home/andy/bootloaders/uboot/u-boot-git/include/image.h:386: error: parse error before hdr /home/andy/bootloaders/uboot/u-boot-git/include/image.h: At top level:
