November 2009 - U-Boot

[U-Boot] Breakage on arm/next
by Tom 28 Nov '09

28 Nov '09

In rebasing arm/next against u-boot/next. There is a general error with targets that use onenand. This includes the targets nk8815_onenand omap3_evm smdkc100 The error message is env_onenand.c: In function 'env_relocate_spec': env_onenand.c:70: error: 'CONFIG_ENV_ADDR_FLEX' undeclared (first use in this function) env_onenand.c:70: error: (Each undeclared identifier is reported only once env_onenand.c:70: error: for each function it appears in.) env_onenand.c: In function 'saveenv': env_onenand.c:106: error: 'CONFIG_ENV_ADDR_FLEX' undeclared (first use in this function) env_onenand.c:107: error: 'CONFIG_ENV_SIZE_FLEX' undeclared (first use in this function) I believe the error is from commit c758e947aa7d39a2be607ecdedd818ad300807b2 Author: Amul Kumar Saha <amul.saha(a)samsung.com> Date: Wed Nov 4 10:38:46 2009 +0530 ENV Variable support for Flex-OneNAND Define and use CONFIG_ENV_ADDR_FLEX and CONFIG_ENV_SIZE_FLEX for storing environment variables. Signed-off-by: Rohit Hagargundgi <h.rohit(a)samsung.com> Signed-off-by: Amul Kumar Saha <amul.saha(a)samsung.com> In general MAKEALL should be used to regression test your changes. Please send a patch for this problem as soon as possible. Tom

1 0

[U-Boot] U-Boot hangs when board is attached to BDI2000
by Dunda, Matthias 27 Nov '09

27 Nov '09

Hi all, I am trying to debug u-boot following the instructions in DULG 10.1. As mentioned in 10.1.1. before relocation I connect to the target an get desired first output: Remote debugging using jtag:3333 0xfffffffc in ?? () Even without setting a breakpoint then, I just say gdb to continue: (gdb) c Continuing. The output in the console then is: U-Boot 2009.08 (Nov 25 2009 - 09:18:37) CPU: 8568E, Version: 1.1, (0x807d0011) Core: E500, Version: 2.2, (0x80210022) Clock Configuration: CPU0:1320 MHz, CCB:528 MHz, DDR:264 MHz (528 MT/s data rate), LBC:66 MHz QE:528 MHz L1: D-cache 32 kB enabled I-cache 32 kB enabled Board: 8568 MDS I2C: ready DRAM: Initializing SDRAM: 64 MB DDR: 512 MB (DDR2, 64-bit, CL=4, ECC off) ...and nothing further happens. After 30 secs or so, I simply hit Ctrl-C and get: ^C Program received signal SIGSTOP, Stopped (signal). 0x1ff70700 in ?? () (gdb) bt #0 0x1ff70700 in ?? () #1 0x1ff71574 in ?? () Cannot access memory at address 0xdeadbef3 (gdb) When I issue a "reset run" within the BDI shell, the target boots as expected, but when I start the target with "reset halt" to debug it from the first instruction it behaves at described above. I am using a BDI2000 on a Freescale MPC8568E-MDS board. U-boot 2009.08 is compiled with make CROSS_COMPILE=ppc_85xx- MPC8568MDS_config make CROSS_COMPILE=ppc_85xx- all Any ideas? Is there some watchdog issue to cope with, maybe? Cheers Matthias

2 1

Re: [U-Boot] [PATCH] ppc: transform init_sequence into a function.
by Alessandro Rubini 27 Nov '09

27 Nov '09

> I think most of the ugliness comes from the #ifdef hell in this list. > replacing the #ifdefs is another matter so looking behind > the #ifdef mess, I don't think it looks too bad. I think the approach I took with lib_arm/board.c may apply as well. A simple weak init_nop(), no change at all in board code and no more "CONFIG_BOARD_EARLY_INIT_F" kind of stuff. >> This is much more ugly, and I cannot see why it would be easier to >> debug. > > You can set breakpoints anywhere you like. When it crashes in here > somewhere, it isn't easy to tell where it did so. I agree it is uglier (and I've discussed with Joakim offlist), this is a very strong point. I never had problems with the u-boot init function, I had serious issues with kernel initcalls. Whils debug_initcall is great and good in the kernel, we can't do with printf ini u-boot, not in the first steps, at least. So while I strongly prefer data structures to a burst of "if () goto error;", I think Joakim has a point here -- after I argued against it offlist. /alessandro

