Home / Browse / Das U-Boot - Universal Bootloader / Mail / Archive

Das U-Boot - Universal Bootloader

Email Archive: u-boot-users (read-only)

2002:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov (181)	_Dec (70)
2003:	_Jan (125)	_Feb (184)	_Mar (402)	_Apr (263)	_May (228)	_Jun (340)	_Jul (279)	_Aug (238)	_Sep (284)	_Oct (282)	_Nov (270)	_Dec (237)
2004:	_Jan (346)	_Feb (533)	_Mar (470)	_Apr (395)	_May (317)	_Jun (448)	_Jul (501)	_Aug (396)	_Sep (461)	_Oct (432)	_Nov (391)	_Dec (374)
2005:	_Jan (405)	_Feb (309)	_Mar (365)	_Apr (350)	_May (419)	_Jun (479)	_Jul (321)	_Aug (416)	_Sep (385)	_Oct (345)	_Nov (462)	_Dec (163)
2006:	_Jan (378)	_Feb (295)	_Mar (499)	_Apr (587)	_May (495)	_Jun (460)	_Jul (545)	_Aug (557)	_Sep (293)	_Oct (563)	_Nov (631)	_Dec (361)
2007:	_Jan (485)	_Feb (522)	_Mar (783)	_Apr (673)	_May (802)	_Jun (671)	_Jul (835)	_Aug (1080)	_Sep (691)	_Oct (831)	_Nov (887)	_Dec (717)
2008:	_Jan (1674)	_Feb (1191)	_Mar (1561)	_Apr (1491)	_May (1442)	_Jun (1145)	_Jul (1821)	_Aug (538)	_Sep (89)	_Oct (123)	_Nov (64)	_Dec (74)
2009:	_Jan (36)	_Feb (44)	_Mar (57)	_Apr (105)	_May (178)	_Jun (160)	_Jul (70)	_Aug	_Sep	_Oct	_Nov	_Dec (2)
2010:	_Jan (9)	_Feb (4)	_Mar	_Apr (1)	_May	_Jun (3)	_Jul	_Aug	_Sep	_Oct	_Nov (1)	_Dec (1)
2011:	_Jan	_Feb	_Mar (3)	_Apr	_May (1)	_Jun	_Jul	_Aug	_Sep	_Oct (1)	_Nov	_Dec
2012:	_Jan (6)	_Feb (10)	_Mar	_Apr (7)	_May (3)	_Jun	_Jul	_Aug (1)	_Sep (1)	_Oct	_Nov	_Dec (1)
2013:	_Jan	_Feb (2)	_Mar	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec


S	M	T	W	T	F	S
		1	2	3	4	5
		(30)	(16)	(5)	(1)
6	7	8	9	10	11	12
(1)	(7)	(7)	(15)	(12)	(7)
13	14	15	16	17	18	19
(4)	(6)	(4)	(15)	(6)	(14)	(10)
20	21	22	23	24	25	26
(1)	(8)	(11)	(7)	(22)	(15)	(8)
27	28	29	30	31
(9)	(11)	(6)	(10)	(11)

[U-Boot-Users] BDI error

From: Rune Torgersen <runet@in...> - 2003-07-10 21:25

Hi
Have anybody seen this BDI error and have an idea why it happens?
The board is based on a 8266.
(FLASH is programed with HRCW (0x08b23645) starting at address 0xff800000)

- TARGET: waiting for target Vcc
- TARGET: processing power-up delay
- TARGET: processing user reset request
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x55 => 0xAA
- Bypass check: 0x55 => 0xAA
- JTAG exists check passed
- Target PVR is 0x80911014
- COP status is 0x01
- Check running state passed
- BDI scans COP freeze command
- BDI removes HRESET
- COP status is 0x05
- Check stopped state passed
- Check LSRL length passed
- BDI sets breakpoint at 0xFFF00100
- BDI resumes program execution
- COP status is 0xF1
- Waiting for target stop failed
- TARGET: Break at boot vector failed, freeze forced
- TARGET: Target PVR is 0x80911014
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed

Rune Torgersen
System Developer
Innovative Systems LLC
1000 Innovative Drive
Mitchell, SD 57301
Ph: 605-995-6120
 http://www.innovsys.com

