Need help on ftp and telnet in my Ramdisk

2006-06-27 Thread Denny
 
 

Hi,
 
   1. I copied the ftp and telnet commands to my /bin, and the needed library 
is also copied to my /lib, but they still don't work so far, can anybody tell 
me why, thanks!
 
 
logs:
...
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k init
init started:  BusyBox v1.1.3 (2006.06.23-09:32+) multi-call binary
Bad inittab entry: :reth0: link is up, 100 FDX
Starting pid 23, console /dev/ttyS1: '/bin/application'
Starting pid 24, console /dev/ttyS1: '/bin/bash'
### Application running ...
bash-3.00# ]
bash: ]: command not found
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# ftp 192.168.65.143
ftp: ftp/tcp: unknown service
bash-3.00# telnet 192.168.65.143
telnet: telnet: bad port
Starting pid 29, console /dev/ttyS1: '/bin/application'
Starting pid 30, console /dev/ttyS1: '/bin/bash'
### Application running ...
Starting pid 33, console /dev/ttyS1: '/bin/bash'
Starting pid 32, console /dev/ttyS1: '/bin/application'
### Application running ...
bash-3.00# 
 
Thanks!
- Denny
 
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/0745e7ec/attachment.htm
 


Need help on ftp and telnet in my Ramdisk

2006-06-27 Thread Denny
Hi,
 
   1. I copied the ftp and telnet commands to my /bin, and the needed library 
is also copied to my /lib, but they still don't work so far, can anybody tell 
me why, thanks!
 
 
logs:
...
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k init
init started:  BusyBox v1.1.3 (2006.06.23-09:32+) multi-call binary
Bad inittab entry: :reth0: link is up, 100 FDX
Starting pid 23, console /dev/ttyS1: '/bin/application'
Starting pid 24, console /dev/ttyS1: '/bin/bash'
### Application running ...
bash-3.00# ]
bash: ]: command not found
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# ftp 192.168.65.143
ftp: ftp/tcp: unknown service
bash-3.00# telnet 192.168.65.143
telnet: telnet: bad port
Starting pid 29, console /dev/ttyS1: '/bin/application'
Starting pid 30, console /dev/ttyS1: '/bin/bash'
### Application running ...
Starting pid 33, console /dev/ttyS1: '/bin/bash'
Starting pid 32, console /dev/ttyS1: '/bin/application'
### Application running ...
bash-3.00# 
 
Thanks!
- Denny
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/46130edf/attachment.htm
 


Need help on adding a command to my ramdi sk

2006-06-27 Thread Denny
Hi, 
 
   Since there is no ldd command in busybox1.1.3, so I copied it from ELDK4.0 
to my bin,
but it didn't work, can anybody tell me how to add a new command to my ramdisk ?
 
bash-3.00# ldd /bin/ftp
sh: applet not found
bash-3.00# 
 
 
- Denny
 
 
 
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/04cab4ea/attachment.htm
 


Need help on adding a command to my ramdi sk

2006-06-27 Thread Denny
 
 

Hi, 
 
   Since there is no ldd command in busybox1.1.3, so I copied it from ELDK4.0 
to my bin,
but it didn't work, can anybody tell me how to add a new command to my ramdisk ?
 
bash-3.00# ldd /bin/ftp
sh: applet not found
bash-3.00# 
 
 
- Denny
 
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/ccd60608/attachment.htm
 


MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006

2006-06-27 Thread Zhang Wei-r63237
Hi, 

Please see inline comments.

Best Regards,
Zhang Wei

 -Original Message-
 From: 
 linuxppc-embedded-bounces+wei.zhang=freescale.com at ozlabs.org 
 [mailto:linuxppc-embedded-bounces+wei.zhang=freescale.com at ozla
 bs.org] On Behalf Of Florian Boelstler
 Sent: Monday, June 26, 2006 6:48 PM
 To: linuxppc-embedded at ozlabs.org
 Subject: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
 
 Hi,
 
 I am currently working on a MPC8548-based development system.
 Linux kernel version is 2.6.11 with patches delivered from 
 Freescale (BSP MPC8548CDS 02/24/2006).
 
 Kernel configuration contains a warning message for CONFIG_PEX:
 This requires hardware modification to work correctly if 
 your CPU version  2.0 and will break the PCI bus. [...]
 
 I was wondering whether enabling PCIe makes PCI bus 
 functionality unusable at all (including kernel functionality 
 for detecting devices behind a transparent PCI-to-PCI bridge).

