AW: [microblaze-uclinux] Problems with partitions

["Schleifer, Philipp, PGR2" <Philipp.Schleifer@xxxxxxxxxxxxxxx>]

I have 8 MB linear flash, which i selected in menuconfig.

This is the address range, when doing an xload in xmd console.

(0x22000000-0x227fffff) FLASH_2Mx32 mb_opb

So, do i have to add an offset of 0x22000000 in Line 179 of
driver/mtd/maps/mb_auto.c where the mtd_partition mb_auto_8mb struct
Is defined? 

Philipp

XMD% xload mhs system.mhs
Loading MHS File..
Processor(s) in System ::
Microblaze(1) : microblaze_0
Address Map for Processor microblaze_0
(0x00000000-0x00001fff) dlmb_cntlr dlmb
(0x00000000-0x00001fff) ilmb_cntlr ilmb
(0x22000000-0x227fffff) FLASH_2Mx32 mb_opb
(0x24000000-0x27ffffff) DDR_SDRAM_64Mx32 mb_opb
(0x40600000-0x4060ffff) RS232_Uart mb_opb
(0x41200000-0x4120ffff) opb_intc_0 mb_opb
(0x41400000-0x4140ffff) debug_module mb_opb
(0x41c00000-0x41c0ffff) opb_timer_1 mb_opb


________________________________

Von: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] Im Auftrag von Jason Wu
Gesendet: Donnerstag, 21. September 2006 11:38
An: microblaze-uclinux@xxxxxxxxxxxxxx
Betreff: Re: [microblaze-uclinux] Problems with partitions


Hi Philipp,

This is because the flash map does not match the type of flash you have.
The flash maps are located in driver/mtd/maps/mb_auto.c

Jason


Schleifer, Philipp, PGR2 wrote: 

	Hello, 

	I managed to bootup linux but i cannot login with root/uClinux 
	I think this is because the creation of flash failed. I checked 
	my menuconfig twice - it matches that one from the tutorial by
John Williams. 

	Thanks, Philipp 

	Creating 8 MTD partitions on "Flash":

	0x00000000-0x00004000 : "Bootloader"

	mtd: partition "Bootloader" doesn't end on an erase block --
force read-only


	0x00004000-0x00008000 : "Bootargs"

	mtd: partition "Bootargs" doesn't start on an erase block
boundary -- force read


	-only     
	0x00008000-0x0000c000 : "MAC"                             
	mtd: partition "MAC" doesn't start on an erase block boundary --
force read-only


	0x00010000-0x00020000                    
	mtd: partition "Config" doesn't start on an erase block boundary
-- force read-o


	nly   
	0x0000c000-0x00010000 : "Spare"                               
	mtd: partition "Spare" doesn't start on an erase block boundary
-- force read-on


	ly  
	0x00100000-0x00400000 : "Image"                               
	0x00400000-0x00800000 : "JFFS2"                               
	0x00000000-0x00800000 : "Flash"                               
	MicroBlaze auto-config ram probe(0x240e6904,864256,4): d3000 at
240e6904


	Creating 1 MTD partitions on "RAM":

	0x00000000-0x000d3000 : "Romfs"                               
	VFS: Mounted root (romfs filesystem) readonly.

	Freeing init memory: 40K                        
	Mounting        
	Mounting var:             
	Populating /var:                
	Running local start scripts.                            
	Mounting /etc/config:                     
	Populating /etc/config:                       
	flatfsd: Nonexistent or bad flatfs (-114), creating new one...


	/bin/flatfsd: mtd.c: 156: flat_dev_close: Assertion `flatinfo.fd
!= -1' failed.


	flatfsd: mtd.c: 156: flat_dev_close: Assertion `flatinfo.fd !=
-1' failed.


	Abort     


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/