No subject


Mon Mar 6 08:03:00 EST 2006


Sanjay,

It appears you are doing everything correctly. If your CF was probed 
successfully in RB you will be able to see it using the disks
command..if 
you cannot see it using disks you won't be able to load anything off it.

I recall there were some timing related issues in RB 2.01 for certain
slow 
CFs...which prompted an update to RB 2.02.

I would recommend either trying an alternate CF or flashing your Avila
with 
the latest RB. You can get the latest binary at:

http://gateworks.unixstudios.net/BSP/GW15002_Rev_0.6/JTAG%20Software%20and%20Images/

Use a RB binary from there appropriate to the memory size of your Avila.

Thanks!

-Dave

>
> Gordon,
>
> The board has 2.0.1 Redboot installed.  I have not upgraded the redboot
> on the board, but these are the latest boards I got from Gateworks.
>
> ...sanjay
>
>
>
>
> -------- Original Message --------
> Subject: RE: [Avila] compact flash help
> From: "Gordon Edmonds" <gordon at gateworks.com>
> Date: Fri, March 03, 2006 3:04 pm
> To: "'Avila'" <avila at lists.unixstudios.net>
>
> Sanjay,
>
> What version of Redboot are you running?  Is it the one from
> the latest release?
>
> Gordon
>
> -----Original Message-----
> From: sanjay at newpacket.com [mailto:sanjay at newpacket.com]
> Sent: Wednesday, March 01, 2006 12:10 AM
> To: Avila
> Cc: Avila
> Subject: [Avila] compact flash help
>
>
>
> Gents,
>
> I'm trying to get CF working on the Avila board.  I followed the
> instructions in the README_AvilaCompactFlash file.  The version of the
> board I have supports redboot 2.01. Consequently I'm trying to set it
> up with RedBoot CF/IDE Support.
>
> After I create the CF (ext2 file system) and plug it into the Avila
> card, I try to manually load the zImage from the CF.
>
> I type in load -r -m disk -b 0x01600000 hda1:zImage
>
> The response I get is "Cant load 'hda1:zImage': unsupported filesystem.
>
> When I type in "disks" I don't get anything.  I am expecting to see
> hda1.
>
> Since I'm new to this, I imagine I'm probably skipping some critical
> step.
>
> Thanks in advance,
> ....Sanjay Gidwani
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
> For additional commands, e-mail: avila-help at lists.unixstudios.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
> For additional commands, e-mail: avila-help at lists.unixstudios.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
> For additional commands, e-mail: avila-help at lists.unixstudios.net
>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net 

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

Date: Wed, 8 Mar 2006 09:58:54 -0700
To: "Avila" <avila at lists.unixstudios.net>
From: "Burns, Darrell" <dburns1 at ibahn.com>
Subject: RE: [Avila] compact flash help
Message-ID: <B9277E488FF89C40882D798E3022421F08C6601B at s-exc01-slc-ftu.stsn.com>

Sanjay,

I have successfully used the flash.exe under windows 98 DOS Mode.  There =
is an easier way, however, to update the Redboot image.  Simply create a =
Linux Kernel that does not have the redboot partition protected ( Memory =
Technology Devices (MTD)  ---> Force read-only for RedBoot system =
images). Make sure that "RedBoot partition table parsing" is selected.

Once you have loaded the kernel on your board, make sure you have a =
/dev/mtdblock0 device.  If you don't, you need to create one with the =
"mknod /dev/mtdblock0 b 31 0" command.

Next, download the redboot.bin image to your board using tftp or ftp, =
and use this command: cp redboot.bin /dev/mtdblock0.  This will replace =
your redboot image with the new one.

You will note that "cat /proc/mtd" produces the following mapping:

dev:    size   erasesize  name
mtd0: 00080000 00020000 "RedBoot"
mtd1: 00100000 00020000 "zimage"
mtd2: 003c0000 00020000 "ramdisk"
            ...

Darrell Burns
Sr. Firmware Engineer
iBAHN
10757 S. River Front Parkway, Suite 300
South Jordan, UT  84095
801.563.2023 direct
dburns1 at ibahn.com

-----Original Message-----
From: sanjay at newpacket.com [mailto:sanjay at newpacket.com]
Sent: Monday, March 06, 2006 10:49 PM
To: Avila
Subject: RE: [Avila] compact flash help
Subject: [Avila] Dave,

Thanks. =20

In regards to burning RB as I remember you need a dos machine right.  I
remember talking to Gordon about this.  The problem is we no longer
maintain any dos stuff.  Do you know if I can go into a dos window of
windows 95 or windows 98 and would flash.exe still work?  I'll try to
dig up the jtag cable tomorrow.

I notice that the redboot binary requires I know the size of the ram.=20
How do I figure out what the RAM size is of the board I have?  Is there
a command in the redboot I can use? =20

Thanks,
Sanjay

=20
-------- Original Message --------
Subject: Re: [Avila] compact flash help
From: "Dave" <daveg at unixstudios.net>


More information about the Avila mailing list