The interrupts polarity of MPC8548 PCIe controller is reversed to PCI. That's 
an errata of MPC8548.
So you must rework to fix them. You can find the detail from user manual of bsp.

 
 Our setup connects a transparent PLX8516 PCI-to-PCI bridge to 
 the PCIe port of the MPC8548 daughter board. Behind that 
 bridge is another PCIe capable device.
 MPC8548 is configured to run as PCIe host mode.
 
 When trying to lookup the PCIe devices using lspci I can only 
 see the PPC itself and the bridge.
 However I cannot see the device(s) behind the bridge.

Yes, that's also an errata to MPC8548 PCIe controller.
Trying to apply below patch code:

diff -u -r1.1.1.2.2.3 ppc85xx_setup.c
--- arch/ppc/syslib/ppc85xx_setup.c 7 Apr 2006 08:57:50 -   
1.1.1.2.2.3
+++ arch/ppc/syslib/ppc85xx_setup.c 27 Jun 2006 02:45:54 -
@@ -256,6 +256,7 @@
 {
volatile struct ccsr_pex *pex;
unsigned short temps;
+   unsigned int pribus;
bd_t *binfo = (bd_t *) __res;
 
pex = ioremap(binfo-bi_immr_base + MPC85xx_PEX_OFFSET,
@@ -265,6 +266,11 @@
temps |= PCI_COMMAND_SERR | PCI_COMMAND_MASTER | PCI_COMMAND_MEMORY;
early_write_config_word(hose, 0, 0, PCI_COMMAND, temps);
early_write_config_byte(hose, 0, 0, PCI_LATENCY_TIMER, 0x80);
+
+   /* PCIE Bus, Fix the MPC8548 host bridge's location to bus 0xFF. */
+   early_read_config_dword(hose, 0, 0, PCI_PRIMARY_BUS, pribus);
+   pribus = (pribus  0xff00) | (0xff) | (0x0  8) | (0xfe  16);
+   early_write_config_dword(hose, 0, 0, PCI_PRIMARY_BUS, pribus);
 
/* Disable all windows (except powar0 since its ignored) */
pex-pexowar1 = 0; 
 
 Is there another method for detecting PCI(e) devices?
 Is BSP MPC8548CDS 02/24/2006 the latest version 
 corresponding to that hardware?

Yes, it's the last version.

 
 Thanks in advance,
 
Florian
 
 ___
 Linuxppc-embedded mailing list
 Linuxppc-embedded at ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-embedded
 



Need help on ftp and telnet in my Ramdisk

2006-06-27 Thread Denny
Yes, it is the root cause, thanks Lee!
 
Thanks  Regards!
- Denny
 
 
 
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/296ff157/attachment.htm
 


Need help ragarding MPC8360 Kernel bootup failure - got solved

2006-06-27 Thread sudheer
Hello All,

I got this problem sorted out.
I have changed the bootargs at u-boot to
setenv bootargs root=/dev/ram rw console=uart,io,0xfe004500
Now i could boot the linux and login.

Thanks  Regards
Sudheer



sudheer wrote:

Hello all,

I need help regarding the bootup of linux on MPC8360 MDS Board.

After doing tftp the uImage from u-boot, with the bootm command  the 
kernel gets uncompressed and stops there.
The serial output from kernel could  not be seen.

Source being used:
 uboot - U-Boot-1.1.3
 linux - Linux-2.6.11 supporting mpc8360epb.
board - MPC8360 MDS

The dump is below:

U-Boot 1.1.3 (ppc83xx-20050315-dev) (Dec 14 2005 - 09:37:59) MPC83XX

Clock configuration:
  Coherent System Bus:  264 MHz
  Core: 528 MHz
  QE:   396 MHz
  Local Bus Controller: 264 MHz
  Local Bus: 66 MHz
  DDR:  264 MHz
  DDR Secondary:264 MHz
  I2C:  264 MHz
CPU: MPC83xx, Rev: 20 at 528 MHz
Board: Freescale MPC8360EPB
I2C:   ready
DRAM:
   SDRAM on Local Bus: 64 MB
   DDR RAM: 256 MB
FLASH: 16 MB
In:serial
Out:   serial
Err:   serial
Net:   FSL GETH0
Hit any key to stop autoboot:  0
= printenv
bootcmd=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrramboot=setenv
bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp
$ramdiskaddr $ramdiskfile;tftp $loarnfsboot=setenv bootargs root=/dev/nfs
rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrbootdelay=6
baudrate=115200
loads_echo=1
ethaddr=00:04:9f:11:22:33
eth1addr=00:E0:0C:00:7D:01
hostname=unknown
loadaddr=20
netdev=eth0
consoledev=ttyS0
ramdiskaddr=40
ramdiskfile=ramfs.83xx
ethact=FSL GETH0
filesize=2d030a
fileaddr=2
gatewayip=192.168.3.1
netmask=255.255.255.0
serverip=192.168.3.81
bootfile=/tftpboot/vmlinux.gz
ipaddr=192.168.3.253
stdin=serial
stdout=serial
stderr=serial

Environment size: 1005/8188 bytes
= setenv bootargs console=ttyS1 root=/dev/ram
= tftp 20 uImage_test
Auto negotiating done
switching to rgmii 100
duplexity: full
mac speed set to: 100
Using FSL GETH0 device
TFTP from server 192.168.3.81; our IP address is 192.168.3.253
Filename 'uImage_test'.
Load address: 0x20
Loading: #
 #
 #
 ###
done
Bytes transferred = 1033098 (fc38a hex)
= bootm 20
## Booting image at 0020 ...
   Image Name:   Linux-2.6.11.12
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1033034 Bytes = 1008.8 kB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

 CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 |  Offline


After Uncompressing kernel, nothing comes onto the minicom.
I have tried the console env in bootargs to ttyS0,  ttyS1, ttyCPM0, ttyCPM1, 
ttyUCC0. But could not succeed.

Anyone Please help me in this regard.

Thanks  Regards
Sudheer


___
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  




MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006

2006-06-27 Thread Florian Boelstler
Hi,

thanks for your quick response.
I'll try the proposed changes today.

Zhang Wei-r63237 schrieb:
 Trying to apply below patch code:
  [...]

Is there a publicly available source for patches to the current BSP?
Are there any other PCIe-related fixes?

Best regards,

   Florian




MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006

2006-06-27 Thread Zhang Wei-r63237
 
 Is there a publicly available source for patches to the current BSP?
 Are there any other PCIe-related fixes?

It's an add-on PCIe patch. We have tested it on MPC8641, but we have no 
PCIe-PCI bridge on MPC8548 platform to do more test. So if you verify it, I'll 
commit it. :)

 
 Best regards,
 
Florian
 
 ___
 Linuxppc-embedded mailing list
 Linuxppc-embedded at ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-embedded
 



Reg RISC timers in MPC 8260

2006-06-27 Thread Jagan
Hi all

We have a requirement of running a periodic timer for
5 millisecond using RISC timers in CPM module of
MPC8260. The OS is monta vista linux and target is
MPC8260 I have written a sample code to start a
periodic timer using MPC8260. 

But it hangs when SET TIMER command is issued to the
CPCR register. The cross compiler we r using is
ppc_82xx-gcc.
 
Can anyone pls help me in getting this right ?

I am pasting the code here 
--
/*Start of code snippet  ignoring the header files */
cpm8xx_t*cpmp;

volatile immap_t *immap = (immap_t *)IMAP_ADDR;

#define CPCR_OPCODE ( 8  8 ) /* CPCR Opcode Field:
SET TIMER */
#define CPCR_CHNUM ( 5  4 ) /* CPCR Ch Num Field:
SPI/IDMA2/RISC Timers */
#define CPCR_FLAG ( 1  0 ) /* CPCR Flag Field:
Process Command */
#define PROFF_RISCTT((uint)0x01B0)

void risc_timer_handler(int irq, void *dev_id, struct
pt_regs *regs)
{
 unsigned int i, rter;

 printk(Inside risc timer handler \n);
 /*read RTER to see which timers have caused
interrupts.
 */
 
 rter  = immap-im_cpm.cp_rter ;

 /*The RISC timer event bits are usually cleared
  *by this time
  */
 immap-im_cpm.cp_rter = 0x ; 

  
}

int  __init device_init(void)
{
   unsigned int ticks = 0;
   unsigned int interval  = 1000;
   unsigned short prescaler = 0; 
   volatile cpm8xx_t*cp;


  /* 
   * Write the TIMEP bits of the RCCR with 11 to
generate the slowest 
   * clock, This value generates a tick every 65,536
clocks, which is every 
   * 2.6 milliseconds at 25 MHz.
   */

   immap-im_cpm.cp_rccr = ( 0x3f  8 );
   
   /*
* Configure the TM_BASE in the RISC timer table
parameter RAM to point to a location in the
* dual-port RAM with 4 bytes available.
*/ 



 //  rt_pram_t *rtt_pramp = (rt_pram_t
*)(cpmp-cp_dparam[PROFF_RISCTT]);


   cp = (cpm8xx_t *)(immap-im_cpm);


   
   rt_pram_t *rtt_pramp = (rt_pram_t *)cp-cp_dparam;

   /*
   * Assuming the beginning of dual-port RAM is
available,
   * write 0x to TM_BASE.
   */



rtt_pramp-tm_base = 0x; 

 
//   rtt_pramp-tm_base = m8xx_cpm_dpalloc(16);  
logic 1

   /*Write 0x to the TM_CNT field in the RISC
timer table 
*parameter RAM to see how many ticks elapsed since
the RISC 
*internal timer was enabled.
   */
   rtt_pramp-tm_cnt  = 0x0;

   /*Write 0x to the RTER to clear any previous
events.
*/

   immap-im_cpm.cp_rter = 0x;

   /* Write 0x0001 to the RTMR to enable RISC timer 0
*  and timer 1 to generate an interrupt.
*/
   immap-im_cpm.cp_rtmr |= 0x1 ;



   if(
request_irq(SIU_INT_RISC,risc_timer_handler,0,0,0) 
0)
   {
 printk(\n unable to register the RISC timer
\n);
   }

  /*Write 0xC000_080D to the TM_CMD field of the RISC
timer table
parameter RAM. This enables RISC timer 0 to
timeout after 2,061(decimal)
ticks of the timer. The timer automatically
restarts after it times out.
  */ 

  rtt_pramp-tm_cmd = 0xC80D ; 

  /* Enter Command:  SET TIMER */

  while (immap-im_cpm.cp_cpcr  CPM_CR_FLG);
 immap-im_cpm.cp_cpcr =
mk_cr_cmd(CPM_CR_CH_SPI, CPM_CR_SET_TIMER) |
CPM_CR_FLG;
  while (immap-im_cpm.cp_cpcr  CPM_CR_FLG);

 
  /* Set RCCR[TIME] to enable the RISC timer to
   * begin operation.  
   */

  immap-im_cpm.cp_rccr = ( 1  15 );


  return 0;
}



  
  
   
void cleanup_device(void)
{
 
 
  request_irq(SIU_INT_RISC, NULL, 0, 0,
0);
  
  
   
  printk(KERN_INFO cleaned up \n);
}
  
  
   
