Mounting PRAMFS support

Hi,

Im using a ppc85xx processor with Denx ELDK (4.1) The board  has 512MB
DDR2 and the board config reserves 64M for pram. during bootup the
mem=$mem argument is passed to the linux kernel command line and linux
boots successfully.

I am unable to mount the PRAMFS - all documentation leads me to use

mount -t pramfs -o physaddr=0x1c000000,init=0x4000000 none /mnt

witch fails with the message:
mounting none on /mtd failed: no such devise 

I have tried mounting using busybox v1.3  that comes with ELDK4.2 and
with busybox v1.10 and have not had success.
Can anyone help

-- 
Pieter Henning
VASTech

Tel: +27 (0)21 850 5921
Fax: +27 (0)86 503 8941
e-mail: phenning@vastech.co.za

Dear Pieter,

In message [off-list ref] you wrote:

Im using a ppc85xx processor with Denx ELDK (4.1) The board  has 512MB
DDR2 and the board config reserves 64M for pram. during bootup the
mem=$mem argument is passed to the linux kernel command line and linux
boots successfully.

So what are the exact boot messages of your kernel?

I am unable to mount the PRAMFS - all documentation leads me to use

mount -t pramfs -o physaddr=0x1c000000,init=0x4000000 none /mnt

-------------------------------------------------------------^^^^

witch fails with the message:
mounting none on /mtd failed: no such devise 

-------------------^^^^

/mnt != /mtd

There is something worng, probably your description. It would be
better if you showed the precise commands and outpout from your
target system.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Open the pod bay doors, HAL."                    - Dave Bowman, 2001

Hi Wolfgang

thanks for your quick reply. Below i have placed the boot message,
Another question I have that might help is that in DULG  section 5.10
where the environmental variable "pram" is defined,  the documentation
states "If the "Protected RAM" feature is enabled in your board's
configuration" 
Is the PRAMFS support  built in and available when CONFIG_PRAM and the
"pram" environmental variable is defined in the board config or are
there other elements to be configured or activated on the linux side
aswell?.  (mpc8548 board using  ELDK 4.1 ppc_85xx)

The boot message:

U-Boot 1.2.0 (Aug 12 2008 - 16:21:15)

CPU:   8548_E, Version: 1.1, (0x80390011)
Core:  E500, Version: 1.0, (0x80210010)
Clock Configuration:
       CPU: 990 MHz, CCB: 396 MHz,
       DDR: 198 MHz, LBC:  49 MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: Equus MPC8548
    PCI1: 64 bit, 66 MHz, sync
I2C:   ready
DRAM:  Initializing
    DDR: 512 MB
FLASH: 128 MB
L2 cache 512KB: enabled
*** Warning - bad CRC, using default environment

BIE:
  serial number = EQ_0002
  build level   = EQUUS-1.1
  set ethaddr  to 00:50:C2:52:50:FC
  set eth1addr to 00:50:C2:52:50:FD
  set eth2addr to 00:50:C2:52:50:FE
  set bootsrc  to factory
Running boot diagnostics

152 more lines

Dear Pieter,

In message [off-list ref] you wrote:
  

quoted

Im using a ppc85xx processor with Denx ELDK (4.1) The board  has 512MB
DDR2 and the board config reserves 64M for pram. during bootup the
mem=$mem argument is passed to the linux kernel command line and linux
boots successfully.
    

So what are the exact boot messages of your kernel?

  

quoted

I am unable to mount the PRAMFS - all documentation leads me to use

mount -t pramfs -o physaddr=0x1c000000,init=0x4000000 none /mnt
    

-------------------------------------------------------------^^^^
  

quoted

witch fails with the message:
mounting none on /mtd failed: no such devise 
    

-------------------^^^^

/mnt != /mtd
  

--------------^^^^
This was a typo

There is something worng, probably your description. It would be
better if you showed the precise commands and outpout from your
target system.

Best regards,

Wolfgang Denk

  

-- 
Pieter Henning
VASTech

Tel: +27 (0)21 850 5921
Fax: +27 (0)86 503 8941
e-mail: phenning@vastech.co.za

Hi all

I am using U-Boot 1.3.4 and an ELDK linux Kernel snapshot from the Denx
Git dated 14th October 2008-10-23

My custom architecture is based around a Power PC 860 processor.

I have written a Flattened Device Tree for the architecture.

 

I am having some trouble with the allocation of the Buffer Descriptors
when microcode is loaded.

My IMMR address is 0xfa200000 and the DPRAM is located at 0xfa202000.

 

The buffer descriptors are trying to be located at 0xfa202040, which is
all 0xFFs, as indicated by the cp_rccr = 0x3

I am debugging this with a BDI3000

 

My SMC console works fine IF I set rccr back to 0x0 during console_init
and the buffers are then allocated at 0xfa202040.

 

U-boot.1.3.4 is configured to use install micro code,
CFG_I2C_UCODE_PATCH. 

 

Rightly or wrongly I have based my DTS file on the mpc866ads.dts file.

The relevant section of the DTS to setup the DPRAM space is,

 

141 more lines

Gray, Steve - UK wrote:

I have tried a few things, including setting the range of muram to ranges = <0x0 0x3000 0x1000>;

Am I correct to assume this will push the muram above the microcode??

No, that will confuse the kernel into thinking that muram starts at IMMR offset 0x3000.  You need to change the reg property of the data subnode to <0x1000 0xc00>, so that you restrict the allocation range without affecting the offset that is subtracted from the physical address to obtain the value given to the CPM.

-Scott

Hi Scott
Thanks for the notes on modifying the data subnode.=20
I am pleased to say this has fixed the problem and the console is
working now.


Kind Regards

Stve

-----Original Message-----
From: Scott Wood [mailto:<redacted>]=20
Sent: 23 October 2008 16:32
To: Gray, Steve - UK
Cc: <redacted>
Subject: Re: Ucode/BD conflict on PowerPC 860

Gray, Steve - UK wrote:

I have tried a few things, including setting the range of muram to=20
ranges =3D <0x0 0x3000 0x1000>;
=20
Am I correct to assume this will push the muram above the microcode??

No, that will confuse the kernel into thinking that muram starts at IMMR

offset 0x3000.  You need to change the reg property of the data subnode=20
to <0x1000 0xc00>, so that you restrict the allocation range without=20
affecting the offset that is subtracted from the physical address to=20
obtain the value given to the CPM.

-Scott