April 2009 - U-Boot

Re: [U-Boot] use of C99
by Pink Boy 09 Apr '09

09 Apr '09

Premi, Sanjeev sez, > I was referring to declaring variable within #ifdefs with > belief that > use will be contained. > > e.g. > #ifdef CONFIG_COOL_FEATURE > int i; > int* ptr ; > ... > ... > #endif > > ... > ... 2 screenful down; in same function... > ... > > #ifdef CONFIG_HOT_FEATURE > u32 i; > void* ptr; > ... > ... > #endif > > Maybe for sometime the usage seems contained. Until someone > decides to have both the COOL and HOT feature. Pops out of hole, looks at shadow, 6 more weeks till we ship... Um... my feeling is that if one is going to declare a variable inside a #ifdef then that variable ought to be called something like int indx_CONFIG_COOL_FEATURE and u32 indx_CONFIG_HOT_FEATURE Matt Harper Tehama Wireless

4 3

[U-Boot] use of C99
by Kumar Gala 09 Apr '09

09 Apr '09

I was wondering if there was any reason we avoid C99 features in u- boot source. Specifically the ability to declare variables in the middle of functions. There are a slew of places that we have something like: foobar() { ... #ifdef CONFIG_COOL_FEATURE u32 myvarrocks; #endif ... #ifdef CONFIG_COOL_FEATURE myvarrocks = foo * bar * bar; gd->neato = myvarrocks #endif it would be nice to just have: foobar() { ... #ifdef CONFIG_COOL_FEATURE u32 myvarrocks = foo * bar * bar; gd->neato = myvarrocks #endif - k

10 24

[U-Boot] : Bus Fault issue in MPC8313ERDB Custom board
by rudresh 09 Apr '09

09 Apr '09

Hi All, I am using u-boot 1.1.6 in MPC8313ERDB custom board. when i'm doing Ethernet(tftp) test after 10th iteration "Bus Fault" error occur and restart the board. The error message is as follows. ##############################################Bus Fault @ 0x00000900, fixup 0x00000000 Machine check in kernel mode. Caused by (from msr): regs 07f85378 Unknown values in msr NIP: 00000900 XER: 00000000 LR: 07FB4A8C REGS: 07f85378 TRAP: 0200 DAR: 20000000 MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00 GPR00: 0803BAE4 07F85468 00000080 07F89CB8 07FFE5A6 00000000 07F85420 07FED124 GPR08: 07FEDBA0 E0024000 07FEDB98 0008362A 07F85348 F40A8804 07FF0000 09FA8000 GPR16: 6B577F13 00000000 00000000 00000000 00000000 00000000 00000000 00000000 GPR24: 07F8ADB8 00000000 07F85FBC 00000003 00000000 07F85F58 0FFF0570 E0025000 Call backtrace: 07FC7268 07FAFB74 07FAE034 07FC4718 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 07FCB4C4 07FCB6D0 07FBAAB8 07FCBDD0 machine check Resetting the board. i'm not understanding this isssue. please help me to fix this issue. Thanks Rudresh -- View this message in context: http://www.nabble.com/-U-Boot-%3A-Bus-Fault-issue-in-MPC8313ERDB-Custom-boa… Sent from the Uboot - Users mailing list archive at Nabble.com.

2 1

[U-Boot] Interrupt handlers in u-boot
by prathika 09 Apr '09

09 Apr '09

Hi, I am working on u-boot 1.1.6 version for PowerPC 440.I am using the hello world application from the examples folder. I had no issues in loading and executing it. Now I have enabled SPI interrupt in the application. I have written for SPI loopback. My issue is, as there is no interrupt handler defined for the SPI in uboot, whenever i execute my application, it says "Masking bogus interrupt for Vector 0x08". I am calling "install_irq_handler" function for assigning my own interrupt handler for SPI as part of my application itself. I can understand that, there is no exclusive handler for SPI in uboot, so it is disabling the SPI interrupt and printing the BOGUS INTERRUPT message. Now how do I get rid of this and have my own interrupt handler?? Some one please help. Thanks all in advance. Thanks & Regards, Prathika R

2 5

[U-Boot] Multiple device support -- sorry state :(
by ksi＠koi8.net 08 Apr '09

08 Apr '09

OK, this is _NOT_ just multiple I2C adapters... The entire thing is fundamentally broken. One supposed to have _THE_ device and only this device is somehow supported. Now it is USB. Each and every USB driver exports the same set of functions, submit_XXX_msg(...) That means there can be one and only one USB device in the system. Let's take e.g. widely used ISP1563 PCI USB controller. It has _TWO_ OHCI controllers. Existing usb_ohci.c code only supports one. That means that one can only use odd numbered ports (1 and 3) for any USB devices. Ports 2 and 4 are not usable at all. Not just together with odd numbered ones but even _INSTEAD_ of those. But wait, there is more... This very same controller also has a 4-port EHCI controller for USB 2.0 support. This is not supported at all because usb_ehci_pci.c is a mere stub that does NOT support _ANY_ PCI EHCI controller. But it would not do any good if it did support ISP1563 -- there should be one and only one USB controller, _THE_ USB controller... EHCI driver, usb_ehci_core.c exports exactly the same submit_XXX_msg() set of function so it can _NOT_ coexist with anything else. So what's the choice? Let's say we somehow made that usb_ehci_pci.c stub in a real driver and got ISP1563 (or _ANY_ other USB2.0 PCI adapter) recognized and initialized. This hypothetically gives us all 4 ports because all 4 are supported by EHCI vs. only 2 by OHCI. Would it do any good? The answer is _NO_. EHCI does _NOT_ support slower USB1.X ports so one can _NOT_ hook his e.g. USB keyboard to EHCI controller. It is only for hi-speed devices. USB2.0 controller actually consists of an EHCI and set of slower USB1.X controllers that share the same USB pins. If a connected device supports high speed, EHCI is used. If it does NOT support high speed, driver should made EHCI controller to give up ownership of that particular USB port to OHCI (or whatever it is) and pass control to OHCI driver. That is how USB works. Now we suddenly have _THREE_ USB controllers while our software only supports one. And that is _NOT_ some exotic situation with multiple chips or other strange design -- e.g. MPC8548 does NOT have a built-in USB controller so I added a single PCI chip to provide for a USB interface. One can recommend using only the first OHCI controller in U-Boot somehow tolerating it being painfully slow with storage devices etc. and limited with what ports can be used but that is also _NOT_ a solution... OHCI only allows for 2 ports and in our case they are both already used (KBD + MOUSE.) Sure we don't need a mouse in U-Boot but we _DO_ need it to be connected anyways because we boot full-blown Fedora with X that uses mouse. That means we do NOT have any USB ports available for storage or anything else... USB keyboard is another grand kludge deserving its own chapter... As of now one can only switch to it from command line because USB is not even initialized until do_usb() from cmd_usb.c is called... What if we do NOT have a serial console at all? Grrr... --- ****************************************************************** * KSI@home KOI8 Net < > The impossible we do immediately. * * Las Vegas NV, USA < > Miracles require 24-hour notice. * ******************************************************************

3 10

[U-Boot] Query: console.c
by Premi, Sanjeev 08 Apr '09

08 Apr '09

Hi, While browsing common/console.c, I found 2 banners: - U-Boot INITIAL CONSOLE-NOT COMPATIBLE FUNCTIONS - U-Boot INITIAL CONSOLE-COMPATIBLE FUNCTION What does this indicate? One first pass, I also appeared that some functionality is duplicated e.g. serial_puts, puts, serial_printf, printf, et. Is there a specific reason for it? Best regards, Sanjeev

1 0

[U-Boot] UBIFS - Reading superblock error
by DATACOM - Mallmann 08 Apr '09

08 Apr '09

Hi, I'm trying to use UBI and UBIFS over a nand device. I want to create a mtd partition in u-boot (with ubi part command), save a ubifs image (with mkfs.ubifs), mount and load it with ubifs commands. The commands that I used are listed bellow: (environment) mtdids=nand0=nand mtdparts=mtdparts=nand:64m(allstuff) partition=nand0,0 mtddevnum=0 mtddevname=allstuff => ubi part nand allstuff Creating 1 MTD partitions on "NAND 64MiB 3,3V 8-bit": 0x00000000-0x04000000 : "mtd=0" UBI: attaching mtd0 to ubi0 UBI: physical eraseblock size: 16384 bytes (16 KiB) UBI: logical eraseblock size: 15872 bytes UBI: smallest flash I/O unit: 512 UBI: sub-page size: 256 UBI: VID header offset: 256 (aligned 256) UBI: data offset: 512 UBI: empty MTD device detected UBI: create volume table (copy #1) UBI: create volume table (copy #2) UBI: attached mtd0 to ubi0 UBI: MTD device name: "mtd=0" UBI: MTD device size: 64 MiB UBI: number of good PEBs: 4096 UBI: number of bad PEBs: 0 UBI: max. allowed volumes: 92 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 0 UBI: available PEBs: 4052 UBI: total number of reserved PEBs: 44 UBI: number of PEBs reserved for bad PEB handling: 40 UBI: max/mean erase counter: 0/0 => ubi create vol Creating dynamic volume vol of size 64313344 => ubi info l UBI: volume information dump: UBI: vol_id 0 UBI: reserved_pebs 4052 UBI: alignment 1 UBI: data_pad 0 UBI: vol_type 3 UBI: name_len 3 UBI: usable_leb_size 15872 UBI: used_ebs 4052 UBI: used_bytes 64313344 UBI: last_eb_bytes 15872 UBI: corrupted 0 UBI: upd_marker 0 UBI: name vol UBI: volume information dump: UBI: vol_id 2147479551 UBI: reserved_pebs 2 UBI: alignment 1 UBI: data_pad 0 UBI: vol_type 3 UBI: name_len 13 UBI: usable_leb_size 15872 UBI: used_ebs 2 UBI: used_bytes 31744 UBI: last_eb_bytes 2 UBI: corrupted 0 UBI: upd_marker 0 UBI: name layout volume tftp 1000000 image.ubifs vol ${filesize} => ubi write 1000000 vol ${filesize} Volume "vol" found at volume id 0 => ubifsmount vol UBIFS error (pid 0): ubifs_check_node: bad node length 4100 UBIFS error (pid 0): ubifs_check_node: bad node at LEB 0:0 UBIFS error (pid 0): ubifs_read_node: expected node type 6 Error reading superblock on volume 'ubi:vol'! image.ubifs was generated with the follow command: mkfs.ubifs -r /ubifs -m 256 -c 2180 -e 16KiB -v -g 3 -o image.ubifs (/ubifs contains a kernel+ramdisk cramfs image.) My question is if the error was in image.ubifs creation or some u-boot configuration. I can't find where u-boot takes this 4100 length from. By the way, is a volume created in u-boot able to be used in linux kernel in read-write mode? Thanks in advance, Marcelo

2 2

[U-Boot] dtb merge
by Andre Schwarz 08 Apr '09

08 Apr '09

Any ideas on how to merge device tree binaries from slave devices ? Having a PowerPC based board with various extension boards on e.g. the local bus with each board having some kind of PROM device (I2C, SPI etc.) containing a dtb ... is it possible to merge this into the existing boards dtb into the local bus node ? Is it already working - have I missed it ? If not - is someone thinking/working on it ? Any suggestions on how to do it ? Regards, Andre MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Hans-Joachim Reich

2 1

[U-Boot] Ping on Coldfire patch status
by Richard Retanubun 08 Apr '09

08 Apr '09

Hi John, Just wanted to ping on the status of the Coldfire patches I submitted, I noticed the submission window is closed on 2009.06 :) http://www.nabble.com/-U-Boot---PATCH--Coldfire-M5271%3A-Activate-u-boot-sy… http://www.nabble.com/-U-Boot---PATCH--Coldfire%3A-interrupts%3A-Add-watchd… http://www.nabble.com/-U-Boot---PATCH--Coldfire%3A-cleanup-compiler-warning… http://www.nabble.com/-U-Boot---PATCH--Coldfire%3A-I2C%3A-Update-I2CFDR-fre… Thanks for your time - Richard

1 0

[U-Boot] porting u-boot and linux for ARM9 on WinXP
by ranjan.dash1＠wipro.com 08 Apr '09

08 Apr '09

Hi Guys, I have few querries. 1> I want to port u-boot and linux for ARM9 architecture on Wndows XP. is it possible? 2> If yes, please let me know how. 3> and also let me know which ARM toolchain I would use, and from where I wud download the kernel source tree? 4> How to unzip on windows XP (tar,.bz2 files) Kindly find some time for reolve it. With Regards Ranjan Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0