[U-Boot-Users] at91rm9200 - silent console

[U-Boot-Users] at91rm9200 - silent console

[Craig Robinson]

Dear List

I have a at91rm9200ek based board on which I am trying to get u boot 1.2.0
running, without success. 

I have also tried to compile and run u-boot for the ek directly from the
source, all be it with unmodified at91rm9200dk_config. This does not work
either. When I load the uboot.bin into flash (with a J-Link ICE) at
0x10000000 and reboot I get nothing on the DBGU console. Is this what you
would expect for an ek board with un-patched 1.2.0 source? I have seen
references to patches from Ulf for an EK board in the list - is there
something I am missing? Is the at91rm92000 support broken in the latest
version? Not sure if the recent thread [ARM cleanup - was: [GIT PULL] [ARM]
Please pull fromgit://denx.de/git/u-boot-arm.git] suggested it was...

Just to put my mind at rest I have also tried to compile and run u-boot with
CONFIG_SKIP_LOWLWEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT defined. I thought
this may then allow loading and running uboot using the loader.bin programme
provided by Atmel. However, I got as far as a report that u-boot was
downloaded successfully and then silence....is this what you would expect?

Also, I'm a bit confused by the following snippet from at91rm9200dk.h:

#ifdef CFG_ENV_IS_IN_DATAFLASH
#define CFG_ENV_OFFSET			0x20000
#define CFG_ENV_ADDR			(CFG_DATAFLASH_LOGIC_ADDR_CS0 +
CFG_ENV_OFFSET)
#define CFG_ENV_SIZE			0x2000  /* 0x8000 */
#else
#define CFG_ENV_IS_IN_FLASH		1
#ifdef CONFIG_SKIP_LOWLEVEL_INIT
#define CFG_ENV_ADDR			(PHYS_FLASH_1 + 0x60000)  /* after
u-boot.bin */
#define CFG_ENV_SIZE			0x10000 /* sectors are 64K here */
#else
#define CFG_ENV_ADDR			(PHYS_FLASH_1 + 0xe000)  /* between
boot.bin and u-boot.bin.gz */
#define CFG_ENV_SIZE			0x2000  /* 0x8000 */
#endif	/* CONFIG_SKIP_LOWLEVEL_INIT */
#endif	/* CFG_ENV_IS_IN_DATAFLASH */

Does the above say (or imply through comments) that if we are booting from
flash and skipping low level init then the format of uboot is an
umcompressed binary and boot.bin is not used? Is this backwards or am I?

On our new board there is a different flash chip to the, now obsolete, one
on the ek board. I have altered flash.h and board/at91rm9200xxx/flash.c
along the lines of the patch by Nicolas Lacressonniere (24 Jun 2004) to
1.1.1 to take this into account. We are now using the AT49BV642D. I believe
it is compatible in all respects, aside from CFI ID, with the previous chip
(AT49BV6416). If anyone knows this to be incorrect then please let me know! 

Many thanks for you help and I hope I have not asked anything too obviously
daft!

Best regards,
Craig Robinson.

Circuitree Ltd
W: www.cctree.co.uk


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.485 / Virus Database: 269.13.13/998 - Release Date: 10/09/2007
08:48
 

[U-Boot-Users] at91rm9200 - silent console

[Ulf Samuelsson]

----- Original Message ----- 
From: "Craig Robinson" <craig.robinson@cctree.co.uk>
To: <u-boot-users@lists.sourceforge.net>
Sent: Monday, September 10, 2007 5:45 PM
Subject: [U-Boot-Users] at91rm9200 - silent console


> Dear List
> 
> I have a at91rm9200ek based board on which I am trying to get u boot 1.2.0
> running, without success. 
> 

You may want to get the u-boot-1.2.0-atmel.tar.bz2 from

ftp://at91dist:distrib at 81.80.104.162/ -> AT91 Third Party -> Linux Host -> Source

This supports the AT91RM9200 booting from dataflash.

It also contains a number of other things which really simplifies 
the experience of booting linux, which unfortunately is rejected
for inclusion into mainstream u-boot.

This version is not an official Atmel release, but I have included all patches
from the Atmel 1.1.5 version.

