> I've not looked at this lately, but consider this: You have to be=20
> careful not running
> into the mem area where blob's stack and code is.
> I thought I have done this correctly, tough.
> Could you please validate that there's no code/stack in the area you=20
I'm using the same locations as with the Assabet board:
#define BLOB_RAM_BASE (0xc0100000)
#define KERNEL_RAM_BASE (0xC0008000)
#define PARAM_RAM_BASE (0xc0110000)
#define RAMDISK_RAM_BASE (0xC0400000)
> And, what board/configuration do you use? Is memory detected correctly=20
> sizes, adresses etc.)?
At the moment I'm working with a new board/custom board. SA-1110, 2x 32M
SDRAM chips (i.e. 64M total). The memory is detected correctly with
testmem2.S and blob is running fine on it.
I've also tried the chkmem tests on a LART board and I run into the same
problems. With what board did you test with?
After 14 non-maintainer releases, I'm the S-Lang non-maintainer.
-- Ray Dassen
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Antree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@... Kenilworth, 7700
Http: http://www.2d3d.com South Africa
Get latest updates about Open Source Projects, Conferences and News.