* [U-Boot-Users] External RTC in MPC860P (i2c - rtc DS1307)
From: Wolfgang Denk @ 2006-05-10 13:32 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20060510122158.47635.qmail@web36907.mail.mud.yahoo.com>
In message <20060510122158.47635.qmail@web36907.mail.mud.yahoo.com> you wrote:
>
> We are interfacing external RTC DS1307 in MPC860P(40MHz core frequency).
> I've configured the following files in U-boot-1.1.3.
Why are you using old code?
> 1. In i2c.c
You should never have to modify this file.
> #define CFG_I2C_SLAVE 0xFE
...
> 2. In include/configs/BOARD.h
...
> #define CFG_I2C_SLAVE 0x7F
SO what is your slave address? 0xFE or 0x7F ?
> #define CONFIG_HARD_I2C 1
Makes not much sense to me. I prefer to use soft-I2C.
> 3. In <board/board.h>
...
> #define CONFIG_HARD_I2C 1
> #define CFG_I2C_SPEED 50000
> #define CFG_I2C_SLAVE 0xFE
And yet another set of definitions?
Do NOT do this.
> Is the above things correct in order to get the date and time
> up and running in an MPC860P based custom board.
No, this is NOT correct. You must not define the same things in
several place, and differently. Use a single definition in your board
config file, and make sure it is correct.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Ill-chosen abstraction is particularly evident in the design of the
ADA runtime system. The interface to the ADA runtime system is so
opaque that it is impossible to model or predict its performance,
making it effectively useless for real-time systems.
- Marc D. Donner and David H. Jameson.
^ permalink raw reply
* [U-Boot-Users] External RTC in MPC860P (i2c - rtc DS1307)
From: Anand Mallya @ 2006-05-10 12:21 UTC (permalink / raw)
To: u-boot
Dear All,
We are interfacing external RTC DS1307 in MPC860P(40MHz core frequency).
I've configured the following files in U-boot-1.1.3.
1. In i2c.c
#define CFG_I2C_SPEED 50000
#define CFG_I2C_SLAVE 0xFE
2. In include/configs/BOARD.h
#define CFG_I2C_SPEED 50000
#define CFG_I2C_SLAVE 0x7F
#define CONFIG_HARD_I2C 1
#define CONFIG_RTC_DS1307 1
#define CFG_CMD_DATE 1
In this file I commented CONFIG_RTC_MPC8xx
3. In <board/board.h>
#define CONFIG_HARD_I2C 1
#define CFG_I2C_SPEED 50000
#define CFG_I2C_SLAVE 0xFE
Is the above things correct in order to get the date and time
up and running in an MPC860P based custom board.
Anything else I need to configure !? or any code changes
required here?
But I'm not able to get the date and time in my board.
I've captured the log of i2c with debug enabled.
Pleas edo have a look at it & Kindly let me know where
I've gone wrong .
Thanks in advance!!!!.
The U-boot log :
~~~~~~~~~~~~
U-Boot 1.1.3 (May 3 2006 - 15:06:18)
CPU: XPC86xxxZPnnD4 at 40 MHz: 16 kB I-Cache 8 kB D-Cache FEC present
Board: Integrated Communications Manager - Beta with MPC860P
UPMB Enabled for IDE
I2C: [I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
ready
DRAM: (16 MB SDRAM) 16 MB
Top of RAM usable for U-Boot at: 01000000
Reserving 378k for U-Boot at: 00fa1000
Reserving 400k for malloc() at: 00f3d000
Reserving 60 Bytes for Board Info at: 00f3cfc4
Reserving 48 Bytes for Global Data at: 00f3cf94
Stack Pointer at: 00f3cf78
New Stack Pointer is: 00f3cf78
Now running in RAM - U-Boot at: 00fa1000
FLASH: flash_protect ON: from 0xFF800000 to 0xFF829FFF
protect on 0
protect on 1
protect on 2
protect on 3
flash_protect ON: from 0xFF840000 to 0xFF843FFF
protect on 4
AMD-LV160-B : 8 MB
*** Warning - bad CRC, using default environment
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
In: serial
Out: serial
Err: serial
U-Boot relocated to 00fa1000
Net: FEC ETHERNET
IDE: Bus 0: not available Status = 0x00
LECD: 4 Line D## main_loop entered: bootdelay=1
### main_loop: bootcmd="bootm 0xff900000"
Hit any key to stop autoboot: 1 \b\b\b 0
## Booting image at ff900000 ...
Bad Magic Number
[ICM] $
[ICM] $
[ICM] $date
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x00
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
[I2C] Receiving...(rxbd=0xff002820)
2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0htz
[I2C] i2mod=000002 i2brgR=00000016
[I2CC] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x01
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x02
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x03
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
[I2C] Receiving...(rxbd=0xff002820)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x04
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
[I2C] Receiving...(rxbd=0xff002820)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x05
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
[I2C] Best is:
[I2C] CPU=40000000hz RATE=50000 F=0 I2MOD=00000001 I2BRG=00000016 DIFF=0hz
[I2C] i2mod=00000002 i2brg=00000016
[I2C] rbase = 0820
[I2C] tbase = 0840
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] i2c_newio
[I2C] rxbd = ff002820
[I2C] txbd = ff002840
[I2C] tx_buf = ff002860
[I2C] i2c_send add=104 sec=00 flag=02 size=1
[I2C] txbd = ff002840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x06
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0xf3
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
[I2C] Receiving...(rxbd=0xff002820)
i2c_read: i2c_doio failed (-1)
Get RTC year: 00 mon: 00 mday: 00 wday: 00 hr: 00 min: 00 sec: 00
Get DATE: 2000-00-00 (wday=7) TIME: 0:00:00
Date: 2000-00-00 (unknown day) Time: 0:00:00
[ICM] $i2cinfo
I2MOD = 03 I2ADD = fe
I2BRG = 16 I2COM = 01
I2CER = 10 I2CMR = 00
RBASE = 00000820 TBASE = 00000840
RFCR = 10 TFCR = 10
MRBLR = 0080
RSTATE= 00000000 RDP = 61cf2623
RBPTR = 0820 RBC = c6ef
RXTMP = bd65484e
TSTATE= 10000000 TDP = ff002864
TBPTR = 0840 TBC = 0001
TXTMP = d10057e2
[ICM] $
I2MOD = 03 I2ADD = fe
I2BRG = 16 I2COM = 01
I2CER = 10 I2CMR = 00
RBASE = 00000820 TBASE = 00000840
RFCR = 10 TFCR = 10
MRBLR = 0080
RSTATE= 00000000 RDP = 61cf2623
RBPTR = 0820 RBC = c6ef
RXTMP = bd65484e
TSTATE= 10000000 TDP = ff002864
TBPTR = 0840 TBC = 0001
TXTMP = d10057e2
02840
[I2C] Formatting addresses...
[I2C] copy data...
[I2C] txbd: length=0x0002 status=0x8400 addr[0]=0xd0 addr[1]=0x05
[I2C] i2c_receive 104 00 04
[I2C] rxbd = ff002820
[I2C] txbd = ff002848
[I2C] txbd: length=0x0002 status=0xac00 addr[0]=0xd1 addr[1]=0x00
[I2C] rxbd: length=0x0001 status=0xa000 addr[0]=0x00 addr[1]=0x00
[I2C] i2c_doio
[I2C] Enabling I2C...
[I2C] Transmitting...(txbd=0xff002848)
[I2C] Receiving...(rxbd=0xff002820)
[I2C] Receiving...(rxbd=0xff002820)
i2c_read: i2c_doio failed (-1)
[I2C] Setting rate...
[I2C] trying hz=40000000, speed=50000, filter=0, modval=0
moddiv=32, brgdiv=25
accepted brgval=10, totspeed=48076
[I2C] trying hz=40000000, speed=50000, filter=0, modval=1
moddiv=16, brgdiv=50
accepted brgval=22, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=2
moddiv=8, brgdiv=100
accepted brgval=47, totspeed=50000
[I2C] trying hz=40000000, speed=50000, filter=0, modval=3
moddiv=4, brgdiv=200
accepted brgval=97, totspeed=50000
Regards,
ganesh
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060510/63da39be/attachment.htm
^ permalink raw reply
* [U-Boot-Users] Re: the AMyBtEN
From: Boipelo Zygmont @ 2006-05-10 10:01 UTC (permalink / raw)
To: u-boot
web site <http://trankolizasep.com>
need mine. I am not over fond of dwarves; but if it is true you are
Thorin (son of Thrain, son of Thror, I believe), and that your companion
is respectable, and that you are enemies of goblins and are not up to
any mischief in my lands-what are you up to, by the way? They are on
their way to visit the land of their fathers, away east beyond
Mirkwood, put in Gandalf, and it is entirely an accident that we are
in your lands at all. We were crossing by the High Pass that should have
brought us to the road that lies to the south of your country, when we
were attacked by the evil goblins-as I was about to tell you. Go on
telling, then! said Beorn, who was never very polite. There was a
terrible storm; the stone-giants were out hurling rocks, and at the head
of the pass we took refuge in a cave, the hob bit and I and several of
our companions...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060510/783e8555/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2414 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060510/783e8555/attachment.gif
^ permalink raw reply
* [U-Boot-Users] RAM mapping repeats
From: Joao, Nuno @ 2006-05-10 9:55 UTC (permalink / raw)
To: u-boot
> On Behalf Of Antonio Di Bacco
> Sent: ter?a-feira, 9 de Maio de 2006 21:49
> Subject: [U-Boot-Users] RAM mapping repeats
> I have 16MB of RAM (0x01000000) then I specified BR2=0x0000xxxx and
> OR2=0xFE000000 . Obviously if I write at 1000000 is the same as I write at
> 0x00000000. That is, the memory repeats in the space address. This doesn't
> seem good to me because I will not receive any bus error if go to an address
> higher than my RAM size. Am I wrong?
No, you are not wrong.
You should set the CS address range only for the address range
supported by your device. If you setup a bigger address range in
the CS, the wrap-around happens, it is "normal" because your device
is "looking" only at the less significant 24 address lines. An
address like 1000000 uses more than 24 address bits, so the extra
bits will be ignored because they are not connnected to your device
(this is simplistic view, assuming the device has an 8 bit port size).
In your case you should set AM to 1111.1111.0000.0, check your
device's datasheet.
^ permalink raw reply
* [DNX#2006040142000795] [U-Boot-Users] [PATCH] fix undefined error on omap5912osk
From: U-Boot patch tracking system @ 2006-05-10 9:50 UTC (permalink / raw)
To: u-boot
Dear Hiroki Kaminaga,
Applied with my previous OMAP fixes. Thanks.
Your Ticket-Team
--
Stefan Roese --
DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support at denx.de
Powered by OTRS (http://otrs.org/)
^ permalink raw reply
* [DNX#2006033142000491] [U-Boot-Users] [PATCH] OMAP 5912/OSK: update EMIFS CS1 timin [...]
From: U-Boot patch tracking system @ 2006-05-10 9:49 UTC (permalink / raw)
To: u-boot
Dear Kevin Hilman,
Applied, thanks.
Please provide a proper CHANGELOG entry next time.
Your Ticket-Team
--
Stefan Roese --
DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support at denx.de
Powered by OTRS (http://otrs.org/)
^ permalink raw reply
* [DNX#2006040142000508] [U-Boot-Users] build error for omap5912osk on u-boot 1.1.4
From: U-Boot patch tracking system @ 2006-05-10 9:37 UTC (permalink / raw)
To: u-boot
Dear Hiroki Kaminaga,
Applied with some enhancements. Thanks.
Your Ticket-Team
--
Stefan Roese --
DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support at denx.de
Powered by OTRS (http://otrs.org/)
^ permalink raw reply
* [U-Boot-Users] serial interface in U-boot
From: Ganesh Ramachandran @ 2006-05-10 9:36 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20060510073322.28015.qmail@web30602.mail.mud.yahoo.com>
>> In my board_config.h file i have define : CONFIG_BAUDRATE 9600
>> but when i execute the 'bdinfo' command from the prompt i am
getting baud as 0.
It may be the problem with your u-boot configuration. I also the got
the same problem once. We can say number of reasons. Are you getting
any warnings like 'bad CRC using defaults environment'? Are you sure
that your u-boot configuration is properly configured for flash
address and length/size settings?
Thanks & Regards,
P. Ganesh Ramachandran.
^ permalink raw reply
* [DNX#2006040142000615] [U-Boot-Users] [PATCH] fix address of REG_MPU_LOAD_TIMER for [...]
From: U-Boot patch tracking system @ 2006-05-10 9:34 UTC (permalink / raw)
To: u-boot
Dear Hiroki Kaminaga,
Applied, thanks.
Please provide a propper CHANGELOG entry next time.
Your Ticket-Team
--
Stefan Roese --
DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support at denx.de
Powered by OTRS (http://otrs.org/)
^ permalink raw reply
* [U-Boot-Users] serial interface in U-boot
From: Kaushik karandikar @ 2006-05-10 7:33 UTC (permalink / raw)
To: u-boot
Hi all,
I am successfully able to configure the u-boot for phytec board (for ARM7TDMI). I am getting the u-boot prompt.
But the problem is i am not able to trnasfer the image at specified address in RAM( which is say 0x81000000). Even u-boot is finding this address , thts not the issue.
I am transferring a sample application code (blink LED) at this location. As i am getting the prompt and other prints through minicom utility , serial interface is working.
Is there any configurable option need to set say for ymodem, kermit,xmodem,zmodem in u-boot ? so that i can transfer my application image through minicom.
In my board_config.h file i have define : CONFIG_BAUDRATE 9600
but when i execute the 'bdinfo' command from the prompt i am getting baud as 0.
Can anyone please let me know about this.
Thanks and Regards,
Kaushik
---------------------------------
Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2?/min with Yahoo! Messenger with Voice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060510/52e4d956/attachment.htm
^ permalink raw reply
* [U-Boot-Users] Section overlap
From: Wolfgang Denk @ 2006-05-10 7:20 UTC (permalink / raw)
To: u-boot
In-Reply-To: <BAY105-F16366015E401A8668F788D8EAE0@phx.gbl>
In message <BAY105-F16366015E401A8668F788D8EAE0@phx.gbl> you wrote:
>
> I'm using U-boot-1.0.0 on an ebony board (ppc),
...
> 1) how do i get around this ?
Use current code. U-Boot-1.0.0 is just too old.
> 2) How does these commands scheme work, are the always linked in ?
Yes, the configured commands are always linked in.
> 3) I thought you could cherry pick the ones you need. is this correct ?
Yes, you can, when configuring your board.
> 4) Also is this a right approach to handle the above problem.
No.
> 5) Would using -ffunction-sections -fdata-sections for gcc and --gc-sections
> for the linker possible.
It makes no sense trying to fix problems that have been fixed long
ago in less prehistoric versions ov the code.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"355/113 -- Not the famous irrational number PI, but an incredible
simulation!"
^ permalink raw reply
* [U-Boot-Users] patch for dmatek dma-arm9 fs2410 eval board
From: Kevin Lo @ 2006-05-10 5:46 UTC (permalink / raw)
To: u-boot
Hi,
Attached is a patch file for DMATEK DMA-ARM9 FS2410 board.
Regards,
Kevin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-fs2410
Type: text/x-patch
Size: 36252 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060510/ac869e7e/attachment.bin
^ permalink raw reply
* [U-Boot-Users] Section overlap
From: k bisla @ 2006-05-10 1:05 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20060509221330.8DE95353DB1@atlas.denx.de>
Hi,
I'm using U-boot-1.0.0 on an ebony board (ppc),
and running into section overlap error at the time of linking.
here's what the output looks like ...
section .u_boot_cmd [ffffef50 -> fffff567] overlaps section .bootpg
[fffff000 -> fffff29f]
1) how do i get around this ?
Taking out cmd_bmp, cmd_ide, cmd_scsi etc etc which i'm not using from the
common/Makefile helped,
Looks like i cant take out most of the commands, they are referred from
other portion of the code.
2) How does these commands scheme work, are the always linked in ?
3) I thought you could cherry pick the ones you need. is this correct ?
4) Also is this a right approach to handle the above problem.
5) Would using -ffunction-sections -fdata-sections for gcc and --gc-sections
for the linker possible.
Any suggestion how i could remove unwanted stuff.
Your thoughts and suggestion would be appreciated.
-Kunal
^ permalink raw reply
* [U-Boot-Users] RAM mapping repeats
From: Wolfgang Denk @ 2006-05-09 22:13 UTC (permalink / raw)
To: u-boot
In-Reply-To: <200605092249.11586.antonio.dibacco@aruba.it>
In message <200605092249.11586.antonio.dibacco@aruba.it> you wrote:
>
> I have 16MB of RAM (0x01000000) then I specified BR2=0x0000xxxx and
> OR2=0xFE000000 . Obviously if I write at 1000000 is the same as I write at
> 0x00000000. That is, the memory repeats in the space address. This doesn't
> seem good to me because I will not receive any bus error if go to an address
> higher than my RAM size. Am I wrong?
Why do you set OR2 to this value then, after you know it is wrong?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Live long and prosper.
-- Spock, "Amok Time", stardate 3372.7
^ permalink raw reply
* [U-Boot-Users] Usually dram test executed not on whole sdram
From: Wolfgang Denk @ 2006-05-09 22:07 UTC (permalink / raw)
To: u-boot
In-Reply-To: <200605092241.38323.antonio.dibacco@aruba.it>
In message <200605092241.38323.antonio.dibacco@aruba.it> you wrote:
> Anyone knows why in the u-boot normally the dram test is not executed on the
> whole DRAM? For example a lot boards that have 16MB specify start_address =
> 1MB and end_addr = 15MB. If the u-boot is executing in flash the DRAM can be
> written completely I think!
The "mtest" can only be run after relocation to RAM, so you have to
leave out the memory needed ofr exception vectors, U-Boot code,
malloc arena, stack, etc.
For the POST tests no such restriction exists.
But you are on the wrong track. A memory test will NOT detect your
problem, as it is exercising pleain read / write accesses only, while
your problem is most probably with burst mode accesses. Please read
the FAQ!
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Success in marriage is not so much finding the right person as it is
being the right person.
^ permalink raw reply
* [U-Boot-Users] RAM mapping repeats
From: Antonio Di Bacco @ 2006-05-09 20:49 UTC (permalink / raw)
To: u-boot
Hi all,
I have 16MB of RAM (0x01000000) then I specified BR2=0x0000xxxx and
OR2=0xFE000000 . Obviously if I write at 1000000 is the same as I write at
0x00000000. That is, the memory repeats in the space address. This doesn't
seem good to me because I will not receive any bus error if go to an address
higher than my RAM size. Am I wrong?
Bye,
Antonio.
^ permalink raw reply
* [U-Boot-Users] Usually dram test executed not on whole sdram
From: Antonio Di Bacco @ 2006-05-09 20:41 UTC (permalink / raw)
To: u-boot
Anyone knows why in the u-boot normally the dram test is not executed on the
whole DRAM? For example a lot boards that have 16MB specify start_address =
1MB and end_addr = 15MB. If the u-boot is executing in flash the DRAM can be
written completely I think!
Bye,
Antonio.
^ permalink raw reply
* [U-Boot-Users] Re: the AMBmtEN
From: Ghislaine Ladner @ 2006-05-09 20:04 UTC (permalink / raw)
To: u-boot
web site <http://zamerigalop.com>
Arrow! said the bowman. Black arrow! I have saved you to the last.
You have never failed me and always I have recovered you. I had you from
my father and he from of old. If ever you came from the forges of the
true king under the Mountain, go now and speed well!
The dragon swooped once more lower than ever, and as he turned and
dived down his belly glittered white with sparkling fires of gems in the
moon-but not in one place. The great bow twanged. The black arrow sped
straight from the string, straight for the hollow by the left breast
where the foreleg was flung wide. In it smote and vanished, barb, shaft
and feather, so fierce was its flight. With a shriek that deafened men,
felled trees and split stone, Smaug shot spouting into the air, turned
over and crashed down from on high in ruin.
Full on the town he fell. His last throes splintered it to sparks and
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060509/9a33b154/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2500 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060509/9a33b154/attachment.gif
^ permalink raw reply
* [U-Boot-Users] lost between in_ram and "bl board_init_r"
From: Wolfgang Denk @ 2006-05-09 19:25 UTC (permalink / raw)
To: u-boot
In-Reply-To: <200605091940.29621.antonio.dibacco@aruba.it>
In message <200605091940.29621.antonio.dibacco@aruba.it> you wrote:
>
> I'm trying to run u-boot 1.1.4 on a MPC880 board with 16MB ram and 8MB flash.
> After a long porting phase now the processor has arrived to relocate_code and
> once entered there it loops forever between in_ram (start.S) and "bl
> board_init_r" without calling board_init_r. The u-boot seems to be corrected
So there is a 99.999 % likelyhood that your SDRAM init sequence is
incorrect and/or incomplete.
> relocated at 0x00FCA000, the stack seems to be correctly setup but it seems
> that the printf in board_init_r is never called. I've also enabled a
> CFG_DRAM_TEST and it is successfull, then I hope no DRAM problems.
You do. You can be sure of it.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You are an excellent tactician, Captain. You let your second in com-
mand attack while you sit and watch for weakness.
-- Khan Noonian Singh, "Space Seed", stardate 3141.9
^ permalink raw reply
* [U-Boot-Users] lost between in_ram and "bl board_init_r"
From: Antonio Di Bacco @ 2006-05-09 17:40 UTC (permalink / raw)
To: u-boot
Hi all,
I'm trying to run u-boot 1.1.4 on a MPC880 board with 16MB ram and 8MB flash.
After a long porting phase now the processor has arrived to relocate_code and
once entered there it loops forever between in_ram (start.S) and "bl
board_init_r" without calling board_init_r. The u-boot seems to be corrected
relocated at 0x00FCA000, the stack seems to be correctly setup but it seems
that the printf in board_init_r is never called. I've also enabled a
CFG_DRAM_TEST and it is successfull, then I hope no DRAM problems.
Thank you for your help,
Antonio.
^ permalink raw reply
* [U-Boot-Users] AT91RM9200 Dataflash op error with U-Boot1.1.4
From: Andrey P. Vasilyev @ 2006-05-09 16:22 UTC (permalink / raw)
To: u-boot
In-Reply-To: <006f01c67377$34cf2150$b7899d0a@first>
On Tue, May 09, 2006 at 10:45:20PM +0800, KylongMu wrote:
> > On Tue, May 09, 2006 at 07:11:52PM +0800, KylongMu wrote:
> > > Dear Groups:
> > > My board contains: AT91RM9200 DataFlash:AT45DB642 (without nand
> > > flash)
> > ...
> > > U-Boot> erase c0020000 c0027fff
> > > Error: start address not on sector boundary
> > > U-Boot>
> >
> > Perhaps, this patch will help you:
...
> > If it will not solve the problem, try this:
...
>
> Dear Andrey,
> Thanks for your answer. I patched these two files one by one, or
> both of them, but all failed, and the error is still.
> Thanks a lot!
Oops... My mistake. I've replied without carefully reading your
question...
Right answer (I hope): you dont need to erase dataflash. AFAIK,
dataflash erasing is performed by driver when you write into dataflash.
So, for example, to download binary into c0042000 dataflash "virtual"
address, you can use simple "cp" command, without issuing "erase"
command first, like this:
loadb 21000000
<sending image 0x12345 bytes long by kermit>
cp.b 21000000 c0042000 12345
--
With best regards,
Andrey Vasilyev
^ permalink raw reply
* [U-Boot-Users] Re: License issues with Xilinx provided files
From: Keith J Outwater @ 2006-05-09 16:21 UTC (permalink / raw)
To: u-boot
In-Reply-To: <445FEE82.8070208@xilinx.com>
Peter Ryser <peter.ryser@xilinx.com> wrote on 05/08/2006 06:21:06 PM:
> Keith,
>
> thanks for the follow-up. I would have missed Wolfgang's email.
> I think we should take the discussion back to the mailing list.
>
> The drivers should be in a common location and the BSP generation
mechanism should be used to overwrite these files for a given hardware
design. That will always guarantee that the drivers matching the IP will
be used.
Won't that mean that for any given design that uses a Virtex2/ppc405, the
public U-Boot source tree will never be guaranteed correct?
It sounds like the user would be required to maintain a locally modified
U-Boot source tree for each design.
That sounds like a clumsy solution.
Could we just set up a common driver library and provide a mechanism to
allow a particular board to configure the library for the particular IP
versions used in the hardware design? Then the IP versions are specified
in the board configuration file and you're done.
Note that no matter what approach is used, there is still the licensing
issue. I cannot, for example, submit certain Xilinx driver files for
inclusion into U-Boot that I need to support my board.
Are you planning to add a complete set of drivers to U-Boot?
>
> Cheers,
> - Peter
>
>
^ permalink raw reply
* [U-Boot-Users] PXA27x USB support?
From: Wolfgang Denk @ 2006-05-09 15:52 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20060509151511.GL10349@enneenne.com>
Dear Rodolfo,
in message <20060509151511.GL10349@enneenne.com> you wrote:
>
> However I think it could be a good idea to put OHCI support into
> ?common? directory (the new file can be called ?usb-ohci.c?) and then
> exporting into it some hooks for several platforms whose wish use it.
You are right. Please feel free to submit a patch.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If it has syntax, it isn't user friendly.
^ permalink raw reply
* [U-Boot-Users] CompactFlash TrueIDE with 1 chip select
From: llandre @ 2006-05-09 15:29 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1147187629.16780.48.camel@saruman.qstreams.net>
This AN provides some useful information
http://www.toshiba.com/taec/components/ApplNote/TSB_CF-IBM_PPC405GP_030523.pdf
Regards,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave-tech.it
email: r&d2 at dave-tech.it
> Hello,
>
> I'm planning on using Compact Flash on an MPC8349 in True IDE mode, but
> only have one chip select line available. The local bus on this chip is
> for all intents and purposes the same as all of the 8xx/82xx chips that
> came before it. The plan is do some address decoding magic in a CPLD to
> provide two indirect chip selects.
>
> Browsing through the U-boot code and some other boards using True IDE, I
> think this should work without much drama. Does anyone have comments or
> suggestions?
>
> thanks,
> Ben
^ permalink raw reply
* [U-Boot-Users] PXA27x USB support?
From: Rodolfo Giometti @ 2006-05-09 15:15 UTC (permalink / raw)
To: u-boot
In-Reply-To: <5AA61C4F-6B71-4793-8C5A-17749ABD0423@cse.unsw.edu.au>
On Mon, May 08, 2006 at 09:36:56PM +1000, David Snowdon wrote:
>
> Thanks Markus and Rodolfo for you thoughts! I'll give it a go and
> submit a patch.
You are well come.
However I think it could be a good idea to put OHCI support into
?common? directory (the new file can be called ?usb-ohci.c?) and then
exporting into it some hooks for several platforms whose wish use it.
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at gnudd.com
Embedded Systems giometti at linux.it
UNIX programming phone: +39 349 2432127
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060509/8383fd3c/attachment.pgp
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox