August 2005 - U-Boot

[U-Boot-Users] Clarification - Missing tsec.c in cpu/mpc85xx ???
by Charles J Gillan 12 Aug '05

12 Aug '05

Just to clarify my previous message, there was an error in it. I did not actually modify the cpu/mpc85xx/Makefile Instead, I fixed the linker problem by removing the reference to cpu/mpc85xx/tsec.o in the u-boot.lds file for my board. I had copied this from board/tqm8540/u-boot.lds in the June 15th download. I am still puzzled as to my tsec.c was moved though. Charles. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Charles J Gillan Sent: 12 August 2005 14:01 To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Missing tsec.c in cpu/mpc85xx ??? I have a problem with a missing file. On August 10th I downloaded the latest copy of U-Boot from CVS. I found that when trying to make for an 8540 based board, I received an error from the linker that cpu/mpc85xx/tsec.o was missing. I checked the CVS repository via the Web on the SourceForge site today and confirmed that tsec.c is no longer in the cpu/mpc85xx/ directory - but exists in drivers/ instead. On checking my previous downloads (Apr 11th and June 15th) I see that the file tsec.c existed in cpu/mpc85xx. Obviously, modifying the cpu/mpc85xx/Makefile to remove tsec.o from the COBJS list fixed the problem. I want to check with the rest of the list though to see if this is maybe a symptom of something more serious that I have done wrong. Maybe it was indeed just a simple bug - hopefully! Charles. --------------------------------------------------------------------------- Dr Charles J Gillan The Institute of Electronics, Communications and Information Technology (ECIT), Queen's University Belfast, Titanic Quarter Queens Road, Queens Island, Belfast, BT3 9DT Northern Ireland, UK Tel: +44 (0) 2890 971847 Fax: +44 (0) 2890 971702 --------------------------------------------------------------------------- ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] Missing tsec.c in cpu/mpc85xx ???
by Charles J Gillan 12 Aug '05

12 Aug '05

I have a problem with a missing file. On August 10th I downloaded the latest copy of U-Boot from CVS. I found that when trying to make for an 8540 based board, I received an error from the linker that cpu/mpc85xx/tsec.o was missing. I checked the CVS repository via the Web on the SourceForge site today and confirmed that tsec.c is no longer in the cpu/mpc85xx/ directory - but exists in drivers/ instead. On checking my previous downloads (Apr 11th and June 15th) I see that the file tsec.c existed in cpu/mpc85xx. Obviously, modifying the cpu/mpc85xx/Makefile to remove tsec.o from the COBJS list fixed the problem. I want to check with the rest of the list though to see if this is maybe a symptom of something more serious that I have done wrong. Maybe it was indeed just a simple bug - hopefully! Charles. --------------------------------------------------------------------------- Dr Charles J Gillan The Institute of Electronics, Communications and Information Technology (ECIT), Queen's University Belfast, Titanic Quarter Queens Road, Queens Island, Belfast, BT3 9DT Northern Ireland, UK Tel: +44 (0) 2890 971847 Fax: +44 (0) 2890 971702 ---------------------------------------------------------------------------

2 1

[U-Boot-Users] How to build and install U-Boot?
by boku 12 Aug '05

12 Aug '05

Dear Experts, I've surfed the internet to find any helpful U-Boot how-to guidelines or tutorials but failed. Does anyone have such info for me especially for each config in it? My target is to build U-boot on ARM IntegratorAP board with ARM926EJ-S. Thanks in advance. B.R. Boku

3 2

[U-Boot-Users] DM9000 on PXA
by Hinko Kocevar 12 Aug '05

12 Aug '05