An easy way to get this done is to download the buildroot script
from the www.at91.com Linux Forum.
(The buildroot project in www.at91.com is too old)
This will build a cross compiler, linux, u-boot and dataflashboot.


> I have also tried to compile and run u-boot for the ek directly from the
> source, all be it with unmodified at91rm9200dk_config. This does not work
> either. When I load the uboot.bin into flash (with a J-Link ICE) at
> 0x10000000 and reboot I get nothing on the DBGU console. Is this what you
> would expect for an ek board with un-patched 1.2.0 source? I have seen
> references to patches from Ulf for an EK board in the list - is there
> something I am missing? Is the at91rm92000 support broken in the latest
> version? Not sure if the recent thread [ARM cleanup - was: [GIT PULL] [ARM]
> Please pull fromgit://denx.de/git/u-boot-arm.git] suggested it was...
> 
> Just to put my mind at rest I have also tried to compile and run u-boot with
> CONFIG_SKIP_LOWLWEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT defined. I thought
> this may then allow loading and running uboot using the loader.bin programme
> provided by Atmel. However, I got as far as a report that u-boot was
> downloaded successfully and then silence....is this what you would expect?
> 
> Also, I'm a bit confused by the following snippet from at91rm9200dk.h:
> 
> #ifdef CFG_ENV_IS_IN_DATAFLASH
> #define CFG_ENV_OFFSET 0x20000
> #define CFG_ENV_ADDR (CFG_DATAFLASH_LOGIC_ADDR_CS0 +
> CFG_ENV_OFFSET)
> #define CFG_ENV_SIZE 0x2000  /* 0x8000 */
> #else
> #define CFG_ENV_IS_IN_FLASH 1
> #ifdef CONFIG_SKIP_LOWLEVEL_INIT
> #define CFG_ENV_ADDR (PHYS_FLASH_1 + 0x60000)  /* after
> u-boot.bin */
> #define CFG_ENV_SIZE 0x10000 /* sectors are 64K here */
> #else
> #define CFG_ENV_ADDR (PHYS_FLASH_1 + 0xe000)  /* between
> boot.bin and u-boot.bin.gz */
> #define CFG_ENV_SIZE 0x2000  /* 0x8000 */
> #endif /* CONFIG_SKIP_LOWLEVEL_INIT */
> #endif /* CFG_ENV_IS_IN_DATAFLASH */
> 
> Does the above say (or imply through comments) that if we are booting from
> flash and skipping low level init then the format of uboot is an
> umcompressed binary and boot.bin is not used? Is this backwards or am I?
> 
> On our new board there is a different flash chip to the, now obsolete, one
> on the ek board. I have altered flash.h and board/at91rm9200xxx/flash.c
> along the lines of the patch by Nicolas Lacressonniere (24 Jun 2004) to
> 1.1.1 to take this into account. We are now using the AT49BV642D. I believe
> it is compatible in all respects, aside from CFI ID, with the previous chip
> (AT49BV6416). If anyone knows this to be incorrect then please let me know! 
> 
> Many thanks for you help and I hope I have not asked anything too obviously
> daft!
> 
> Best regards,
> Craig Robinson.
> 
> Circuitree Ltd
> W: www.cctree.co.uk
> 
> 


Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group        mailto:avr32 at atmel.com
http://www.avrfreaks.net/;            http://avr32linux.org/
http://www.at91.com/ ;                ftp://at91dist:distrib at 81.80.104.162/

[U-Boot-Users] at91rm9200 - silent console

[Leonid]

Unlike more "traditional" PPC versions of u-boot, at91... U-boot is not
the first code running on the board. The first one is normally some
small bootstrap, running from dataflash or flash itself - it depends on
jumper settings and also u-bbot configuration must be right. 

Search this list's archives - this question has been discussed many
times in different forms.

Leonid.

-----Original Message-----
From: u-boot-users-bounces@lists.sourceforge.net
[mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf Of Craig
Robinson
Sent: Monday, September 10, 2007 8:46 AM
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] at91rm9200 - silent console

Dear List

I have a at91rm9200ek based board on which I am trying to get u boot
1.2.0 running, without success. 

