Skip to contentSkip to conversation

Loading u-boot to mpc5200 flash with bdi2000

U-Boot-Users Kate Alhola 2 participants 3 messages Feb 9, 2004 – Feb 10, 2004

lore
Share & tools
lore
#0 lore raw

I have been trying to load u-bood into flash of brand new board but found some problems.

I have bdi2000, lite5200 and my own board ( itipower5200 ).
I noticed that when i boot either board up. I can't read access flash with bdi2000 untill i have executed some amount of initial code that exists in lite5200 but of cource i can do this with my board because there is no code in flash yet.

It looks a like that cpu in lite5200 can read instructions from flash at beginning but bdi2000 displays only zeroes when i try to use md command. Both boards, lite5200 and itipower5200 displays zeroes and i have checked with osciloscope that least my board access flash and gives out 0xff

I have tried look the bdi2000 sample configuration files from denx but i have not yet find out what i have missed.

I also traced the motorola dBug from reset with lite5200 board to see what changed the behavior but least
i did not get sensible result that should affect the behavior.

The bdi2000 has all the time read access to the internal memory space of mpc5200 and i can accress config redisters or internal ram at beginning but just reading external flash gives zeroes even i have initializeg cs controll registers.

So, simply, the problem is that what i should tell to bdi2000 that i can access flash in empty board ?

Kate

-------------------------------------------------------------------------------------------------

; bdiGDB configuration file for 603ei (Zeppo) evaluation system ; ------------------------------------------------------------- ;
; DINK is used to setup the target.
;
;
; bdiGDB configuration file for the IceCube5200 evaluation board ; -------------------------------------------------------------- ;
[INIT]
; init core register

WREG    MSR         0x00001002  ;MSR  : ME,RI
WM32    0x80000000  0x0000f000  ;MBAR : internal registers at 0xf0000000
WSPR    311         0xf0000000  ;MBAR : save internal register offset
WSPR    279         0xf0000000  ;SPRG7: save internal memory offsetReg: 279
;
; init memory controller
WM32    0xf0000004  0x0000ff80  ;CS0 start = 0xff800000
WM32    0xf0000008  0x0000ffff  ;CS0 stop  = 0xffffffff
WM32    0xf0000054  0x00010001  ;CSE: enable CS0, disable CSBOOT
WM32    0xf0000300  0x00047800  ;BOOT ctrl

; init SDRAM CS for 16/16 Micron Type
WM32 0xf0000034 0x00000019 ;SDRAM CS0, 64 MByte physical, can use all 64MByte
WM32 0xf0000038 0x04000019 ;SDRAM CS1, 64 MByte physical, can use all 64MByte
WM32 0xf0000204 0x10000000 ;SDRAM Set tap delay to 0x10
TSZ4 0x00000000 0x07FFFFFF ;SDRAM CS0,1, 128 MByte
MMAP 0x00000000 0x07FFFFFF ;SDRAM CS0,1, 128 MByte

WM32 0x80000B00 0x80000000 ;GPIO Enable CS1

; init SDRAM controller for DDR 132MHz, CL=2.5
WM32 0x80000108 0x73722930 ;SDRAM Config 1 single
read2readwrite delay cl=2.5, swt2rp =3 for DDR, read CAS = 7 (cl=2,5), act2rd= 2,66 -> 3, pre2act=2,66 -> 3, refresh to no read delay=0xA, Write latency for DDR =3
WM32 0x8000010C 0x47770000 ;SDRAM Config 2
WM32 0x80000104 0xF15F0F00 ;SDRAM Control: Mode register write enable
mode reg=0, clk enable=1, DDR mode, auto refresh enabled,
hi_addr set, use A10 for precharge, drive rule=1, refresh interval=d15, dqs_oe=b1111
WM32 0x80000104 0xF15F0F02 ;SDRAM Control: Mode register write enable, precharge all
WM32 0x80000100 0x40090000 ;SDRAM Extended Mode
DLL enabled, drive strength reduced, QFC disabled
WM32 0x80000100 0x058D0000 ;SDRAM Mode, reset DLL
burst 8, sequential, CAS latency 2.5
WM32 0x80000104 0xF15F0F02 ;SDRAM Control: precharge all WM32 0x80000104 0xF15F0F04 ;SDRAM Control: refresh
WM32 0x80000100 0x018D0000 ;SDRAM Mode, normal DLL operation WM32 0x80000104 0x715F0F00 ;SDRAM Control, lock Mode register

; define maximal transfer size

TSZ4    0xFF800000  0xFFFFFFFF  ;ROM space
TSZ4    0xF0000000  0xF0003FFF  ;internal registers
;
; define the valid memory map
MMAP    0x00000000  0x03FFFFFF  ;Memory range for SDRAM
MMAP    0xF0000000  0xF0003FFF  ;Memory map for Internal Register
MMAP    0xF0008000  0xF000BFFF  ;Memory map for On-chip SRAM
MMAP    0xFF800000  0xFFFFFFFF  ;ROM space

[TARGET]

CPUTYPE     5200        ;the CPU type
JTAGCLOCK   0           ;use 16 MHz JTAG clock
BREAK       HARD    ;SOFT or HARD, HARD uses PPC hardware breakpoint

POWERUP 500 ;start delay after power-up detected in ms
BOOTADDR 0xFFF00100 ;Boot High
MMU XLAT
DCACHE NOFLUSH

[FLASH]
CHIPTYPE AM29F ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8
| I28BX16)

CHIPSIZE    0x800000    ;The size of one flash chip in bytes
BUSWIDTH    8           ;The width of the flash memory bus in bits (8 | 
16 | 32)
WORKSPACE   0xF0008000    ;workspace in internal SRAM
FILE        u-boot.bin
FORMAT      BIN 0xFF800000
ERASE       0xFF800000  ;erase sector 0
ERASE       0xFF810000  ;erase sector 1
ERASE       0xFF820000  ;erase sector 2
#1 lore raw
Quoted 6 lines · In message <[email protected]> you wrote:

I have bdi2000, lite5200 and my own board ( itipower5200 ).
I noticed that when i boot either board up. I can't read access flash with bdi2000 untill i have executed some amount of initial code that exists in lite5200 but of cource i can do this with my board because there is no code in flash yet.

Which BDI2000 configuration file are you using?

Quoted 2 lines

I have tried look the bdi2000 sample configuration files from denx but i have not yet find out what i have missed.

What's the exactl difference between our config file and yours?

Quoted 4 lines

So, simply, the problem is that what i should tell to bdi2000 that i can access flash in empty board ?

Quoted 8 lines

; bdiGDB configuration file for 603ei (Zeppo) evaluation system ; ------------------------------------------------------------- ;
; DINK is used to setup the target.
;
;
; bdiGDB configuration file for the IceCube5200 evaluation board ; --------------------------------------------------------------

Argh... Did you try using the config file from our FTP server?

Best regards,

Wolfgang Denk

Signature · 4 lines
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Philosophy:  A route of many roads leading from nowhere to nothing.
- Ambrose Bierce
#2 lore raw
Quoted 11 lines · Wolfgang Denk
Quoted 7 lines · In message <[email protected]> you wrote:

I have bdi2000, lite5200 and my own board ( itipower5200 ).
I noticed that when i boot either board up. I can't read access flash with bdi2000 untill i have executed some amount of initial code that exists in lite5200 but of cource i can do this with my board because there is no code in flash yet.

Quoted 4 lines

Which BDI2000 configuration file are you using?

I have been using various versions. Now i use mpc5200.cfg.flash from ftp.denx.de

Quoted 1 line

What's the exactl difference between our config file and yours?

only modifications host ip address and u-boot load path.

Quoted 3 lines

Argh... Did you try using the config file from our FTP server?

Yes i used. The following log is with bdi2000 with working lite5200 board and mpc5200.cfg.flash
config file. I get the flash visible only after using TI command several times in bdi2000
commad level.

Kate

BDI>reset halt
- 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 0x80822011
- Target SVR is 0x80110012
- 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
- Waiting for target stop passed
- TARGET: Target PVR is 0x80822011
- TARGET: resetting target passed
- TARGET: processing target startup ....
- Target MBAR is 0x80000000
- Target XLBA is 0x80000006
- TARGET: processing target startup passed
BDI>md 0xfff00100
fff00100 : 00000000 00000000 00000000 00000000 ................

BDI>md 0xf0000000
f0000000 : 0000f000 0000ff80 0000ffff 0000ffff ................ f0000010 : 0000ffff 0000ffff 0000ffff 0000ffff ................ f0000020 : 0000ffff 0000ffff 0000ffff 0000ffff ................ f0000030 : 0000ffff 00000000 00000000 0000ffff ................ f0000040 : 0000ffff 0000ffff 0000ffff 0000fff0 ................ f0000050 : 0000fff7 00010001 0000ffff 0000ffff ................ f0000060 : 0000ffff 0000ffff 00000000 00000000 ................

BDI>md 0xf0000300
f0000300 : 000f7800 00004000 00004000 00004000 ..x... at ...@... at . f0000310 : 00004000 00004000 00000000 00000000 .. at ...@......... f0000320 : 00004000 00004000 00000000 33333333 .. at [email protected] f0000330 : 00000000 00000000 00000000 00000000 ................ f0000340 : 00000000 00000000 00000000 00000000 ................ f0000350 : 00000000 00000000 00000000 00000000 ................ f0000360 : 00000000 00000000 00000000 00000000 ................ f0000370 : 00000000 00000000 00000000 00000000 ................

BDI>ti
- Target MBAR is 0xF0000000
- Target XLBA is 0x80000006
BDI> Target CPU : MPC8280/MGT5200 (Zeppo)
Target state : debug mode
Debug entry cause : trace
Current PC : 0xfff00104

..... lines removed

BDI>ti
- Target MBAR is 0xF0000000
- Target XLBA is 0x80000006
BDI> Target CPU : MPC8280/MGT5200 (Zeppo)

    Target state      : debug mode
    Debug entry cause : trace
    Current PC        : 0xfff001d8
    Current CR        : 0x80000000
    Current MSR       : 0x00001002
    Current LR        : 0xfff00118

BDI>md 0xfff00100
fff00100 : 00000000 00000000 00000000 00000000 ................ fff00110 : 00000000 00000000 00000000 00000000 ................

... lines removed

BDI>ti
- Target MBAR is 0xF0000000
- Target XLBA is 0x80000006
BDI> Target CPU : MPC8280/MGT5200 (Zeppo)

    Target state      : debug mode
    Debug entry cause : trace
    Current PC        : 0xfff02000
    Current CR        : 0x80000000
    Current MSR       : 0x00001002
    Current LR        : 0xfff001f0

BDI>md 0xfff00100
fff00100 : 00000000 00000000 00000000 00000000 ................

- Target MBAR is 0xF0000000
- Target XLBA is 0x80000006
BDI> Target CPU : MPC8280/MGT5200 (Zeppo)

    Target state      : debug mode
    Debug entry cause : COP halt
    Current PC        : 0xfff0d61c
    Current CR        : 0x40000000
    Current MSR       : 0x00001002
    Current LR        : 0xfff0d544

# Step timeout detected
BDI>md 0xfff00100
fff00100 : 7ff043a6 7fe802a6 7ff143a6 7c774aa6 ..C.......C.|wJ. fff00110 : 7c631b79 408200bd 3c608000 60630000 |c.y at ...<..c..