Re: [U-Boot-Users] U-boot on EP8260 Board

From: <mss59@at...> - 2003-07-10 15:58

Thanks for the tip.
Now I am using uImage file to boot MV Kernel from U-boot on Embedded Planet 
EP8260 board. But it seems to be stuck after uncompressing:

=>tftp 0x400000 uImage.ep8260
ARP broadcast 1
TFTP from server 10.0.0.1; our IP address is 10.0.0.2
Filename 'uImage.ep8260'.
Load address: 0x400000
Loading: #################################################################
         ###############################################################
done
Bytes transferred = 655335 (9ffe7 hex)

=> imi    
## Checking Image at 00400000 ...
   Image Name:   MV Linux Kernel Image for EP8260
   Created:      2003-07-10  13:09:51 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    655271 Bytes = 639.9 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

=> bootm 0x400000
## Booting image at 00400000 ...
   Image Name:   MV Linux Kernel Image for EP8260
   Created:      2003-07-10  13:09:51 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    655271 Bytes = 639.9 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Nothing happens after this.

I tried to enable the Pipeline in the boot which results in some extra 
characters after "Uncompressing Kernel Image ... OK". 

I used following to make uImage.ep8260 file

../u-boot-0.3.0/tools/mkimage -A ppc -O linux -T kernel -C gzip -a 0 -e 0 -
n "MV Linux Kernel Image for EP8260" -
d /prj3/kernel/arch/ppc/boot/images/vmlinux.gz /tftpboot/uImage.ep8260

Thanks

MSS//
> In message <E19aLYj-0004yx-00@...> you wrote:
> > I am using u-boot to boot an EP8260 board. However once I load/tftp Kernel ELF 
> > file to 0x400000 and try to run the kernel from 0x410000, it crashes...
> > I used the same ELF file with Embedded planet's boot loader and it works fine.
> > Any pointers....
> 
> Read the README. U-Boot does not use ELF files to boot Linux.
> 
> 
> Wolfgang Denk
> 
> -- 
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@...
> The human race is faced with a cruel choice: work  or  daytime  tele-
> vision.

Re: [U-Boot-Users] U-boot on EP8260 Board

From: Wolfgang Denk <wd@de...> - 2003-07-10 20:30

In message <20030710152137.56D1143076@...> you wrote:
> Thanks for the tip.
> Now I am using uImage file to boot MV Kernel from U-boot on Embedded Planet 
> EP8260 board. But it seems to be stuck after uncompressing:

I think now it's time to read the Q&A section of
http://www.denx.de/re/DPLG.html


Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@...
Living on Earth may be expensive, but it includes an annual free trip
around the Sun.

[U-Boot-Users] mpc8260 eth_loopback_test()

From: Maynard Cabiente <Maynard@ra...> - 2003-07-10 20:54

Hello,

I am currently using u-boot version 0.4.0 for the MPC8260ADS board.  
I am trying to use the additional code in cpu/mpc8260/ether_fcc.c to 
do the ethernet loopback test.   I already added the configuration for 
the MPC8260ADS to connect FCC's tx and rx clocks with the following 
code:

#elif defined(CONFIG_MPC8260ADS)
	/*
	 * Attention: this is board-specific (only using FCC2)
	 * - FCC2 Rx-CLK is CLK13
	 * - FCC2 Tx-CLK is CLK14
	 */

	/* 28.9 - (3): connect FCC's tx and rx clocks */
	immr->im_cpmux.cmx_uar = 0;
	immr->im_cpmux.cmx_fcr = CMXFCR_RF2CS_CLK13|CMXFCR_TF2CS_CLK14;
#else
#error "eth_loopback_test not supported on your board"
#endif

Well, I compiled it and run the test itself by creating a command for it 
(just like ping or mtest) for my own testing and not through "post".  

Here's the questions.  Does the eth_loopback_test() in
cpu/mpc8260/ether_fcc.c 
needs to have a loopback cable connected to the ethernet port [crossing pin
1 (TX+) 
and pin 3 (RX+) together and cross pin 2 (TX-) and pin 6 (RX-) together]?
Or is 
it supposed to be run connected directly to the network?

I tried both ways and couldn't tell which one is correct or if I need to
modify 
something else in the code to make it work properly.  Both have Receive
errors in it. 
(Are we supposed to get RX errors?)

