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] Quark compile errors
Hi Andy, On Wed, May 20, 2015 at 6:00 PM, Andy Pont andy.p...@sdcsystems.com wrote: 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: Can you post your full configuration here? 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! I am using xterm, not sure if this helps. $ echo $TERM xterm Regards, Bin ___ 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 Andy, On Wed, May 20, 2015 at 10:58 PM, Andy Pont andy.p...@sdcsystems.com wrote: 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! Good to know. 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? Regards, Bin ___ 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 Andy, On 20 May 2015 at 04:20, Andy Pont andy.p...@sdcsystems.com wrote: 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. You might be able to set that terminal program to support 'xterm' emulation, or perhaps change TERM to whatever it does support. Regards, Simon ___ 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 Andy, On Wed, May 20, 2015 at 6:20 PM, Andy Pont andy.p...@sdcsystems.com wrote: 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 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, Bin ___ 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 Andy, On Wed, May 20, 2015 at 10:50 PM, Andy Pont andy.p...@sdcsystems.com wrote: 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. I have been using 4.6.1 and 4.7.2, and both work. Can you please try some newer gcc? Regards, Bin ___ 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