I have also tried to compile and run u-boot for the ek directly from the
source, all be it with unmodified at91rm9200dk_config. This does not
work either. When I load the uboot.bin into flash (with a J-Link ICE) at
0x10000000 and reboot I get nothing on the DBGU console. Is this what
you would expect for an ek board with un-patched 1.2.0 source? I have
seen references to patches from Ulf for an EK board in the list - is
there something I am missing? Is the at91rm92000 support broken in the
latest version? Not sure if the recent thread [ARM cleanup - was: [GIT
PULL] [ARM] Please pull fromgit://denx.de/git/u-boot-arm.git] suggested
it was...

Just to put my mind at rest I have also tried to compile and run u-boot
with CONFIG_SKIP_LOWLWEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT defined.
I thought this may then allow loading and running uboot using the
loader.bin programme provided by Atmel. However, I got as far as a
report that u-boot was downloaded successfully and then silence....is
this what you would expect?

Also, I'm a bit confused by the following snippet from at91rm9200dk.h:

#ifdef CFG_ENV_IS_IN_DATAFLASH
#define CFG_ENV_OFFSET			0x20000
#define CFG_ENV_ADDR			(CFG_DATAFLASH_LOGIC_ADDR_CS0 +
CFG_ENV_OFFSET)
#define CFG_ENV_SIZE			0x2000  /* 0x8000 */
#else
#define CFG_ENV_IS_IN_FLASH		1
#ifdef CONFIG_SKIP_LOWLEVEL_INIT
#define CFG_ENV_ADDR			(PHYS_FLASH_1 + 0x60000)  /*
after
u-boot.bin */
#define CFG_ENV_SIZE			0x10000 /* sectors are 64K here
*/
#else
#define CFG_ENV_ADDR			(PHYS_FLASH_1 + 0xe000)  /*
between
boot.bin and u-boot.bin.gz */
#define CFG_ENV_SIZE			0x2000  /* 0x8000 */
#endif	/* CONFIG_SKIP_LOWLEVEL_INIT */
#endif	/* CFG_ENV_IS_IN_DATAFLASH */

Does the above say (or imply through comments) that if we are booting
from flash and skipping low level init then the format of uboot is an
umcompressed binary and boot.bin is not used? Is this backwards or am I?

On our new board there is a different flash chip to the, now obsolete,
one on the ek board. I have altered flash.h and
board/at91rm9200xxx/flash.c along the lines of the patch by Nicolas
Lacressonniere (24 Jun 2004) to
1.1.1 to take this into account. We are now using the AT49BV642D. I
believe it is compatible in all respects, aside from CFI ID, with the
previous chip (AT49BV6416). If anyone knows this to be incorrect then
please let me know! 

Many thanks for you help and I hope I have not asked anything too
obviously daft!

Best regards,
Craig Robinson.

Circuitree Ltd
W: www.cctree.co.uk


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.485 / Virus Database: 269.13.13/998 - Release Date:
10/09/2007
08:48
 


------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

[U-Boot-Users] at91rm9200 - silent console

[Leonid]

Hi, Ulf: 
___________________________________________________________________
On Monday, September 10, 2007 3:10 PM Ulf Samuelsson wrote:

> An easy way to get this done is to download the buildroot script
> from the www.at91.com Linux Forum.
> (The buildroot project in www.at91.com is too old)
> This will build a cross compiler, linux, u-boot and dataflashboot.

Can you please provide a link on latest (not obsolete) at91rm9200
buildroot?

Thanks,

Leonid.

[U-Boot-Users] at91rm9200 - silent console

[Ulf Samuelsson]

tis 2007-09-11 klockan 15:58 -0700 skrev Leonid:
> Hi, Ulf: 
> ___________________________________________________________________
> On Monday, September 10, 2007 3:10 PM Ulf Samuelsson wrote:
> 
> > An easy way to get this done is to download the buildroot script
> > from the www.at91.com Linux Forum.
> > (The buildroot project in www.at91.com is too old)
> > This will build a cross compiler, linux, u-boot and dataflashboot.
> 
> Can you please provide a link on latest (not obsolete) at91rm9200
> buildroot?
> 

Download the buildroot tarball with the latest date from

ftp://at91supp:support at 81.80.104.162/ -> AT91 Third Party support ... ->
Linux_Host -> Source

IIRC it is 2007-06-07.


You can also go to www.at91.com Linux Forum and look for buildroot. 
There should be a script which downloads the stuff above.
It is no longer maintained, since I got write access to the main
buildroot svn.

Someone just broke the AT91 support though, so todays tarball
wont work.

I will try to fix this immediately.


> Thanks,
> 
> Leonid.
-- 
Best Regards,
Ulf Samuelsson          mail:   ulf at atmel.com
Atmel Nordic AB
Box 2033, 174 52 Sundbyberg
Kavalleriv?gen 24, 174 58 Sundbyberg
Sweden
Tel:    +46 8 441 54 22 GSM:    +46 706 224457

[U-Boot-Users] at91rm9200 - silent console

[Craig Robinson]

Hi Leonid & Ulf

Thank-you for the pointers to the atmel patched code and buildroot scripts. 

Can I confirm with you that the correct way to set up u-boot for an
at91rm9200 is to use two boot loaders. Can I also confirm that, to boot from
parallel flash, the first stage boot loader is boot.bin and that this will
load a gzipped version of u-boot. The fact that the atmel source from Ulf's
ftp generates a gzipped binary when built suggests to me that this is so.
I've seen different opinions on the newsgroup, including some pretty
emphatic ones from Wolfgang that u-boot will just work on its own, and
frankly am a bit confused! 

If u-boot should be started by boot.bin are there any specific CONFIG
settings to go along with this? Eg. do we need LOWLEVEL_INIT or not? Also
I'd be grateful if you could point me at the CONFIG (if any) needed to boot
from parallel flash and not dataflash. I think this used to have something
to do with CONFIG_BOOTBINFUNC but now that's been replaced...?

Many thanks
Craig

-----Original Message-----
From: Leonid [mailto:Leonid at a-k-a.net] 
Sent: 10 September 2007 23:20
To: Craig Robinson; u-boot-users at lists.sourceforge.net
Subject: RE: [U-Boot-Users] at91rm9200 - silent console

Unlike more "traditional" PPC versions of u-boot, at91... U-boot is not
the first code running on the board. The first one is normally some
small bootstrap, running from dataflash or flash itself - it depends on
jumper settings and also u-bbot configuration must be right. 

Search this list's archives - this question has been discussed many
times in different forms.

Leonid.

-----Original Message-----
From: u-boot-users-bounces@lists.sourceforge.net
[mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf Of Craig
Robinson
Sent: Monday, September 10, 2007 8:46 AM
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] at91rm9200 - silent console

Dear List

I have a at91rm9200ek based board on which I am trying to get u boot
1.2.0 running, without success. 

I have also tried to compile and run u-boot for the ek directly from the
source, all be it with unmodified at91rm9200dk_config. This does not
work either. When I load the uboot.bin into flash (with a J-Link ICE) at
0x10000000 and reboot I get nothing on the DBGU console. Is this what
you would expect for an ek board with un-patched 1.2.0 source? 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date: 10/09/2007
17:43
 

[U-Boot-Users] at91rm9200 - silent console

[Leonid]

Hi, Craig:

I am using two stage boot loader for Atmel reference board. While there
are indeed different opinions whether this is correct way to go, but
such concept certainly works.

If your first stage boot, u-boot and u-boot environment are on NOR flash
(on the very begiining of it you must program boot.bin) you should undef
both DATAFLASH config and lovel init flags in <board>.h include file. 

......

#define CONFIG_SKIP_LOWLEVEL_INIT       1

....

#undef  CFG_ENV_IS_IN_DATAFLASH

....


at91rm9200dk.h which is in u-boot tree already is a good start point. 

Regards,

Leonid.

-----Original Message-----
From: Craig Robinson [mailto:craig.robinson at cctree.co.uk] 
Sent: Wednesday, September 12, 2007 2:20 AM
To: Leonid; u-boot-users at lists.sourceforge.net; ulf at atmel.com
Subject: RE: [U-Boot-Users] at91rm9200 - silent console

Hi Leonid & Ulf