Any help is appreciated.

Thanks.

Re: [U-Boot-Users] Serial Port Configuration on MPC8xx

From: Wolfgang Denk <wd@de...> - 2003-07-10 12:06

Dear Chris,

in message <D96E2AFA0DF3D211B139009027454948034CBEAF@...> you wrote:
> 
> I use smc1 for the output of Uboot.
> So I set #define CONFIG_8xx_CONS_SMC1.
> 
> In linux config I set SMC1 as my console  output.

OK so far.

> I would like to use SMC2 in linux also.
> So I added use SMC2 as UART in linux conf.

OK, too. This means you will have the serial  console  on  SMC1,  and
SMC2 is used as second serial port (/dev/ttyS1).

> For the SMC1 it works fine as Uboot makes the config of the BRG and IO when
> CONFIG_8xx_CONS_SMC1 is set.

This is because U-Boot uses SMC1.

> But for SMC2 no config is done by Uboot and I can't set CONFIG_8xx_CONS_SMC2
> & CONFIG_8xx_CONS_SMC1.

When U-Boot is configured for console on SMC1, it will not  use  SMC2
for anything, and thus it will not initialize it.

> Is there something clean to do under Uboot to make it configure SMC2 ?

Why should U-Boot initialize a port it does not use?

> Where should this init done ?

This should be done, and actually it _is_ done,  in  the  Linux  UART
driver. No help from U-Boot needed here.

Ummm... what exactly is the problem?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@...
A witty saying proves nothing, but saying  something  pointless  gets
people's attention.

RE: [U-Boot-Users] Serial Port Configuration on MPC8xx

From: <Christophe.LINDHEIMER@fr...> - 2003-07-10 12:16

Hi

> 
> > Is there something clean to do under Uboot to make it 
> configure SMC2 ?
> 
> Why should U-Boot initialize a port it does not use?
> 
> > Where should this init done ?
> 
> This should be done, and actually it _is_ done,  in  the  Linux  UART
> driver. No help from U-Boot needed here.
> 
> 
> Ummm... what exactly is the problem?
> 

Hum I think that I don't understand something.
In fact when I change the baudrate of SMC1 in UBoot, I see that the same
baudrate remains used in the linux console ( am I getting mad ?? :-)) )
So I thought that the IO Connfiguration & The BRG settings was done only by
UBoot.
BTW, depending on the hardware the IO pins ( and the IO Config ) are not the
same and nothing in the linux config allow to choose that... So it should
mean that the Linux Uart Driver should be patched depending on your
hardware.

Chris

Re: [U-Boot-Users] Serial Port Configuration on MPC8xx

From: Wolfgang Denk <wd@de...> - 2003-07-10 12:37

In message <D96E2AFA0DF3D211B139009027454948034CBEB1@...> you wrote:
>
> In fact when I change the baudrate of SMC1 in UBoot, I see that the same
> baudrate remains used in the linux console ( am I getting mad ?? :-)) )

This is just lucky coincidence if you happen to use the  same  serial
port  for cosole in U-Boot and Linux. Normally, you will have to pass
the required information to the Linux kernel as a boot argument, like
"console=ttyS2,115200"

> So I thought that the IO Connfiguration & The BRG settings was done only by
> UBoot.

No, the philosophy is that each part of the software, each driver, is
responsible to initialize the hardware it accesses. So the LInux UART
driver will initialize the serial port(s) itself.

> BTW, depending on the hardware the IO pins ( and the IO Config ) are not the
> same and nothing in the linux config allow to choose that... So it should

There are some de-facto standard configurations, which are  supported
by the Linux driver.

> mean that the Linux Uart Driver should be patched depending on your
> hardware.

Indeed. If your hardware guys decided to build some different  confi-
guration,  this  may require to add some #ifdef's to the Linux kernel
code. If you have a look at the UART drivers in our kernel treee  you
will see what I mean :-(

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@...
"There are some good people in it, but the orchestra as  a  whole  is
equivalent to a gang bent on destruction."      - John Cage, composer

RE: [U-Boot-Users] Serial Port Configuration on MPC8xx

From: <Christophe.LINDHEIMER@fr...> - 2003-07-10 12:46

> >
> > In fact when I change the baudrate of SMC1 in UBoot, I see 
> that the same
> > baudrate remains used in the linux console ( am I getting 
> mad ?? :-)) )
> 
> This is just lucky coincidence if you happen to use the  same  serial
> port  for cosole in U-Boot and Linux. Normally, you will have to pass
> the required information to the Linux kernel as a boot argument, like
> "console=ttyS2,115200"
> 

I am thinking that in the Bd_info there is a parameter indicating the
baudrate of the serial lline.
This value must be used by Linux to set up the console at the right baudrate
even without using the console
boot argument...

> > So I thought that the IO Connfiguration & The BRG settings 
> was done only by
> > UBoot.
> 
> No, the philosophy is that each part of the software, each driver, is
> responsible to initialize the hardware it accesses. So the LInux UART
> driver will initialize the serial port(s) itself.
> 
> > BTW, depending on the hardware the IO pins ( and the IO 
> Config ) are not the
> > same and nothing in the linux config allow to choose 
> that... So it should
> 
> There are some de-facto standard configurations, which are  supported
> by the Linux driver.
> 
> > mean that the Linux Uart Driver should be patched depending on your
> > hardware.
> 
> Indeed. If your hardware guys decided to build some different  confi-
> guration,  this  may require to add some #ifdef's to the Linux kernel
> code. If you have a look at the UART drivers in our kernel treee  you
> will see what I mean :-(

Ok .
I gonna see if I had to change something in the UART driver.

Thanks.

Chris

Re: [U-Boot-Users] Serial Port Configuration on MPC8xx

From: Wolfgang Denk <wd@de...> - 2003-07-10 12:58

In message <D96E2AFA0DF3D211B139009027454948034CBEB7@...> you wrote:
>
> I am thinking that in the Bd_info there is a parameter indicating the
> baudrate of the serial lline.
> This value must be used by Linux to set up the console at the right baudrate
> even without using the console
> boot argument...

This depends on many things, including architecture  and  (sometimes)
board.  For  example, there is no bd_info being passed on ARM or MIPS
systems.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@...
It is not enough to succeed. Others must fail.           - Gore Vidal

[U-Boot-Users] Serial Port Configuration on MPC8xx

From: <Christophe.LINDHEIMER@fr...> - 2003-07-10 11:58

Hi.

I use smc1 for the output of Uboot.
So I set #define CONFIG_8xx_CONS_SMC1.

In linux config I set SMC1 as my console  output.

I would like to use SMC2 in linux also.
So I added use SMC2 as UART in linux conf.

For the SMC1 it works fine as Uboot makes the config of the BRG and IO when
CONFIG_8xx_CONS_SMC1 is set.
But for SMC2 no config is done by Uboot and I can't set CONFIG_8xx_CONS_SMC2
& CONFIG_8xx_CONS_SMC1.

Is there something clean to do under Uboot to make it configure SMC2 ?
Where should this init done ?

Thanks

Regards

Chris

[U-Boot-Users] excluding CVS dirs from diffs

From: Robin Gilks <robin.gilks@ta...> - 2003-07-10 02:47

Greetings

Having just about finished the porting of u-boot to the Motorola 
mpc866ads board, I'm checking my work by diffing against the current 
CVS. Can someone tell me how I exclude all the CVS directories from the 
diff as I want to avoid cvs diff since sf is sooooo slooooowwww.

Many thanks

-- 
Robin Gilks
Senior Design Engineer              Phone: (+64)(3) 357 1569
Tait Electronics                          Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@...
New Zealand

Re: [U-Boot-Users] excluding CVS dirs from diffs

From: Robin Gilks <robin.gilks@ta...> - 2003-07-10 03:03

Robin Gilks wrote:
> Greetings
> 
> Having just about finished the porting of u-boot to the Motorola 
> mpc866ads board, I'm checking my work by diffing against the current 
> CVS. Can someone tell me how I exclude all the CVS directories from the 
> diff as I want to avoid cvs diff since sf is sooooo slooooowwww.
> 
> Many thanks
> 

Doh

RTFM = --exclude=CVS !!!


-- 
Robin Gilks
Senior Design Engineer              Phone: (+64)(3) 357 1569
Tait Electronics                          Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@...
New Zealand