2 1

[U-Boot] Weird problem with kernel/initrd loading
by Ioannis Kyriakopoulos 27 Nov '09

27 Nov '09

Hi all, I have a query regarding the boot of an initrd with U-boot. ASAIK, ramdisk.gz should be converted to a type supported by U-boot with the use of mkimage tool (with a -T ramdisk switch). Also, the "bootm" command should be invoked by passing the address of uImage first and then the address of ramdisk.gz as it is mentioned here http://www.denx.de/wiki/DULG/UBootCmdGroupExec. However, in this case I get the following output and the kernel can't recognize/mount the ramdisk. OMAP3 beagleboard.org # setenv bootargs 'console=ttyS2,115200n8, root=/dev/ram0 rw initrd=0x81600000,8M, init=/linuxrc' OMAP3 beagleboard.org # mmcinit; fatload mmc 0 0x80002000 uImage; fatload mmc 0 0x81600000 ramdisk.gz; bootm 0x80002000 0x81600000 reading uImage 1950244 bytes read reading ramdisk.gz 2910640 bytes read ## Booting kernel from Legacy Image at 80002000 ... Image Name: Linux-2.6.32-rc7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1950180 Bytes = 1.9 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 81600000 ... Image Name: my_ramdisk Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2910576 Bytes = 2.8 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux....................................................................... .................................................. done, booting the kernel. [ 0.000000] Linux version 2.6.32-rc7 (limp@ubuntu) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #1 Thu Nov 26 12:32:47 GMT 2009 [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine: OMAP3 Beagle Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] OMAP3430 ES3.0 [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [ 0.000000] Kernel command line: console=ttyS2,115200n8, root=/dev/ram0 rw initrd=0x81600000,8M, init=/linuxrc [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Memory: 128MB 128MB = 256MB total [ 0.000000] Memory: 247552KB available (3332K code, 307K data, 120K init, 0K highmem) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:402 [ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz [ 0.000000] Reprogramming SDRC clock to 332000000 Hz [ 0.000000] GPMC revision 5.0 [ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts [ 0.000000] Total of 96 interrupts on 1 active controller [ 0.000000] OMAP34xx GPIO hardware version 2.5 [ 0.000000] OMAP clockevent source: GPTIMER1 at 13000000 Hz [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368) [ 0.000000] Mount-cache hash table entries: 512 [ 0.000000] CPU: Testing write buffer coherency: ok [ 0.000000] regulator: core version 0.5 [ 0.000000] NET: Registered protocol family 16 [ 0.000000] Found NAND on CS0 [ 0.000000] Registering NAND on CS0 [ 28.064483] OMAP DMA hardware revision 4.0 [ 28.080444] bio: create slab <bio-0> at 0 [ 28.083923] SCSI subsystem initialized [ 28.084747] usbcore: registered new interface driver usbfs [ 28.085235] usbcore: registered new interface driver hub [ 28.085540] usbcore: registered new device driver usb [ 28.086151] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz [ 28.089538] twl4030: PIH (irq 7) chaining IRQs 368..375 [ 28.089569] twl4030: power (irq 373) chaining IRQs 376..383 [ 28.090026] twl4030: gpio (irq 368) chaining IRQs 384..401 [ 28.091735] regulator: VUSB1V5: 1500 mV normal standby [ 28.092315] regulator: VUSB1V8: 1800 mV normal standby [ 28.092895] regulator: VUSB3V1: 3100 mV normal standby [ 28.094299] twl4030_usb twl4030_usb: Initialized TWL4030 USB module [ 28.095184] regulator: VMMC1: 1850 <--> 3150 mV normal standby [ 28.095794] regulator: VDAC: 1800 mV normal standby [ 28.096374] regulator: VPLL2: 1800 mV normal standby [ 28.096984] regulator: VSIM: 1800 <--> 3000 mV normal standby [ 28.097167] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz [ 28.099304] Switching to clocksource gp timer [ 28.102264] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 [ 28.104858] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92 [ 28.105468] NET: Registered protocol family 2 [ 28.105682] IP route cache hash table entries: 2048 (order: 1, 8192 bytes) [ 28.106262] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 28.106536] TCP bind hash table entries: 8192 (order: 3, 32768 bytes) [ 28.106719] TCP: Hash tables configured (established 8192 bind 8192) [ 28.106750] TCP reno registered [ 28.106964] NET: Registered protocol family 1 [ 28.107391] RPC: Registered udp transport module. [ 28.107391] RPC: Registered tcp transport module. [ 28.107421] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 28.107666] Trying to unpack rootfs image as initramfs... [ 28.107971] rootfs image is not initramfs (junk in compressed archive); looks like an initrd [ 28.154846] Freeing initrd memory: 8192K [ 28.155548] NetWinder Floating Point Emulator V0.97 (double precision) [ 28.157684] VFS: Disk quotas dquot_6.5.2 [ 28.157775] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 28.158996] NTFS driver 2.1.29 [Flags: R/O]. [ 28.159301] JFFS2 version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc. [ 28.160034] msgmni has been set to 499 [ 28.161315] alg: No test for stdrng (krng) [ 28.161407] io scheduler noop registered [ 28.161437] io scheduler anticipatory registered (default) [ 28.161437] io scheduler deadline registered [ 28.161621] io scheduler cfq registered [ 28.162353] omapfb: configured for panel omap3beagle [ 28.172393] omapfb: DISPC version 3.0 initialized [ 28.186523] Console: switching to colour frame buffer device 128x48 [ 28.199157] omapfb: Framebuffer initialized. Total vram 1572864 planes 1 [ 28.199188] omapfb: Pixclock 48000 kHz hfreq 44.7 kHz vfreq 57.7 Hz [ 28.218811] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 28.241882] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 [ 28.262725] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 [ 28.283538] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 [ 28.754913] console [ttyS2] enabled [ 28.759857] brd: module loaded [ 28.768463] loop: module loaded [ 28.772796] usbmon: debugfs is not available [ 28.777099] Initializing USB Mass Storage driver... [ 28.782531] usbcore: registered new interface driver usb-storage [ 28.788604] USB Mass Storage support registered. [ 28.793304] i2c /dev entries driver [ 28.910125] TCP cubic registered [ 28.913391] NET: Registered protocol family 17 [ 28.917907] NET: Registered protocol family 15 [ 28.922515] Power Management for TI OMAP3. [ 28.926818] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 [ 28.936676] regulator_init_complete: incomplete constraints, leaving VDVI on [ 28.943908] regulator_init_complete: incomplete constraints, leaving VDAC on [ 28.951171] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 28.957794] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 28.969543] List of all partitions: [ 28.973083] No filesystem could mount root, tried: ext3 ext2 vfat msdos ntfs [ 28.980346] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) The weird thing is that by using the very same uImage and ramdisk.gz but without using the mkimage tool to convert ramdisk.gz to a U-boot compatible type and without passing the ramdisk.gz memory address at "bootm" command, the filesystem gets mounted and the kernel boots successfully. Does anyone has any clue of what is getting wrong in the first case? Thanks in advance.

