public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kate Alhola <kate@iti.fi>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot and bdi2000
Date: Sat, 08 May 2004 14:03:29 +0300	[thread overview]
Message-ID: <409CBE81.3070500@iti.fi> (raw)
In-Reply-To: <20040507222023.3CA6DC109F@atlas.denx.de>

Wolfgang Denk wrote:

>In message <409C0053.1050306@iti.fi> you wrote:
>  
>
>>It is easiest to do initial testing to load code to internal sram . With 
>>    
>>
>
>This is something between a matter of taste and an urban legend.
>  
>
I don't think so. If you have brand new board to test, you can't be sure 
that everything is working
at all. Things inside of cpu are most propably ones that work. That 
means internal SRAM, UART
and with little external support ethernet.

>>In either case nothing appears in to the console.  Also, allways the 
>>address is same
>>and i got the step timeout.
>>    
>>
>
>Did you contact Abatron support? What did they say (except for: check
>for hardware problems - which I'd say, too).
>
>  
>
The reason why i don't think that it is not hw problem in abatron or 
board but rather
some incompatibility with bdi2000 initialization and u-boot. The abatron 
works
without problemt to load my own code to internal sram, i can start and 
run it etc.
I was expecting something same than Dan Malek said that there is something
with debug register write etc.

For some reason the both cases, trace and starting with go fails in same
place ( before or after bl )

fff00118 <boot_cold>:
fff00118:       7c a0 00 a6     mfmsr   r5
fff0011c:       3c 60 f0 00     lis     r3,-4096
fff00120:       60 63 00 00     ori     r3,r3,0
fff00124:       7c 77 4b a6     mtspr   311,r3
fff00128:       54 63 84 3e     rlwinm  r3,r3,16,16,31
fff0012c:       3c 80 80 00     lis     r4,-32768
fff00130:       90 64 00 00     stw     r3,0(r4)
fff00134:       48 00 30 45     bl      fff03178 <init_5xxx_core>

Also the board works, u-boot works, the board boots and runs linux etc. 
The only
thing that don't work is u-boot with bdi2000 connected.

>>with bdi2000.  There is something that i did wrong with bdi2000 
>>configuration
>>and i try figure out what.
>>    
>>
>
>Which differences are between your board and the LITE5200?
>  
>

There is lot ot abot nothing diferencies. In basic boot level it is wery 
compaible with LITE5200.
Only meaningfull diference is that boot flash is diferent. I just needed 
to change u-boot
to support intel-compatible flash algorithm and change flash size to get 
it working.

The most diferencies goes in expansions. My board has NAND flash for 
filesystem, MMC for
filesystem, TI2301 audio codec/touch screen/system ADC, two banks of 
SDRAM and
FPGA for LCD display controller and i-o expansion use. The board is 
http://www.iti.fi/iti5200.php

I was just working to make u-boot to boot kernel from nand flash or mmc.

Kate

      reply	other threads:[~2004-05-08 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 19:53 [U-Boot-Users] u-boot and bdi2000 Kate Alhola
2004-05-07 20:08 ` Wolfgang Denk
2004-05-07 21:32   ` Kate Alhola
2004-05-07 22:06     ` Dan Malek
2004-05-07 22:20     ` Wolfgang Denk
2004-05-08 11:03       ` Kate Alhola [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=409CBE81.3070500@iti.fi \
    --to=kate@iti.fi \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox