Thanx again Ulf.

I have to find how my board is configurated. I use an Artila Cpu board and try to make my own build root and Kernel. But i have no idea how the memeory is mapped. I will try to get this information from them.

When i Compile only the kernel and upload it to the board, i get an error message from the kernel about a mismatch with the Machine ID. The machine Id is for a DK but i have compiled the kernel for a EK so this doesn't work.

I need to know exactly how the memory is mapped to continue with this board i think ?


regards.

Jonathan

If you use *my* u-boot, you can do
setenv machid <xxx>
and then magically, you can boot an AT91RM9200EK
kernel on an AT91RM9200DK U-boot.

Look in the u-boot file for the AT91RM9200DF.
You will have to set the SETENV configuration item.
(Don't remember its exact name off the top of my head)

Hi ulf,

Right now is not your u-boot in there. I have the one from Artila. I don'tk know it they make another ID for their build or not. I have to check on their FTP server to see if i find other information about this.

I think i will have to know if the boot is done from a df or standard flash to be able to build the rootfs for this board ?

regards

Jonathan

U-Boot and the Linux kernel needs to agree on the Machine Id,
but the root fs is not involved.

You can build a root fs for a dataflash based board
and use it on a parallel flash based board up to a point.

Everything in $(TARGET_DIR) is generic
but when you make a file system like JFFS2, then
you need to specify erase block size etc,
which differs between dataflash and parallel flash.

hi Ulf,

the U-boot that is used, is 1.1.5. I have access now to their compiled rootfs and filsystem, u-boot.

When i try to update the board with the last version (or any other version) of the kernel and the filsystem, the system hangs after writing:

Resetting ....
Starting M501.............
Starting kernel ...

Uncompressing Linux.............................................................
.................................. done, booting the kernel.

that it.

I will try to contact them to see if i can do something.

regards

Jonathan

Hi,

I have found the flash chip that is used on my board. IT,s an intel Strataflash of 128Mbits

It a 128P30 (P30 family). Now i want to know what is the parameter that i need to put in the kernel to configure the right memory type, page size and erase block size.

here the link to the datasheet. I think the Erase block size is 0x8000 but for the rest i don't know realy.

http://download.intel.com/design/flcomp ... 666608.pdf

regards

jonathan

Ok I found the problem, The console is disabled by default.

Jonathan

I'm working with an AT91SAM9260 EK from Atmel. I used the buildroot script commenting out all the boards but AT91SAM9260dfc. I didn't realize (and correct me if I'm wrong) that dfc means running off a Dataflash card, i.e., not the data flash already on the board. So the AT91 Bootloader would hang I guess looking for a flash card I didn't have.

I switched it to EK reran the script and with the resulting build I was able to get into U-boot from the built in flash. However, I can't seem to get past UBoot. For one thing, the UBoot that builds with buildroot shows the dataflash as 1 big area. The UBoot from the Atmel Linux demo shows 4 areas. Another problem is that I get a "bad CRC, using default environment" every time I run and it doesn't remember any of the environment changes I make using savenv. I can boot the kernel but it never finds the rootfs (I'm trying to use a jffs2 filesystem on the flash).

Is the 9260EK supported or do I have to run off a dataflash card? I've ordered one anyway, but I wonder if I'm doing something wrong. Although I have plenty of linux experience I've never worked with it in an embedded environment.

Thanks.

rsepulve:

You can get the board booting off of DataFlash. The easy way around your current problem is to just use the U-Boot binary that comes with the board. For a real fix, the only thing you need to change is which chip select U-Boot uses for DataFlash (it is CS1 on the -ek). I made a few posts in the previous buildroot thread about some things I needed to tweak.

I also use a gzipped ext2 fs in RAM.

Hello,

It seems fakeroot has moved on to 1.8.1.
I changed the $buildroot_root/buildroot-atmel/package/fakeroot/fakeroot.mk
file to read FAKEROOT_VERSION:=1.8.1, reran the script and it finished.
I didn't try to load the files onto the board yet because I have some problems with SAM-BA and reseting the interrupt vectors, but are we able to submit patches to buildroot?
Edit: N/M I send it to buildroot mailing list =)

On Debian host I must change fakeroot version to 1.5.10

http://packages.debian.org/fakeroot