module_init(device_init);
module_exit(cleanup_device);
  
  
   
  
  
   
MODULE_LICENSE(GPL);
  
  
   
MODULE_AUTHOR();
MODULE_DESCRIPTION(driver code);
  
  
   
EXPORT_NO_SYMBOLS;
/*End of code snippet  */
---

Thanks in Advance 
Jagan

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



How to search in this mailing-list?

2006-06-27 Thread Stephen Cheng
hi ALL,

This is maybe a bit silly, but I really don't know:
How to search using some key words in this mailing-list?

Thanks  Best Regards,
Steven C.
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/799e0d26/attachment.htm
 


How to search in this mailing-list?

2006-06-27 Thread Florian Boelstler
Stephen Cheng schrieb:
 This is maybe a bit silly, but I really don't know:
 How to search using some key words in this mailing-list?

You may use one of the options found here:
http://dir.gmane.org/gmane.linux.ports.ppc.embedded

  Florian




How to search in this mailing-list?

2006-06-27 Thread Derycke, Johan
hi,
 
put this google, replace searchstring with whatever you are searching for:
 
searchstring site:ozlabs.org/pipermail
 
br,
 
Johan

   _  

From: [EMAIL PROTECTED]
[mailto:linuxppc-embedded-bounces+johan.derycke=barco.com at ozlabs.org] On
Behalf Of Stephen Cheng
Sent: dinsdag 27 juni 2006 15:24
To: linuxppc-embedded at ozlabs.org
Subject: How to search in this mailing-list?