Hello, I'm half way (probably less) through porting u-boot to trizeps3 K&K cpu module that has PXA255, 32MB flash, 64MB sdram, OTG TD242Lp, DM9000 ETh and UCB1400 onboard. I'm stuck with DM9000 ethernet chip. Every packet that is recieved by the chip is supposed to be errornous. My DM9000 is at 0x08000000 and its IO port is at 0x08000000, while data port is at 0x08008000 (confirmed and working under supplied bootloader and linux). When I issue tftboot command in u-boot following is outputed if I enable debug; ... $ tftpboot a0100000 uImage eth_halt phy_write(reg:0, value:32768) eth_init() resetting dm9000 i/o: 0x8000000, id: 0x90000a46 MAC: 00:50:c2:0e:cc:ba 00:50:c2:0e:cc:ba: operating at 100M full duplex mode TFTP from server 192.168.0.77; our IP address is 192.168.0.97 Filename 'uImage'. Load address: 0xa0100000 Loading: *^Heth_send: length: 42 Send: 0x00: ff ff ff ff ff ff 00 50 Send: 0x08: c2 0e cc ba 08 06 00 01 Send: 0x10: 08 00 06 04 00 01 00 50 Send: 0x18: c2 0e cc ba c0 a8 00 61 Send: 0x20: 00 00 00 00 00 00 c0 a8 Send: 0x28: 00 4d transmit done receiving packet rx status: 0x8000 rx len: 64 eth_rx: length/4: 16 Recv: 0x00: 0ec29000 40009acc deee8d45 01008608 04068008 40008200 deee8d45 4d0088c0 Recv: 0x08: 0ec29000 a8c09acc 00008100 00008000 00008000 00008000 00008000 bc178107 rx length error ... The funny thing is that every recieved packet has bit 15 set to one (compared to ethereal dump)! It looks like address of data port is mixed in with data lines - dm9000 data port is offseted for 0x8000 on my board. This seems to happen when 32 bit access is used (for data transfer) while other register access is done in 8bit mode and that seems to function well. I have following defines for DM9000 (probably nothing special here, anyway): /* LAN is on nCS2 */ #define CONFIG_DRIVER_DM9000 1 #define CONFIG_DM9000_BASE 0x08000000 #define DM9000_IO (CONFIG_DM9000_BASE) #define DM9000_DATA (CONFIG_DM9000_BASE + 0x8000) #define CONFIG_DM9000_USE_32BIT Any comments? reagrds, hinko k -- hinko <dot> kocevar <at> iskramedical <dot> si Hinko Kocevar, embedded systems developer Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU "Aì rén" | [Analects XII:22]

2 3

Re: [U-Boot-Users] MPC8280 USB console
by KokHow Teh 12 Aug '05

12 Aug '05

One additional piece of information: "The host controller programming model does not coform to the OHCI or UHCI standards in which software drivers are hardware-independant". Regards, TEH "KokHow Teh" <KokHow.Teh(a)marconi.com>@lists.sourceforge.net on 08/12/2005 04:32:06 PM Sent by: u-boot-users-admin(a)lists.sourceforge.net To: u-boot-users(a)lists.sourceforge.net cc: Subject: [U-Boot-Users] MPC8280 USB console Hi; I am trying to bring up the USB controller on PQ2FADS-ZU with MPC8280 onboard. I have finished with the initialization and transaction routines but not the ones neccessary for usbtty to work. The u-boot-1.1.2 source tree that I am using is a release version that is definitely not from the top of the CVS. I notice that the usbtty is only implemented for the SX1 board in drivers/usbdcore_omap1510.c. Is omap1550 the name of the usb controller in arm925t core of the card? Some questions pertaining to USB requirements for usbtty to work. Sorry if this is more of usb-related rather than u-boot related. (1) The USB connector on PQ2FADS-ZU is a Type-A connector. Would this work as a console port? (2) What type of usb connections is neccessary for usbtty to work? I mean, is host PC running usb-host or usb-function and PQ2FADS-ZU running usb-host or usb-function? (3) What type of cable should I use? I assume a Type-A-to-Type-A PC-to-PC USB cable would work? How about a USB2.0 Link cable? www.usbcable.com Thanks for any input. Regards, TEH ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] Flash boot issues with MPC8272ADS and PQ2FADS
by Milligan, Keath 11 Aug '05

11 Aug '05

We are using several PQ2FADS-VR and MPC8272ADS boards for a Linux project and are experiencing a high occurrence of boards that get into a state where they will not boot or behave erratically during boot. The symptoms are usually that board continually resets in u-boot. See below for output examples. In other cases, the system will get to the point of attempting to load a kernel, but will claim the checksum is bad, or will start booting the kernel and crash shortly thereafter. When folks bring me systems in this state, my "fix" has been to replace the 8MB flash SIMM. This usually gets them going again, but I honestly don't think the SIMM is the real problem. I have one PQ2FADS board that I have put four different SIMMs in and can not get it to boot. In most other cases, I can take the "bad" SIMM, put it in another board, reprogram it and it will work again (for a while). In all of these cases, we are using known good u-boots (built from unmodified 1.1.2 source for either the PQ2FADS or MPC8272ADS) and known good, tested kernels. Typically, users will have been working for weeks without a problem until they run into this. Here is the method I am using the program the flash using the BDI2000: 8275>unlock 0xff800000 0x40000 32 8275>erase 0xff800000 0x40000 32 Erasing flash at 0xff800000 Erasing flash at ... Erasing flash at 0xfffc0000 Erasing flash passed 8275>prog 0xfff00000 u-boot.bin.pq2fads bin Programming u-boot.bin.pq2fads , please wait .... Programming flash passed 8275>verify 0xfff00000 u-boot.bin.pq2fads bin Verifying u-boot.bin.pq2fads , please wait .... Verifying target memory passed Is this incorrect? Any insight or shared experience on this is greatly appreciated. Thanks, Keath Output such as this is typical (PQ2FADS output shown, MPC8272ADS output is similar): ---------------------------------------------------------------------------- --- U-Boot 1.1.2 (Aug 9 2005 - 12:58:57) MPC8260 Reset Status: Check Stop, External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq 25-75 , Core Freq 100-300 - dfbrg 1, corecnf 0x0a, busdf 3, cpmdf 1, plldf 0, pllmf 3 - vco_out 264000000, scc_clk 66000000, brg_clk 16500000 - cpu_clk 264000000, cpm_clk 132000000, bus_clk 66000000 - pci_clk 44000000 CPU: MPC8260 (HiP7 Rev 11, Mask 0.0 0K49M) at 264 MHz Board: Motorola PQ2FADS-ZU DRAM: 32 MB FLASH: ---------------------------------------------------------------------------- --- <reboot happens here> Sometimes, we will see garbage output to the serial port while this is happening. Occasionally, we will see some crash dump info, but not usually. Example: ---------------------------------------------------------------------------- --- U-Boot 1.1.2 (Aug 9 2005 - 12:58:57) MPC8260 Reset Status: External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq 25-75 , Core Freq 100-300 - dfbrg 1, corecnf 0x0a, busdf 3, cpmdf 1, plldf 0, pllmf 3 - vco_out 264000000, scc_clk 66000000, brg_clk 16500000 - cpu_clk 264000000, cpm_clk 132000000, bus_clk 66000000 - pci_clk 44000000 CPU: MPC8260 (HiP7 Rev 11, Mask 0.0 0K49M) at 264 MHz Board: Motorola PQ2FADS-ZU DRAM: 32 MB FLASH: 8 MB In: serial Out: serial Err: serial Bad trap at PC: 248, SR: 0, vector=800 4NIP: 00000248 XER: 00000000 LR: 01FE64F8 REGS: 01fefea1 TRAP: 0800 DAR: 01FFE04 MSR: 00000000 EE: 0 PR: 0 FP: 1fefea1 ME: 0 IR/DR: 1ffe0240 GPR00: 03FCD7C0 01B88AA0 FFFFFFFF 01B88B5D 01FEFCD3 00000010 FFFFFFFE 00000000 GPR08: 00000001 01FDDAEC 00000000 01FEFCD4 00000030 FFFFFFFF 01FFE000 020C9000 GPR16: FFFFFFFF EFFFFFFF FFFFFFFF FFEFFEFF 00000000 01B889A0 821CDAD8 01FCC098 GPR24: 01B88B50 00000000 00000008 00000000 01B88B62 01B88F6C 00001466 01B88B40 Call backtrace: 01FE64F8 00000010 FFFFFFFE 01B88858 00000041 00000010 00000000 01B889B0 01B889B0 01B889B0 01B889B0 Exception in kernel pc 248 signal 0 ---------------------------------------------------------------------------- --- <reboot> As I mentioned above, these are just a couple of examples, output varies from board to board and boot-attempt to boot-attempt.

4 4

[U-Boot-Users] 85xx - DDR with ECC: Why DMA ?
by Charles J Gillan 11 Aug '05

11 Aug '05

I have a question about the procedure ddr_enable_ecc() included in the U-Boot build only if CONFIG_DDR_ECC is defined CONFIG_ECC_INIT_VIA_DDRCONTROLLER is not defined The routine is found in file ./cpu/mpc85xx/spd_sdram.c so is for the 8540 and 8560 products. Most of the work in the routine seems to concern programming the DMA registers rather than setting the DDR "enable" flag. Why is this DMA configuration an essential step when ECC is used and apparently not necessary when it is not used? I cant see the link between the two. Thanks, Charles. -------------------------------------------------------------------------- Dr Charles J Gillan The Institute of Electronics, Communications and Information Technology (ECIT), Queen's University Belfast, Titanic Quarter Queens Road, Queens Island, Belfast, BT3 9DT Northern Ireland, UK Tel: +44 (0) 2890 971847 Fax: +44 (0) 2890 971702 --------------------------------------------------------------------------

