[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] RE: partition table not found..!



Well, if you did flashitall with the rescue code
from the devboard, you should probably revert the
settings for the partition table and kernelconfig
to the ones that are normally used with the devboard,
and then do a flashitall again just to make sure.

//Peter 

> -----Original Message-----
> From: axis [mailto:axis2list@xxxxxxx.com] 
> Sent: Monday, February 16, 2004 10:47
> To: Peter Kjellerstedt
> Subject: RE: [bluetooth-dev] RE: partition table not found..!
> 
> Sir,
>     I still have the same problem.Actually,out of
> ignorance,last week I did "flashitall" thus erasing
> the rescue partition and now may be because of this
> even if I use the correct parameters as you said Iam
> still not able to boot.So just to confirm,the
> following is the procedure Iam following:
> 1. ptablespec file
>        [ptable]
> # name size     rw-options  type      image-file
> rescue 0x020000 ro          rescue    rescue.img
> flash1 0x2e0000 ro          kernel    flash1.img
> flash2 0x100000 rw          jffs      flash2.img
> 
> 2.  kernelconfig
> CONFIG_ETRAX_PTABLE_SECTOR=131072
> 
> 3.# make kernel
> 4.# make install
> 5.# make images
> 6.# flashit (or boot_linux -f or flashitall)
>       And the following is the boot message on my
> 9010v2 board.Sir,any further advice on this will be of
> great help to sucessfully complete my Masters thesis
> in France.
> Thank you.
> 
> ******************************
> Linux/CRIS port on ETRAX 100LX (c) 2001, 2002 Axis
> Communications AB
> Kernel command line: root=/dev/mtdblock3
> Enabling watchdog...
> Calibrating delay loop... 99.53 BogoMIPS
> Memory: 14600k/16384k available (1023k kernel code,
> 1784k reserved, 420k data, 40k init)
> kmem_create: Forcing size word alignment - mm_struct
> kmem_create: Forcing size word alignment - filp
> Dentry cache hash table entries: 2048 (order: 1, 16384
> bytes)
> Inode cache hash table entries: 1024 (order: 0, 8192
> bytes)
> kmem_create: Forcing size word alignment - inode_cache
> Mount-cache hash table entries: 1024 (order: 0, 8192
> bytes)
> kmem_create: Forcing size word alignment - bdev_cache
> kmem_create: Forcing size word alignment - cdev_cache
> Buffer-cache hash table entries: 2048 (order: 0, 8192
> bytes)
> Page-cache hash table entries: 2048 (order: 0, 8192
> bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society
> NET3.039
> kmem_create: Forcing size word alignment - sock
> Initializing RT netlink socket
> Starting kswapd
> kmem_create: Forcing size word alignment - file lock
> cache
> JFFS version 1.0, (C) 1999, 2000  Axis Communications
> AB
> kmem_create: Forcing size word alignment - jffs_node
> Bluetooth Driver v1.3, Copyright (c) 2000, 2001, 2002
> Axis Communications AB
> BT SYS: Bluetooth driver registered as ttyBT
> BT SYS: Bluetooth line discipline registered.
> BT SYS: Registering BT proc files
> Proc entry registered
> BT SYS: Bluetooth Driver Using ttyBT[0-6] (data),
> ttyBTC (ctrl [7])
> BNEP driver v0.1 (c) 2002 Axis Communications AB
> bnep0 initialized
> bnep1 initialized
> bnep2 initialized
> bnep3 initialized
> bnep4 initialized
> bnep5 initialized
> bnep6 initialized
> kmem_create: Forcing size word alignment -
> blkdev_requests
> PPP generic driver version 2.4.2
> PPP Deflate Compression module registered
> ETRAX 100LX 10/100MBit ethernet v2.0 (c) 2000-2001
> Axis Communications AB
> eth0 initialized
> eth0: changed MAC to 00:40:8C:CD:00:00
> ETRAX 100LX serial-driver 1.40 $, (c) 2000-2002 Axis
> Communications AB
> ttyS0 at 0xb0000060 is a builtin UART with DMA
> ttyS2 at 0xb0000070 is a builtin UART with DMA
> ttyS3 at 0xb0000078 is a builtin UART with DMA
> fast_timer_init()
> cse0: Probing a 0x04000000 bytes large window at
> 0xe0000000.
> cse0: Probing for AMD compatible flash...
> cse0: Found 1 x 2MiB Fujitsu MBM29LV160TE at 0x0
> cse1: Probing a 0x04000000 bytes large window at
> 0xe4000000.
> cse1: Probing for AMD compatible flash...
> cse1: Found 1 x 2MiB Fujitsu MBM29LV160TE at 0x0
> Concatenating MTD devices:
> (0): "cse0"
> (1): "cse1"
> into device "cse0+cse1"
> cse0+cse1: 0x00400000 bytes of flash memory.
>  Adding readonly flash partition for romfs image:
>   /dev/flash1 at 0x000ae884, size 0x0015a000
>  Using default partition table.
> Creating 3 MTD partitions on "cse0+cse1":
> 0x00000000-0x00010000 : "boot firmware"
> 0x00010000-0x001b0000 : "kernel"
> 0x001b0000-0x00200000 : "filesystem"
> GPIO port G: in_bits: 0x3FFF003F out_bits: 0x3E00FF3E
> val: 7DFF00C1
> GPIO port G: dir: 0000FF00 changeable: 01FFFF01
> ETRAX 100LX GPIO driver v2.5, (c) 2001, 2002 Axis
> Communications AB
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> kmem_create: Forcing size word alignment -
> ip_dst_cache
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP: Hash tables configured (established 2048 bind
> 4096)
> ip_conntrack (128 buckets, 1024 max)
> ip_tables: (C) 2000-2002 Netfilter core team
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> IPv6 v0.8 for NET4.0
> kmem_create: Forcing size word alignment -
> ip6_dst_cache
> IPv6 over IPv4 tunneling driver
> ip6_tables: (C) 2000-2002 Netfilter core team
> NET4: Ethernet Bridge 008 for NET4.0
> VFS: Cannot open root device "mtdblock3" or 1f:03
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 1f:03
> 
> 
> 
> 
> --- Peter Kjellerstedt <peter.kjellerstedt@xxxxxxx.com>
> wrote:
> > I was just reminded by a colleague that there is a
> > kernel 
> > configuration option called
> > CONFIG_ETRAX_PTABLE_SECTOR
> > that indicates where the MTD code look for the
> > partition 
> > table. In the devboard this is 65536, but for the
> > 9010v2
> > it is 131072. You should use the latter value in
> > your
> > kernelconfig file to get the correct behavior for
> > your
> > devboard running on the 9010v2.
> > 
> > //Peter
> > 
> > > -----Original Message-----
> > > From: owner-bluetooth-dev On Behalf Of Peter
> > Kjellerstedt
> > > Sent: 13 February 2004 18:11
> > > To: axis
> > > Cc: Bluetooth-dev
> > > Subject: [bluetooth-dev] RE: partition table not
> > found..!
> > > 
> > > 
> > > The partition table is placed at the start of the
> > > romfs/cramfs partition, which comes directly after
> > > the rescue partition. The important thing here is
> > > the size of the rescue partition. For the 9010v2
> > > this is 0x20000 whereas it is 0x10000 for the
> > > devboard 82. So you must make sure that the
> > > partition table ends up at the correct location
> > > for the rescue code to jump to it correctly.
> > > However, this should all be automatically handled
> > > as long as you use the correct partition table,
> > > i.e., the one that corresponds to the rescue
> > > partition that is actually in the flash.
> > > 
> > > //Peter
> > > 
> > > > -----Original Message-----
> > > > From: axis [mailto:axis2list@xxxxxxx.com] 
> > > > Sent: 13 February 2004 17:08
> > > > To: Peter Kjellerstedt
> > > > Cc: Bluetooth-dev
> > > > Subject: partition table not found..!
> > > > 
> > > > 
> > > > Sir,
> > > >     I just checked the mtd
> > driver(axisflashmap.c) to
> > > > see why my image is not able to find the
> > partition
> > > > table and I could see that the following
> > condition is
> > > > always false
> > > > if ((ptable_head->magic ==
> > PARTITION_TABLE_MAGIC).....
> > > >     I tried to print the location of the
> > ptable_head
> > > > in both cases:
> > > > 1.when ptable not found : 0xf001000a (printed
> > before
> > > > entering the above if)
> > > > 2.when ptable found     : 0xf002000a
> > > >     In the first case,as no valid partition
> > table
> > > > found its using the defualt ptable
> > > > 
> > > > ..... Using default partition table.
> > > > Creating 3 MTD partitions on "cse0+cse1":
> > > > 0x00000000-0x00010000 : "boot firmware"
> > > > 0x00010000-0x001b0000 : "kernel"
> > > > 0x001b0000-0x00200000 : "filesystem" ..........
> > > >      Iam still using the ptable you have given
> > and it
> > > > would be of great help if you could tell me how
> > to
> > > > specify the ptable location ...or may the
> > > > PARTITION_TABLE_MAGIC (do we need to specify
> > this)..
> > > >      Hope to hear from you regarding this..
> > > > Thank you.

-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com