hi ALL, 

This is maybe a bit silly, but I really don't know: 
How to search using some key words in this mailing-list? 

Thanks  Best Regards,
Steven C.
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/2d2e368c/attachment.htm
 


How to search in this mailing-list?

2006-06-27 Thread Steven Blakeslee
 

   This is maybe a bit silly, but I really don't know: 
   How to search using some key words in this mailing-list? 

Go to google and do a site search

example
site:ozlabs.org/pipermail/linuxppc-embedded/ 440EP






MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006

2006-06-27 Thread Florian Boelstler
Hi,

Zhang Wei-r63237 schrieb:
 It's an add-on PCIe patch. We have tested it on MPC8641, but we have no 
 PCIe-PCI bridge on MPC8548 platform to do more test. So if you verify it, 
 I'll commit it. :)

We did the hardware fix described in the BSP user's manual to make PCIe 
work (according to the manual section 2.1, step 3).
I.e.
  1) removed R193 and R194 on the carrier card (rev 1.2)
  2) removed RN1 on the CPU daughter card
  2a) connected pad3 of RN1 to pin3 of U12 (IRQ0)
  2b) connected pad2 of RN1 to pin4 of U12 (IRQ1)

Does this fix the interrupt polarity problem (as well)?

We applied the provided kernel patch as well.
IMHO that patch just moves the local PCIe root-complex out-of-space so 
no detection of that one occurs any more.
This is what actually happens when lspci is run.

However we still don't see any devices behind the PCIe switch (e.g. a 
transparent PLX8516). It seems that the enumeration process (traversing 
through the bus hierarchy) in the kernel is somehow disabled.
Bottom line: Only one device accessible at all on the PCIe port.

Any further ideas?

Thanks,

   Florian




Lite5200 MTD partitions in 2.6 build

2006-06-27 Thread Rowan, Chad
In the 2.4 build I had to modify icecube.c in /linux/drivers/mtd/maps/ to
specify the u-boot, kernel image, and root fs partitions.  Icecube.c doesn't
exist in the 2.6 drop.  I got the top of the tree from the denx git
yesterday.  How do you config the partitions for the 2.6 kernel?

 

Thanks,
Chad

-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/4f462f81/attachment.htm
 


Lite5200 MTD partitions in 2.6 build

2006-06-27 Thread White
Am Tue, 27 Jun 2006 13:38:25 -0500 schrieb Rowan, Chad
Chad.Rowan at thyssenkrupp.com :

 In the 2.4 build I had to modify icecube.c in /linux/drivers/mtd/maps/ to
 specify the u-boot, kernel image, and root fs partitions.  Icecube.c doesn't
 exist in the 2.6 drop.  I got the top of the tree from the denx git
 yesterday.  How do you config the partitions for the 2.6 kernel?
 
  
 
 Thanks,
 Chad
 

Please throw a look to the Platform Devices MTD memory Mapper.
(drivers/mtd/maps/plat-ram.c)

With this Info you can add the Info to the Plattform Device List. f.e.
in the Board Support File. (lite5200.c ?)


Good Luck,
Gabor



Using bestcomm in an external module (MPC5200B to be exact)

2006-06-27 Thread John Rigby
Yes I know its the work of many people,  calling it your was just an
abbreviation.

The latest ltib isn't based on your latest but then again your latest
was never public:).

So is your git tree uptodate?  If so then I will look at putting
together some patches to it.  I have an ata update and also an ac97
driver.  My goal is to have the best version in the public and ltib
just a copy of it.

On 6/20/06, Sylvain Munaut tnt at 246tnt.com wrote:

  -Original Message-
  From: John Rigby [mailto:jcrigby at gmail.com]
  Sent: Monday, June 19, 2006 2:33 PM
  To: Trueskew
  Cc: Andrey Volkov; linuxppc-embedded at ozlabs.org
  Subject: Re: Using bestcomm in an external module (MPC5200B to be exact)
 
  The next LTIB bsp for 5200b will use the Sylvain's bestcomm api.

 Cool ;) But it's far from being my whole work. The foundation and a good
 cleanup pass comes from Dale and Andrey respectiverly.

 Be sure to use the latest one I sent you though ;p
 BTW, I guess that means your fine with my last modifications ?


 Sylvain



 
 This message was sent using IMP, the Internet Messaging Program.