2 3

[U-Boot] [PATCH V2] arm/board.c: avoid ifdef using weak default functions
by Alessandro Rubini 27 Nov '09

27 Nov '09

From: Alessandro Rubini <rubini(a)unipv.it> While it's a matter of personal taste, I prefer to avoid ifdef when possible. For example, I don't like to add BOARD_LATE_INIT in the config file just to add a board_late_init() function. Also, I think the file is more readable without the ifdef stuff. This uses two trivial weak functions to provide defaults for all functions that were ifdeffed. This patch was initially rejected in favor of a initcall mechanism but that approach is not a work in progress any ore. --- One complaint I got about this is the runtime overhead. Actually, normal_nop is two instructions (plus the call to it) and void_nop is one instruction (plus the call), similar to the overhead in led management for platforms with no leds. lib_arm/board.c | 62 ++++++++++++++++++++++++++---------------------------- 1 files changed, 30 insertions(+), 32 deletions(-) diff --git a/lib_arm/board.c b/lib_arm/board.c index e148739..122e37a 100644 --- a/lib_arm/board.c +++ b/lib_arm/board.c @@ -65,10 +65,26 @@ DECLARE_GLOBAL_DATA_PTR; ulong monitor_flash_len; -#ifdef CONFIG_HAS_DATAFLASH -extern int AT91F_DataflashInit(void); -extern void dataflash_print_info(void); -#endif +/* Some functions may be there or not. Use a weak placeholder to avoid ifdef */ +int __normal_nop(void) { return 0; } +void __void_nop(void) {} + +/* parts of init_sequence that may not be present */ +int arch_cpu_init(void) __attribute__((weak, alias("__normal_nop"))); +int interrupt_init(void) __attribute__((weak, alias("__normal_nop"))); +int print_cpuinfo(void) __attribute__((weak, alias("__normal_nop"))); +int checkboard(void) __attribute__((weak, alias("__normal_nop"))); + +/* other functions that appear later and depend on config items */ +int AT91F_DataflashInit(void) __attribute__((weak, alias("__normal_nop"))); +void dataflash_print_info(void) __attribute__((weak, alias("__void_nop"))); +void serial_initialize(void) __attribute__((weak, alias("__void_nop"))); +void onenand_init(void) __attribute__((weak, alias("__void_nop"))); +int drv_vfd_init(void) __attribute__((weak, alias("__normal_nop"))); +void api_init(void) __attribute__((weak, alias("__void_nop"))); +int arch_misc_init(void) __attribute__((weak, alias("__normal_nop"))); +int misc_init_r(void) __attribute__((weak, alias("__normal_nop"))); +int board_late_init(void) __attribute__((weak, alias("__normal_nop"))); #ifndef CONFIG_IDENT_STRING #define CONFIG_IDENT_STRING "" @@ -196,6 +212,11 @@ static int init_func_i2c (void) puts ("ready\n"); return (0); } +#else +static int init_func_i2c (void) +{ + return 0; +} #endif #if defined(CONFIG_CMD_PCI) || defined (CONFIG_PCI) @@ -205,6 +226,11 @@ static int arm_pci_init(void) pci_init(); return 0; } +#else +static int arm_pci_init(void) +{ + return 0; +} #endif /* CONFIG_CMD_PCI || CONFIG_PCI */ /* @@ -235,32 +261,20 @@ typedef int (init_fnc_t) (void); int print_cpuinfo (void); init_fnc_t *init_sequence[] = { -#if defined(CONFIG_ARCH_CPU_INIT) arch_cpu_init, /* basic arch cpu dependent setup */ -#endif board_init, /* basic board dependent setup */ -#if defined(CONFIG_USE_IRQ) interrupt_init, /* set up exceptions */ -#endif timer_init, /* initialize timer */ env_init, /* initialize environment */ init_baudrate, /* initialze baudrate settings */ serial_init, /* serial communications setup */ console_init_f, /* stage 1 init of console */ display_banner, /* say that we are here */ -#if defined(CONFIG_DISPLAY_CPUINFO) print_cpuinfo, /* display cpu info (and speed) */ -#endif -#if defined(CONFIG_DISPLAY_BOARDINFO) checkboard, /* display board info */ -#endif -#if defined(CONFIG_HARD_I2C) || defined(CONFIG_SOFT_I2C) init_func_i2c, -#endif dram_init, /* configure available RAM banks */ -#if defined(CONFIG_CMD_PCI) || defined (CONFIG_PCI) arm_pci_init, -#endif display_dram_config, NULL, }; @@ -335,26 +349,18 @@ void start_armboot (void) nand_init(); /* go init the NAND */ #endif -#if defined(CONFIG_CMD_ONENAND) onenand_init(); -#endif -#ifdef CONFIG_HAS_DATAFLASH AT91F_DataflashInit(); dataflash_print_info(); -#endif /* initialize environment */ env_relocate (); -#ifdef CONFIG_VFD /* must do this after the framebuffer is allocated */ drv_vfd_init(); -#endif /* CONFIG_VFD */ -#ifdef CONFIG_SERIAL_MULTI serial_initialize(); -#endif /* IP Address */ gd->bd->bi_ip_addr = getenv_IPaddr ("ipaddr"); @@ -363,21 +369,15 @@ void start_armboot (void) jumptable_init (); -#if defined(CONFIG_API) /* Initialize API */ api_init (); -#endif console_init_r (); /* fully init console as a device */ -#if defined(CONFIG_ARCH_MISC_INIT) /* miscellaneous arch dependent initialisations */ arch_misc_init (); -#endif -#if defined(CONFIG_MISC_INIT_R) /* miscellaneous platform dependent initialisations */ misc_init_r (); -#endif /* enable exceptions */ enable_interrupts (); @@ -412,9 +412,7 @@ extern void davinci_eth_set_mac_addr (const u_int8_t *addr); } #endif -#ifdef BOARD_LATE_INIT board_late_init (); -#endif #ifdef CONFIG_GENERIC_MMC puts ("MMC: "); -- 1.6.0.2

