boot from ram on rd-6281-a
Hello u-boot list
i have an Eval-Board RD-6281 from Marvell for which i found u-boot support on latest version "U-Boot 2009.11.1"
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the TEXT_BASE = 0x00400000
to not collide with the installed one.
But when i load the "u-boot.bin" to the TEXT_BASE via TFTP and enter "go 0x00400000" the system hangs.
Can somebody please tell me where I am wrong ???
--------------------------------------------------------------
J?rgen Schindele
Software-Entwicklung
NENTEC Netzwerktechnologie GmbH
Greschbachstr. 12
76229 Karlsruhe
Deutschland
Telefon: +49 721 94249-51 Telefax: +49 721 94249-10 E-Mail: schindele at nentec.de WEB: www.nentec.de
Gesch?ftsf?hrung: Klaus Becker, Roland Knapp
Sitz der Gesellschaft: Karlsruhe
Handelsregister: Amtsgericht Mannheim HRB 107658
Diese E-Mail enth?lt vertrauliche oder rechtlich gesch?tzte Informationen. Wenn Sie nicht der vorgesehene Empf?nger sind, informieren Sie bitte sofort den Absender und l?schen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet.
The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited.
--------------------------------------------------------------
Dear Juergen Schindele,
Quoted 5 lines · In message <[email protected]> you wrote:
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the
TEXT_BASE=0x00400000
to not collide with the installed one.
This is not enough. You must also make sure not to try to perform all the low level initializations again that have already been done.
Quoted 1 line
Can somebody please tell me where I am wrong ???
Did you read the FAQ?
Quoted 9 lines
Diese E-Mail enth?lt vertrauliche oder rechtlich gesch?tzte Informationen. Wenn Sie nicht der vorgesehene Empf?nger sind, informieren Sie bitte sofort den Absender und l?schen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet.
Quoted 1 line
The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited.
Please omit this crap when posting to public mailing lists (and keep in mind that even in e-mail such statements are bogus at best, see
http://www.heise.de/ix/meldung/Disclaimer-Unnoetiger-Ballast-fuer-E-Mails-892297.html)
Best regards,
Wolfgang Denk
Signature · 5 lines
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 at denx.de Those who do not understand Unix are condemned to reinvent it, poorly. - Henry Spencer, University of Toronto Unix hack
Am Freitag, 26. Februar 2010 schrieb Wolfgang Denk:
Quoted 11 lines
Dear Juergen Schindele,
Quoted 5 lines · In message <[email protected]> you wrote:
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the
TEXT_BASE=0x00400000
to not collide with the installed one.This is not enough. You must also make sure not to try to perform all the low level initializations again that have already been done.
I know that, but SKIP_LOW_LEVEL_INIT is defined because register init is done with kirkwood boot header for booting from SPI/NAND-Flash. I dont see other blocking points. :-( i tried to skip relocate too but it did not help !
Quoted 4 lines
Quoted 2 lines
Can somebody please tell me where I am wrong ???
Did you read the FAQ?
Yes i read the README and searched in Internet or what FAQ do you mean ???
Quoted 4 lines
Please omit this crap when posting to public mailing lists (and keep in mind that even in e-mail such statements are bogus at best, see
http://www.heise.de/ix/meldung/Disclaimer-Unnoetiger-Ballast-fuer-E-Mails-892297.html)
sorry for the crap i forgot to suppress before sending
Signature · 17 lines
-------------------------------------------------------------- J?rgen Schindele Software-Entwicklung NENTEC Netzwerktechnologie GmbH Greschbachstr. 12 76229 Karlsruhe Deutschland Telefon: +49 721 94249-51 Telefax: +49 721 94249-10 E-Mail: schindele at nentec.de WEB: www.nentec.de Gesch?ftsf?hrung: Klaus Becker, Roland Knapp Sitz der Gesellschaft: Karlsruhe Handelsregister: Amtsgericht Mannheim HRB 107658 -------------------------------------------------------------
Dear Juergen,
Quoted 10 lines · Juergen Schindele
Am Freitag, 26. Februar 2010 schrieb Wolfgang Denk:
Quoted 9 lines
Dear Juergen Schindele,
Quoted 5 lines · In message <[email protected]> you wrote:
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the
TEXT_BASE=0x00400000
to not collide with the installed one.
Quoted 6 lines
Quoted 2 lines
This is not enough. You must also make sure not to try to perform all the low level initializations again that have already been done.
I know that, but
SKIP_LOW_LEVEL_INITis defined because register init is done with kirkwood boot header for booting from SPI/NAND-Flash. I dont see other blocking points. :-( i tried to skip relocate too but it did not help !
I have absolutely no experience concerning kirkwood, but did the same for coldfire for running U-Boot as the flasher application started from the debugger...
IIRC there were three places I had to change for coldfire:
- low-level init: do not put the vector table at the beginning of code (probably better: initialize it in the proper place?)
- leave the vector base register as it is (should be set up properly by first loader/debugger, and U-Boot does not use interrupts)
- the cpu speed detection/setting code was basically switched back to detection for CONFIG_MONITOR_IS_IN_RAM because it involved putting the RAM to self-refresh, which is obviously not possible when running from it
(For Coldfire, a special case was that I had to disable monitor protection manually because the standard condition fails due to the memory layout.)
Here's my patch for Coldfire MCF532x/7x:
http://www.mail-archive.com/u-boot at lists.denx.de/msg28779.html
BTW, disabling relocation may lead to bad results for malloc and the initial stack setup. I am not sure but seem to remember I had some problems when I tried it - and, it should not be a problem to do it as usual anyways if everything else is working correctly.
Hope this can give some useful hints,
Wolfgang
Am Freitag, 26. Februar 2010 schrieben Sie:
Quoted 34 lines
Dear Juergen,
Quoted 10 lines · Juergen Schindele
Am Freitag, 26. Februar 2010 schrieb Wolfgang Denk:
Quoted 9 lines
Dear Juergen Schindele,
Quoted 5 lines · In message <[email protected]> you wrote:
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the
TEXT_BASE=0x00400000
to not collide with the installed one.Quoted 6 lines
Quoted 2 lines
This is not enough. You must also make sure not to try to perform all the low level initializations again that have already been done.
I know that, but
SKIP_LOW_LEVEL_INITis defined because register init is done with kirkwood boot header for booting from SPI/NAND-Flash. I dont see other blocking points. :-( i tried to skip relocate too but it did not help !I have absolutely no experience concerning kirkwood, but did the same for coldfire for running U-Boot as the flasher application started from the debugger...
IIRC there were three places I had to change for coldfire:
- low-level init: do not put the vector table at the beginning of code (probably better: initialize it in the proper place?)
- leave the vector base register as it is (should be set up properly by first loader/debugger, and U-Boot does not use interrupts)
- the cpu speed detection/setting code was basically switched back to detection forCONFIG_MONITOR_IS_IN_RAMbecause it involved putting the RAM to self-refresh, which is obviously not possible when running from it
Quoted 3 lines
(For Coldfire, a special case was that I had to disable monitor protection manually because the standard condition fails due to the memory layout.)
Thanks for your hint. It lead me to comment out "kirkwood_mpp_conf" in function "board_init" and now it works quite great like expected. In my understanding the mpp configuration of rd6281a is buggy !?
we'll see in furter tests.
Quoted 12 lines
Here's my patch for Coldfire MCF532x/7x:
http://www.mail-archive.com/u-boot at lists.denx.de/msg28779.htmlBTW, disabling relocation may lead to bad results for malloc and the initial stack setup. I am not sure but seem to remember I had some problems when I tried it - and, it should not be a problem to do it as usual anyways if everything else is working correctly.
Hope this can give some useful hints,
Wolfgang
--------------------------------------------------------------
J?rgen Schindele
Software-Entwicklung
NENTEC Netzwerktechnologie GmbH
Greschbachstr. 12
76229 Karlsruhe
Deutschland
Telefon: +49 721 94249-51 Telefax: +49 721 94249-10 E-Mail: schindele at nentec.de WEB: www.nentec.de
Gesch?ftsf?hrung: Klaus Becker, Roland Knapp
Sitz der Gesellschaft: Karlsruhe
Handelsregister: Amtsgericht Mannheim HRB 107658
--------------------------------------------------------------
Quoted 47 lines
-----Original Message-----
From: u-boot-bounces at lists.denx.de
[mailto:u-boot-bounces at lists.denx.de] On Behalf Of Juergen Schindele
Sent: Friday, February 26, 2010 8:36 PM
To: Wolfgang Wegner
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] boot from ram on rd-6281-aAm Freitag, 26. Februar 2010 schrieben Sie:
Quoted 14 lines
Dear Juergen,
Quoted 11 lines · Juergen Schindele
Am Freitag, 26. Februar 2010 schrieb Wolfgang Denk:
Quoted 10 lines
Dear Juergen Schindele,
Quoted 5 lines · In message <[email protected]> you wrote:
i need a different bootloader than the one installed. so i tried to develop a private one by loading it to RAM. So i modified the
TEXT_BASE=0x00400000
to not collide with the installed one.This is not enough. You must also make sure not to try
to perform all
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
the low level initializations again that have already been done.
I know that, but
SKIP_LOW_LEVEL_INITis defined because register init is done with kirkwood boot header for booting from SPI/NAND-Flash. I dont see other blocking points. :-( i tried to skip relocate too but it did not help !I have absolutely no experience concerning kirkwood, but
did the same
Quoted 9 lines
for coldfire for running U-Boot as the flasher application started from the debugger...
IIRC there were three places I had to change for coldfire:
- low-level init: do not put the vector table at the beginning of code (probably better: initialize it in the proper place?)
- leave the vector base register as it is (should be set up properly by first loader/debugger, and U-Boot does not use interrupts)
- the cpu speed detection/setting code was basicallyswitched back to
Quoted 2 lines
detection for
CONFIG_MONITOR_IS_IN_RAMbecause it involved putting the RAM to self-refresh, which is obviously not possiblewhen running
Quoted 8 lines
Quoted 5 lines
from it
(For Coldfire, a special case was that I had to disable monitor protection manually because the standard condition fails due to the memory layout.)
Thanks for your hint. It lead me to comment out "
kirkwood_mpp_conf" in function "board_init" and now it works quite great like expected. In my understanding the mpp configuration of rd6281a is buggy !?
Hi J?rgen Schindele
Good to know that u-boot from RAM works well for you
The "Kirkwood_mpp_config" reads mpp registers and writes them back as per configuration provided in kwmpp_cponfig.
If the config you are providing for your board are different, certainly the things may not work, but if they are same, I don't see any reason it should not work.
Even in case of standard u-boot.kwb booting from SPI/NAND the DRAM initialization is done by bootROM header first and then mpp config is done.
So I don't think it's buggy,
if you further have some detailed findings with some explaination, certainly I would like to patch to improve it.
Regards..
Prafulla . .