Re: some question about linux kernel in embed system

2007-08-17 Thread Florian A. Voegel

Hi,

what kind of hardware are you using? Try passing the console device name you 
want to use on the kernel command line, ie console=consoledev

Greets,

Florian

On Fri, 17 Aug 2007 10:58:01 +0800
李明 [EMAIL PROTECTED] wrote:

 hello everyone 
 I am doing some embed system works.
 Now I want to replant the linux-2.4.32 to my own system.
 But there are some questions.First let me introduce my heardware:
 I use powerpc+flash+sdram to buildup a mini system,use u-boot 1.1.4 as 
 bootloader then I need to replant the kernel on it .
 The linux-2.4.32 kernel which was made a uImage, is running in this mini 
 system, the question is appear:
 Image Name:   Linux-2.4.32
Created:  2007-08-16  21:31:03 UTC
Image Type:   PowerPC Linux Kernel Image (gzip compressed)
Data Size:685809 Bytes = 669.7 kB
Load Address: 
Entry Point:  
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
 then the kernel is dead, I do not know what is problem,please give me some 
 clew,thanks!   
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: GPIO interrupts on mpc8313e

2007-08-01 Thread Florian A. Voegel
Is the interrupt configured properly for whatever it is you connect to it? 
(level vs edge triggered, rising vs falling)

Best regards,
Florian


On Wed, 1 Aug 2007 14:45:05 +0300
Yoni Levin [EMAIL PROTECTED] wrote:

  
 
 I want to receive interrupt from 1 GPIO port (for example 14)
 
 I changed the GPIMR to 0x (so I need to get interrupts from all GPIO
 ports)
 
 And then request the irq by :
 
 irq_create_mapping(NULL,74);
 
 request_irq(74,handler,IRQF_DISABLED,GPIO,NULL);
 
 the return value is 0 (OK)
 
 but I cant receive any interrupt.
 
 do I need to do something else?
 
  
 
  
 
 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Re: creation of jffs2 rootfile system..

2007-07-27 Thread Florian A. Voegel

Hi Nethra,

what does your inittab and your startup files look like? It looks like

- your inittab does not start a getty but rather a shell, thus no login
- your /proc isn't mounted, and it's needed for ps to work properly


Greets,

Florian Voegel
Carangul.Tech

On Thu, 26 Jul 2007 23:41:32 -0700 (PDT)
Nethra [EMAIL PROTECTED] wrote:

 
 when boot the board with jffs2 rootfile system i m getting output like this,
 
 TCP: Hash tables configured (established 4096 bind 8192)
 IPv4 over IPv4 tunneling driver
 NET: Registered protocol family 1
 NET: Registered protocol family 10
 IPv6 over IPv4 tunneling driver
 NET: Registered protocol family 17
 Disabled Privacy Extensions on device c02527a0(lo)
 IP-Config: Incomplete network configuration information.
 Empty flash at 0xffa0 ends at 0x0001
 Empty flash at 0x0002ffec ends at 0x0003
 Empty flash at 0x0004ffe8 ends at 0x0005
 Empty flash at 0x0006ffc8 ends at 0x0007
 Empty flash at 0x0008fffc ends at 0x0009
 Empty flash at 0x000afffc ends at 0x000b
 Empty flash at 0x000cfffc ends at 0x000d
 Empty flash at 0x000efffc ends at 0x000f
 Empty flash at 0x0010fffc ends at 0x0011
 Empty flash at 0x0012fffc ends at 0x0013
 Empty flash at 0x0014fffc ends at 0x0015
 Empty flash at 0x0016fffc ends at 0x0017
 Empty flash at 0x0018fffc ends at 0x0019
 Empty flash at 0x001cfffc ends at 0x001d
 Empty flash at 0x001efffc ends at 0x001f
 Empty flash at 0x0020fffc ends at 0x0021
 Empty flash at 0x0022fffc ends at 0x0023
 Empty flash at 0x0024fffc ends at 0x0025
 Empty flash at 0x0026fffc ends at 0x0027
 Empty flash at 0x002afffc ends at 0x002b
 Empty flash at 0x002cfffc ends at 0x002d
 VFS: Mounted root (jffs2 filesystem).
 Freeing unused kernel memory: 108k init
 
 Please press Enter to activate this console.
 / #
 / #
 / #
 
 login prompt itself is not coming and
  
 ps command is not working
 # ps
   PID  Uid VmSize Stat Command
 #
 
 what is the problem..?
 
 waiting for early response,
 Nethra
 
 -- 
 View this message in context: 
 http://www.nabble.com/creation-of-jffs2-rootfile-system..-tf4155759.html#a11823840
 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
 
 ___
 Linuxppc-embedded mailing list
 Linuxppc-embedded@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-embedded
 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Re: SDRAM failures on MPC5200B

2007-07-20 Thread Florian A. Voegel
Hi,

Considering the age of the U-Boot version you're using, it's most likely the 
problem with the SD-RAM controller of the 5200B. Later U-Boot versions fix this 
I think by writing a value of 4 to the register at MBAR+0x0190, which does 
_something_ to resolve the problem. It worked for us. However, we still had 
problems with SD-RAM in conjunction with other components, so we switched to 
DDR which has worked flawlessly so far - you might want to consider doing the 
same.

Greets,

Florian Voegel
Carangul.Tech

On Fri, 20 Jul 2007 10:40:30 -0500
lokowich [EMAIL PROTECTED] wrote:

 We're working on bringing up a MPC5200B version of our original MPC5200 
 board using U-Boot 1.1.4 configured for Icecube/Lite5200B.  Other than 
 the CPU, the board is identical.  The bootloader crashes just after 
 relocation to RAM, often with a Program Check Exception, typically a 
 memory corruption issue.  I noticed failures at different stages after 
 relocation based on content, suggesting problems with upper SDRAM.  If I 
 force the initram to 1/2 the determined size (64MB instead of 128MB), 
 then everything works well through kernel load and initialization.  
 We've added termination resistors to improve AD signals, to no avail.  
 Memory tests work fine too.  Any help is appreciated.
 
 Thanks,
 Mark Lokowich
 Systems Engineer
 Advanced Communication Design
 7901 12th Ave. So.
 Bloomington, MN 55425
 952-854-4000
 [EMAIL PROTECTED]
 
 This email was Anti Virus checked by Astaro Security Gateway. 
 http://www.astaro.com
 
 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded