Problem with ibm ppc 405 processor. Pretty confused thing that this is hard to patch to work with ibm ppc 405!!!
On Wed, May 14, 2008 at 10:54 PM, < u-boot-users-request@lists.sourceforge.net> wrote:
Send U-Boot-Users mailing list submissions to u-boot-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/u-boot-users or, via email, send a message with subject or body 'help' to u-boot-users-request@lists.sourceforge.net
You can reach the person managing the list at u-boot-users-owner@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of U-Boot-Users digest..."
Today's Topics:
- Re: build u-boot error: No rule to make target `.depend', needed by `_depend'. (Wolfgang Denk)
- Re: [PATCH 2/2] Added support for Aztek Networks cta5000s telecom board. (Wolfgang Denk)
- Re: [PATCH] MPC85xx: Change traps.c to not reference non-addressable memory (Kim Phillips)
- Re: [PATCH] MPC85xx: Change traps.c to not reference non-addressable memory (Becky Bruce)
- Re: Loading a kernel on MX31ADS using U-boot (Fabio Estevam)
- A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT) (Niklaus Giger)
Message: 1 Date: Wed, 14 May 2008 20:49:26 +0200 From: Wolfgang Denk wd@denx.de Subject: Re: [U-Boot-Users] build u-boot error: No rule to make target `.depend', needed by `_depend'. To: "Steven Woody" narkewoody@gmail.com Cc: u-boot-users@lists.sourceforge.net Message-ID: 20080514184926.63F59248C8@gemini.denx.de Content-Type: text/plain; charset=ISO-8859-1
Steven,
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
And you not only top-post, you also full-quote.
You are ignoring Netiquette more or less completely, are you aware of this?
I think you should read http://www.netmeister.org/news/learn2quote.html really carefully.
In message ed4892840805141049v3f7b2828w6d5ee74cf1923e09@mail.gmail.com you wrote:
1.2.0 is come frome eldk-4.1 iso file. Downloading independent u-boot seems require `git' tool which I get problem with because my office network gets many limits. Is there a http way to download u-boot?
If you bothered to read the documentation or tyhe U-Boot web pages you should have seen the links to the FTP site, and you should have read about the snapshot feature of git.
Please see http://www.denx.de/wiki/UBoot/SourceCode
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@denx.de I have a theory that it's impossible to prove anything, but I can't prove it.
Message: 2 Date: Wed, 14 May 2008 20:54:34 +0200 From: Wolfgang Denk wd@denx.de Subject: Re: [U-Boot-Users] [PATCH 2/2] Added support for Aztek Networks cta5000s telecom board. To: Jim Black jblack547@gmail.com Cc: u-boot-users@lists.sourceforge.net, Jim Black jblack@azteknetworks.com Message-ID: 20080514185434.244B9248C8@gemini.denx.de Content-Type: text/plain; charset=ISO-8859-1
In message 1210781443-6819-3-git-send-email-jblack@azteknetworks.com you wrote:
board/cta5000s/Makefile | 50 +++ board/cta5000s/config.mk | 30 ++ board/cta5000s/cta5000s.c | 575 +++++++++++++++++++++++++++++++++++ include/configs/cta5000s.h | 723
++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 1378 insertions(+), 0 deletions(-) create mode 100644 board/cta5000s/Makefile create mode 100644 board/cta5000s/config.mk create mode 100644 board/cta5000s/cta5000s.c create mode 100644 include/configs/cta5000s.h
There is trailing white space in some of the files.
Please use TABs for indentation instead of spaces (Not only at the beginning of the lines).
+/* See include/configs/cta5000s.h for CFG_* settings
- All values in the following tables taken from
- chapter 6 of the cta Programmer's Guide
- */
...
+/* Compact Flash Control Registers
- */
...
+/* Compact Flash IO memory
- */
These comments, and many others, are not in the requested format for multiline comments.
And I dare to ask if this:
+/* FPGA memory
- */
really requires a multiline comment?
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@denx.de The more we disagree, the more chance there is that at least one of us is right.
Message: 3 Date: Wed, 14 May 2008 13:57:32 -0500 From: Kim Phillips kim.phillips@freescale.com Subject: Re: [U-Boot-Users] [PATCH] MPC85xx: Change traps.c to not reference non-addressable memory To: becky.bruce@freescale.com Cc: u-boot-users@lists.sourceforge.net Message-ID: 20080514135732.a12d2b13.kim.phillips@freescale.com Content-Type: text/plain; charset=US-ASCII
On Wed, 14 May 2008 13:10:04 -0500 becky.bruce@freescale.com wrote:
From: Becky Bruce becky.bruce@freescale.com
Currently, END_OF_RAM is used by the trap code to determine if we should attempt to access the stack pointer or not. However, on systems with a lot of RAM, only a subset of the RAM is guaranteed to be mapped in and accessible. Change END_OF_RAM to use get_effective_memsize() instead of using the raw ram size out of the bd.
Signed-off-by: Becky Bruce becky.bruce@freescale.com
what, no love for 4xx, 83xx, and 74xx_7xx?
can also be made a single patch for WD to apply directly.
Kim
Message: 4 Date: Wed, 14 May 2008 15:31:43 -0500 From: Becky Bruce becky.bruce@freescale.com Subject: Re: [U-Boot-Users] [PATCH] MPC85xx: Change traps.c to not reference non-addressable memory To: Kim Phillips kim.phillips@freescale.com Cc: u-boot-users@lists.sourceforge.net Message-ID: 7D0431BD-E54C-42C2-AB52-EDDEFDF715DA@freescale.com Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
On May 14, 2008, at 1:57 PM, Kim Phillips wrote:
On Wed, 14 May 2008 13:10:04 -0500 becky.bruce@freescale.com wrote:
From: Becky Bruce becky.bruce@freescale.com
Currently, END_OF_RAM is used by the trap code to determine if we should attempt to access the stack pointer or not. However, on systems with a lot of RAM, only a subset of the RAM is guaranteed to be mapped in and accessible. Change END_OF_RAM to use get_effective_memsize() instead of using the raw ram size out of the bd.
Signed-off-by: Becky Bruce becky.bruce@freescale.com
what, no love for 4xx, 83xx, and 74xx_7xx?
The other platforms currently set a hard limit that should still be valid - I just changed the ones that were reading memsize directly out of the bd.
can also be made a single patch for WD to apply directly.
Sure, I just split it up in case there was some reason we shouldn't do it for one of them.
-B
Message: 5 Date: Wed, 14 May 2008 13:53:28 -0700 (PDT) From: Fabio Estevam fabioestevam@yahoo.com Subject: Re: [U-Boot-Users] Loading a kernel on MX31ADS using U-boot To: Guennadi Liakhovetski g.liakhovetski@gmx.de, Jens Gehrlein sew_s@tqs.de Cc: u-boot-users@lists.sourceforge.net Message-ID: 209131.47056.qm@web51011.mail.re2.yahoo.com Content-Type: text/plain; charset=us-ascii
Hi Jens,
Have you tried to pass the "jtag=on" option into the kernel command line?
Regards,
Fabio Estevam
--- On Wed, 5/14/08, Jens Gehrlein sew_s@tqs.de wrote:
From: Jens Gehrlein sew_s@tqs.de Subject: Re: [U-Boot-Users] Loading a kernel on MX31ADS using U-boot To: "Guennadi Liakhovetski" g.liakhovetski@gmx.de Cc: u-boot-users@lists.sourceforge.net Date: Wednesday, May 14, 2008, 4:08 AM Hi Guennadi,
Guennadi Liakhovetski schrieb:
...
Apart from that, verify that your console=
command line parameter is correct, your machine ID
matches, and that you
don't have a jtag debugger like bdi2000 connected
when you're trying to
boot.
I have the same problem on our board: I don't see the console outputs if the BDI2000 cable is connected to the target, although the BDI is in mode "reset run". Do have an idea why?
Best Regards, Jens
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Message: 6 Date: Wed, 14 May 2008 22:54:16 +0200 From: Niklaus Giger niklaus.giger@member.fsf.org Subject: [U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT) To: u-boot-users@lists.sourceforge.net Message-ID: 200805142254.16731.niklaus.giger@member.fsf.org Content-Type: text/plain; charset="iso-8859-1"
Hi
It took me a evening to put everything together. Therefore I send this mail hoping it may help somebody else. Hopefully some of the content will find its way into the DULG/FAQ, may as point 14.3.30. "Booting using flattened device tree (FDT)"
First one needs a recent U-boot with FDT support compiled into, e.g 1.3.2-rc3-g772003e4-dirty (Apr 11 2008 - 15:56:0 for the sequoia board.
Secone one needs a recent Linux kernel made using "ARCH=powerpc", e.g. from 2.6.25-00002-ga9bf9f0 from git://www.denx.de/git/linux-2.6-denx.git.
Third one needs a recent dtc (Device Tree Compiler). The following commands $ git clone http://www.jdl.com/software/dtc.git $ cd dtc && make && sudo cp dtc /usr/local/bin should do the job.
Now you are ready to compile the device tree blob. I used the commands given in http://www.denx.de/wiki/view/DULG/LinuxFDTBlob dtc -b 0 -V 17 -R 4 -S 0x3000 -I dts -O dtb -f arch/powerpc/boot/dts/sequoia.dts \
/tftpboot/sequoia/sequoia.dtb
Now power up your sequoia board and execute the following commands to start a Linux kernel on a NFS root device. The following commands did the job for me:
Hit any key to stop autoboot: 0 => tftp 200000 /tftpboot/sequoia/uImage Waiting for PHY auto negotiation to complete.. done ENET Speed is 100 Mbps - FULL duplex connection (EMAC0) Using ppc_4xx_eth0 device TFTP from server 172.25.1.3; our IP address is 172.25.1.88 Filename '/tftpboot/sequoia/uImage'. Load address: 0x200000 Loading:
#################################################################
######################done Bytes transferred = 1277067 (137c8b hex) => tftp 1000000 /tftpboot/sequoia/sequoia.dtb ENET Speed is 100 Mbps - FULL duplex connection (EMAC0) Using ppc_4xx_eth0 device TFTP from server 172.25.1.3; our IP address is 172.25.1.88 Filename '/tftpboot/sequoia/sequoia.dtb'. Load address: 0x1000000 Loading: # done Bytes transferred = 12288 (3000 hex) => run nfsargs addip addtty => printenv bootargs bootargs=root=/dev/nfs rw nfsroot=172.25.1.3:/opt/eldk/ppc_4xxFP ip=172.25.1.88:172.25.1.3:::sequoia:eth0:off panic=1
console=ttyS0,115200
=> fdt addr 1000000 => fdt chosen => fdt list
<...>
=> fdt print
<...>
=> bootm 200000 - 1000000 ## Booting image at 00200000 ... Image Name: Linux-2.6.25-00002-ga9bf9f0 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1277003 Bytes = 1.2 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Booting using the fdt at 0x1000000 Loading Device Tree to 007fc000, end 007fefff ... OK Using Sequoia machine description
<...>
Thats it. Now you should boot into your shiny new Linux kernel. Attached is a gzipped output of my startup (for the curious).
Once my kernel started I used the following commands to update my u-boot environment:
setenv ftd_get 'tftp 200000 ${bootfile};tftp 1000000
sequoia/sequoia.dtb;fdt addr 1000000;'
setenv net_nfs 'run ftd_get nfsargs addip addtty; fdt chosen;bootm 200000
- 1000000'
saveenv
Best regards
Niklaus