Thank-you for the pointers to the atmel patched code and buildroot
scripts. 

Can I confirm with you that the correct way to set up u-boot for an
at91rm9200 is to use two boot loaders. Can I also confirm that, to boot
from parallel flash, the first stage boot loader is boot.bin and that
this will load a gzipped version of u-boot. The fact that the atmel
source from Ulf's ftp generates a gzipped binary when built suggests to
me that this is so.
I've seen different opinions on the newsgroup, including some pretty
emphatic ones from Wolfgang that u-boot will just work on its own, and
frankly am a bit confused! 

If u-boot should be started by boot.bin are there any specific CONFIG
settings to go along with this? Eg. do we need LOWLEVEL_INIT or not?
Also I'd be grateful if you could point me at the CONFIG (if any) needed
to boot from parallel flash and not dataflash. I think this used to have
something to do with CONFIG_BOOTBINFUNC but now that's been replaced...?

Many thanks
Craig

-----Original Message-----
From: Leonid [mailto:Leonid at a-k-a.net]
Sent: 10 September 2007 23:20
To: Craig Robinson; u-boot-users at lists.sourceforge.net
Subject: RE: [U-Boot-Users] at91rm9200 - silent console

Unlike more "traditional" PPC versions of u-boot, at91... U-boot is not
the first code running on the board. The first one is normally some
small bootstrap, running from dataflash or flash itself - it depends on
jumper settings and also u-bbot configuration must be right. 

Search this list's archives - this question has been discussed many
times in different forms.

Leonid.

-----Original Message-----
From: u-boot-users-bounces@lists.sourceforge.net
[mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf Of Craig
Robinson
Sent: Monday, September 10, 2007 8:46 AM
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] at91rm9200 - silent console

Dear List

I have a at91rm9200ek based board on which I am trying to get u boot
1.2.0 running, without success. 

I have also tried to compile and run u-boot for the ek directly from the
source, all be it with unmodified at91rm9200dk_config. This does not
work either. When I load the uboot.bin into flash (with a J-Link ICE) at
0x10000000 and reboot I get nothing on the DBGU console. Is this what
you would expect for an ek board with un-patched 1.2.0 source? 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date:
10/09/2007
17:43
 

[U-Boot-Users] at91rm9200 - silent console

[Leonid]

Than you, Ulf. Tarball doesn't work indeed. I could create workable filesystem from January buildroot, but if you can suggest better/newer sources, I'd appreciate that.

Thanks,

Leonid.  

-----Original Message-----
From: Ulf Samuelsson [mailto:ulf at atmel.com] 
Sent: Tuesday, September 11, 2007 7:34 PM
To: Leonid
Cc: Craig Robinson; u-boot-users at lists.sourceforge.net
Subject: RE: [U-Boot-Users] at91rm9200 - silent console

tis 2007-09-11 klockan 15:58 -0700 skrev Leonid:
> Hi, Ulf: 
> ___________________________________________________________________
> On Monday, September 10, 2007 3:10 PM Ulf Samuelsson wrote:
> 
> > An easy way to get this done is to download the buildroot script 
> > from the www.at91.com Linux Forum.
> > (The buildroot project in www.at91.com is too old) This will build a 
> > cross compiler, linux, u-boot and dataflashboot.
> 
> Can you please provide a link on latest (not obsolete) at91rm9200 
> buildroot?
> 

Download the buildroot tarball with the latest date from

ftp://at91supp:support at 81.80.104.162/ -> AT91 Third Party support ... -> Linux_Host -> Source

IIRC it is 2007-06-07.


You can also go to www.at91.com Linux Forum and look for buildroot. 
There should be a script which downloads the stuff above.
It is no longer maintained, since I got write access to the main buildroot svn.

Someone just broke the AT91 support though, so todays tarball wont work.

I will try to fix this immediately.


> Thanks,
> 
> Leonid.
--
Best Regards,
Ulf Samuelsson          mail:   ulf at atmel.com
Atmel Nordic AB
Box 2033, 174 52 Sundbyberg
Kavalleriv?gen 24, 174 58 Sundbyberg
Sweden
Tel:    +46 8 441 54 22 GSM:    +46 706 224457