3 4

[U-Boot] [PATCH] TI DaVinci: Adding a README for the DaVinci series of SOC's
by s-paulraj＠ti.com 27 Nov '09

27 Nov '09

From: Sandeep Paulraj <s-paulraj(a)ti.com> Adding an initial README for the DaVinci series of SOC's Signed-off-by: Sandeep Paulraj <s-paulraj(a)ti.com> --- doc/README.davinci | 116 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 116 insertions(+), 0 deletions(-) create mode 100644 doc/README.davinci diff --git a/doc/README.davinci b/doc/README.davinci new file mode 100644 index 0000000..506f0d4 --- /dev/null +++ b/doc/README.davinci @@ -0,0 +1,116 @@ +Summary +======= + +This README is about U-Boot support for TI's ARM 926EJS based family of SoCs. +These SOCs are used for cameras, video security and surveillance, DVR's, etc. +DaVinci SOC's comprise of DM644x, DM646x, DM35x and DM36x series of SOC's +Additionally there are some SOCs meant for the audio market which though have +an OMAP part number are very similar to the DaVinci series of SOC's +Additionally, some family members contain a TI DSP and/or graphics +co processors along with a host of other peripherals. + +Currently the following boards are supported: + +* TI DaVinci DM644x EVM + +* TI DaVinci DM646x EVM + +* TI DaVinci DM355 EVM + +* TI DaVinci DM365 EVM + +* TI DA830 EVM + +* DM355 based Leopard board + +* DM644x based schmoogie board + +* DM644x based sffsdr board + +* DM644x based sonata board + +Build +===== + +* TI DaVinci DM644x EVM: + +make davinci_dvevm_config +make + +* TI DaVinci DM646x EVM: + +make davinci_dm6467evm_config +make + +* TI DaVinci DM355 EVM: + +make davinci_dm355evm_config +make + +* TI DaVinci DM365 EVM: + +make davinci_dm365evm_config +make + +* TI DA830 EVM: + +make da830evm_config +make + +* DM355 based Leopard board: + +make davinci_dm355leopard_config +make + +* DM644x based schmoogie board: + +make davinci_schmoogie_config +make + +* DM644x based sffsdr board: + +make davinci_sffsdr_config +make + +* DM644x based sonata board: + +make davinci_sonata_config +make + +Bootloaders +=============== + +The DaVinci SOC's use 2 bootloaders. The low level initialization +is done by a UBL(user boot loader). The UBL is written to a NAND/NOR/SPI flash +by a programmer. During initial bootup, the ROM Bootloader reads the UBL +from a storage device and loads it into the IRAM. The UBL then loads the U-Boot +into the RAM. +The programmers and UBL are always released as part of any standard TI +software release associated with an SOC. + +Links +===== + +1) TI DaVinci DM355 EVM: +http://focus.ti.com/docs/prod/folders/print/tms320dm355.html +http://www.spectrumdigital.com/product_info.php?cPath=103&products_id=203&osCsid=c499af6087317f11b3da19b4e8f1af32 + +2) TI DaVinci DM365 EVM: +http://focus.ti.com/docs/prod/folders/print/tms320dm365.html?247SEM= +http://support.spectrumdigital.com/boards/evmdm365/revc/ + +3) DaVinci DM355 based leopard board +http://designsomething.org/leopardboard/default.aspx +http://www.spectrumdigital.com/product_info.php?cPath=103&products_id=192&osCsid=67c20335668ffc57cb35727106eb24b1 + +4) TI DaVinci DM6467 EVM: +http://focus.ti.com/docs/prod/folders/print/tms320dm6467.html +http://support.spectrumdigital.com/boards/evmdm6467/revf/ + +5) TI DaVinci DM6446 EVM: +http://focus.ti.com/docs/prod/folders/print/tms320dm6446.html +http://www.spectrumdigital.com/product_info.php?cPath=103&products_id=222 + +6) TI DA830 EVM +http://focus.ti.com/apps/docs/gencontent.tsp?appId=1&contentId=52385 +http://www.spectrumdigital.com/product_info.php?cPath=37&products_id=214 -- 1.6.0.4

2 2

[U-Boot] [PATCH 1/1] avr32/hsdramc: Move conditional compilation to Makefile
by Jean-Christophe PLAGNIOL-VILLARD 26 Nov '09

26 Nov '09

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj(a)jcrosoft.com> Cc: Haavard Skinnemoen <haavard.skinnemoen(a)atmel.com> --- cpu/at32ap/Makefile | 2 +- cpu/at32ap/hsdramc.c | 3 --- 2 files changed, 1 insertions(+), 4 deletions(-) diff --git a/cpu/at32ap/Makefile b/cpu/at32ap/Makefile index e08f273..60899c7 100644 --- a/cpu/at32ap/Makefile +++ b/cpu/at32ap/Makefile @@ -30,7 +30,7 @@ LIB := $(obj)lib$(CPU).a START-y += start.o COBJS-y += cpu.o -COBJS-y += hsdramc.o +COBJS-$(CONFIG_SYS_HSDRAMC) += hsdramc.o COBJS-y += exception.o COBJS-y += cache.o COBJS-y += interrupts.o diff --git a/cpu/at32ap/hsdramc.c b/cpu/at32ap/hsdramc.c index f74121c..b6eae66 100644 --- a/cpu/at32ap/hsdramc.c +++ b/cpu/at32ap/hsdramc.c @@ -21,7 +21,6 @@ */ #include <common.h> -#ifdef CONFIG_SYS_HSDRAMC #include <asm/io.h> #include <asm/sdram.h> @@ -116,5 +115,3 @@ unsigned long sdram_init(void *sdram_base, const struct sdram_config *config) return sdram_size; } - -#endif /* CONFIG_SYS_HSDRAMC */ -- 1.6.3.1