2 1

[U-Boot-Users] Kernel does not boot
by Andy Chuo 11 Aug '05

11 Aug '05

Hi all, I'm having difficulties booting my kernel. I've checked the followings: 1. CONFIG_CMDLINE_TAG, CONFIG_SETUP_MEMORY_TAGS and CONFIG_INITRD_TAG all enabled. (#define as 1 in my include/configs/myboard.h file) 2. the machines descriptor in my board specific file under linux/arch/arm/myboard.c as follows: MACHINE_START(LP2A, "SOCLE-LP2A") MAINTAINER("Socle Ltd/DE1") BOOT_MEM(0x40000000, 0x1e800000,0x9e800000) BOOT_PARAMS(0x40000100) FIXUP(fixup_lp2a) MAPIO(lp2a_map_io) INITIRQ(lp2a_init_irq) MACHINE_END Few notes: * Kernel version is 2.4.21.rmk2 and was obtained from www.kernel.org <http://www.kernel.org/> , cross compiler tool was from www.gnuarm.com <http://www.gnuarm.com/> - version 3.4.3. * It seems that misc.c does the decompression of the kernel again, when kernel is already decompressed by u-boot to the load address 0x40008000. * Do I have to modify head.S at all? I am pretty sure that I've done pretty much everything u-boot needs to boot my kernel but it just won't do it (attached below is the log of the output from the board). Can anyone help please? Thanks in advance! Andy uP-Boot 1.3 (May 31 2005 - 10:24:23) U-Boot code: 40400000 -> 40445A54 BSS: -> 40462508 IRQ Stack: 403def7c FIQ Stack: 403ddf7c RAM Configuration: Bank #0: 40000000 64 MB Board: SOCLE LeopardII.A erase_region_count = 64 erase_region_size = 131072 erase_region_count = 64 erase_region_size = 131072 Flash: 16 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 3 2 1 0 enter cmd_bootm1 ## Booting image at 1f100000 ... Image Name: Linux Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 621593 Bytes = 607 kB Load Address: 40008000 Entry Point: 40008000 checksum enter Verifying Checksum ... OK checksum out Uncompressing Kernel Image ... OK ## Loading Ramdisk Image at 1f300000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1026439 Bytes = 1002.4 kB Load Address: 40800000 Entry Point: 40800000 Verifying Checksum ... OK OK Starting kernel ... (<------------------------- just hangs here!)

1 0

[U-Boot-Users] version mismatch
by zhonglei 11 Aug '05

11 Aug '05

hi How can I compile the kernel as the no-Version Dependency to avoid the warning : kernel-module version mismatch when I use "insmod hello.o" . BestRegards zhonglei

2 1

AW: [U-Boot-Users] Flash boot issues with MPC8272ADS and PQ2FADS
by Jonas Mark (ST/EPP1) * 10 Aug '05

10 Aug '05

Keith, > We are using several PQ2FADS-VR and MPC8272ADS boards for a Linux > project and are experiencing a high occurrence of boards that get > into a state where they will not boot or behave erratically during > boot. [...] > When folks bring me systems in this state, my "fix" has been to > replace the 8MB flash SIMM. This usually gets them going again, but I > honestly don't think the SIMM is the real problem. I have one PQ2FADS > board that I have put four different SIMMs in and can not get it to > boot. In most other cases, I can take the "bad" SIMM, put it in > another board, reprogram it and it will work again (for a while). [...] > known good, tested kernels. Typically, users will have been working > for weeks without a problem until they run into this. [...] > Any insight or shared experience on this is greatly appreciated. >From my experience a possible answer to your problem is that the contact metal of the board connector does not match the metal of the contact area on your SIMMs. I saw similar problems before with self-built SDRAM SIMMs. The only way to get it working reliably was to use a board connector with gold plated contacts and to use a SIMM with a gold plated PCB. I am not a chemist or physicist but I think else the two different materials after a while build up some strange alloy / oxide that ruins the contact. What's the plating of your board connector and what's the plating of the SIMM contact area? Regards Mark

1 0