4 3

[U-Boot] Debugging U-boot after relocation
by Dunda, Matthias 26 Nov '09

26 Nov '09

Hi again, following up on my other message, I split them up into seperate messages, as I think there are different reasons. When I start the target from the BDI shell with "RESET RUN" and wait until the "Hit any key to stop autoboot" message appears, I can then attach to the target : Remote debugging using jtag:3333 0x1ff731ec in ?? () I then discard the symbols: (gdb) symb Discard symbol table from `...uboot/u-boot-2009.08/u-boot'? (y or n) y No symbol file now. Then, I calculate the RAM address for the symbols as described in DULG-10.1.2.: RAM is 512 MB --> 0x2000 0000 Monitor Len according to board specific file is 256k --> 0x0004 0000 This yields address 0x1FFC 0000. (gdb) add-symbol-file u-boot 0x1FFC0000 add symbol table from file "u-boot" at .text_addr = 0x1FFC0000 (y or n) y Reading symbols from ...uboot/u-boot-2009.08/u-boot...done. I then apply a breakpoint to TftpStart, which is definitely up next: (gdb) b TftpStart Breakpoint 1 at 0x1ffc6314: file tftp.c, line 474. looks like an appropriate address, anyway saying (gdb) c Continuing. never stops in TftpStart. The kernel is loaded by TFTP and the target can only be halted by pressing Ctrl-C. On the other hand, calculating the address the other way yields (gdb) print/x ((gd_t *)$r2)->reloc_off $4 = 0x1fff0000 adding this to TEXT_BASE which is ./board/freescale/mpc8568mds/config.mk:TEXT_BASE = 0xfff80000 results in something above 32 bit. What am I doing wrong here? Cheers Matthias

2 1

Re: [U-Boot] about ## Unknown FLASH on Bank 0
by Wolfgang Denk 26 Nov '09

26 Nov '09

Dear Peter Pan, please keel the mailinmg list on Cc: In message <48abf2c20910261812g75d17990jd1793f0560bc882c(a)mail.gmail.com> you wrote: > > I also think the 1.2.0 is an ancient version, so I migrate my u-boot from > 1.2.0 to u-boot-2009-08 yestoday, the same "Unknown Flash Bank" problem > happened. > I changed a little in the common files, all of which I think should not lead > to this "Unknown Flash Bank" problem. > I use MPC8247, and all my changes are: Which exact board are you using? > 1. in /common/env_common.c, I add my environment variables to array > default_environment. Bad, very bad. You should never meddle with this file. You should add your custom settings to your board config file only. > 2. in /cpu/mpc8260/cpu_init.c, in function cpu_init_f, I common this line > "immr->im_clkrst.car_rsr = RSR_ALLBITS;", because I will need RSR register > value later > 3. in /cpu/mpc8260/serial_smc.c, we use BRG1 for SMC1 instead of BRG7 You are not supposed to meddle with these files. No changes to such common files are necessary to port U-Boot to custom hardware. > 4. in /include/mpc8260.h, we add a hardware dog kick function, and modified > functiion "reset_8260_watchdog" a little to kick the hardware dog. > 5. in /common/main.c, we add support to the two jumper on our board, which > is just two "if... else...". Such changes should be done in board specific code, not in common files. > 6. in our board specific files, they all works fine before and I did not > change a thing. > Make all the changes above, the u-boot works fine. then I modified the > /common/cmd_mem.c, we make the mtest command to test memory only once(in > CFG_ALT_MEMTEST mode). > I change the "for(;;)" to for(;iterations == 1;)", then the "Unknown Flash > Bank" happens. > I printed out the 4 Flash IDs, the Manufacture Id changes from 0x01(normal) > to 0x808(wrong!!), other IDs are all normal. This makes zero sense to me. I understand you have a custom board with local modifications. That means we don't know neither your hardware nor your code, which makes it impossible to help. From the symptoms you describe, there must be something fundamentally broken with your port, but without seeing your code we cannot even guess what this might be. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de The high cost of living hasn't affected its popularity.

2 5

[U-Boot] [PATCH] NAND: Add config option for imx27lite
by s-paulraj＠ti.com 26 Nov '09

26 Nov '09

From: Sandeep Paulraj <s-paulraj(a)ti.com> We will get compilation warnings without "CONFIG_SYS_64BIT_VSPRINTF" being defined in the board config. Signed-off-by: Sandeep Paulraj <s-paulraj(a)ti.com> --- include/configs/imx27lite.h | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/configs/imx27lite.h b/include/configs/imx27lite.h index 8ebb0bb..e219ccc 100644 --- a/include/configs/imx27lite.h +++ b/include/configs/imx27lite.h @@ -156,6 +156,7 @@ #define CONFIG_SYS_NAND_BASE 0xd8000000 #define CONFIG_JFFS2_NAND #define CONFIG_MXC_NAND_HWECC +#define CONFIG_SYS_64BIT_VSPRINTF /* needed for nand_util.c */ /* * SD/MMC -- 1.6.0.4

2 1