Re: [uClinux-dev] uclinux with RAM size problem

2007-05-10 Thread Greg Ungerer 

Hi Will,

will wrote:
I have used 2x32M SDRAM on my board, the loader did chip select well and 
I think it is not neccesory to do chip select again


in kernel, is that right?


Normally that is right, the boot loader sets up chip selects and
SDRAM.


When I used 128k ramfs image, the system will boot well and work, but 
sometimes it hangs up in the situation using


memory.


From what you describe it would seem like SDRAM is not quite
configured and working properly. You need to closely look at
your SDRAM setup.


I think, as Greg said, I have my SDRAM working in unormal status. I 
cannot allocate memory larger than 1M enven I have choose


the option allocate large memory and I cannot use static array larger 
than 500k in my program. Also, when I tar a tarball with size larger


than 500k, the system hangs..

 


Forgive my poor English and this is my first time using mailist.

Would you plese told me how to "Re" your mails as you do show in the 
thread tree and how to quot your mail content? ^_^


Most email readers will do this for you if you hit the "Reply"
button...

Regards
Greg




not sure if I remember it right, seems the chip select was done in boot
loader and uclinux does not do this in kernel.

Bin


On 5/9/07, Greg Ungerer > wrote:

 >/
/>/ Hi Will,
/>/
/>/ will wrote:
/>/ > I have encoutered some problems with my coldfire m5272 board running
/>/ > uclinux of version 2.6.17-uc1.
/>/ >
/>/ > My board has 64M sdram and I configured the "CONFIG_RAMSIZE" with the
/>/ > value of 0x0400 instead of the default value 8M. When I 
increase the

/>/ > ramfs image from 128k default to 2048k, system will hang up while
/>/ > expanding the ramfs image. Then, I configured the ram size back to the
/>/ > default value 8M, the system works well and never hang up again.
/>/
/>/ I f you use the 128k ramfs image, but with the memory size set to
/>/ 64MB does the system boot and work?
/>/
/>/ Are you sure that all 64MB of SDRAM is actually working properly?
/>/
/>/ Regards
/>/ Greg
/>/
/>/
/



ÏÖÔÚ¹ºÂò21CNÆóÒµÓÊÏä,¼´¿ÉÓÃ100Ôª»»5000Ôª! 

ÖíÄêÐдóÔË£¬²ÂͼӮ»°·Ñ£¡ 






___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev


--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
Secure Computing CorporationPHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] uclinux with RAM size problem

2007-05-09 Thread Tao Wang 
Hi, Mr. Huang,
 I think you don't need to set the CS in kernel. As for the SDRAM, it is 
not easy to make it work, so first, I think you'd better check the problem in 
your bootloader, some bootloaders such as u-boot can do memory write and read, 
so you can use these operations to check if the SDRAM on board can be accessed 
properly. If not, the problem is in your bootloader, so you may need to ask the 
hardware engineer, what is parameters of SDRAM, and then how to initialize it 
to work properly.
 In summay, testing the SDRAM from bootloader if possible, then when it is 
passed the test, starting you kernel load and boot.
 Good luck to you.
 

will <[EMAIL PROTECTED]> wrote: Hi Greg & Bin,
 I have used 2x32M SDRAM on my board, the loader did chip select well and I 
think it is not neccesory to do chip select again 
 in kernel, is that right?
 When I used 128k ramfs image, the system will boot well and work, but 
sometimes it hangs up in the situation using
 memory.
 I think, as Greg said, I have my SDRAM working in unormal status. I cannot 
allocate memory larger than 1M enven I have choose
 the option allocate large memory and I cannot use static array larger than 
500k in my program. Also, when I tar a tarball with size larger
 than 500k, the system hangs..
  
 Forgive my poor English and this is my first time using mailist.
 Would you plese told me how to "Re" your mails as you do show in the thread 
tree and how to quot your mail content? ^_^
  
 Thank you very much!
  
 Best Regards,
 Will Huang
  
 not sure if I remember it right, seems the chip select was done in boot
loader and uclinux does not do this in kernel.

Bin


On 5/9/07, Greg Ungerer  wrote:
>
> Hi Will,
>
> will wrote:
> > I have encoutered some problems with my coldfire m5272 board running
> > uclinux of version 2.6.17-uc1.
> >
> > My board has 64M sdram and I configured the "CONFIG_RAMSIZE" with the
> > value of 0x0400 instead of the default value 8M. When I increase the
> > ramfs image from 128k default to 2048k, system will hang up while
> > expanding the ramfs image. Then, I configured the ram size back to the
> > default value 8M, the system works well and never hang up again.
>
> I  f you use the 128k ramfs image, but with the memory size set to
> 64MB does the system boot and work?
>
> Are you sure that all 64MB of SDRAM is actually working properly?
>
> Regards
> Greg
>
>




ÏÖÔÚ¹ºÂò21CNÆóÒµÓÊÏä,¼´¿ÉÓÃ100Ôª»»5000Ôª!
ÖíÄêÐдóÔË£¬²ÂͼӮ»°·Ñ£¡
  ___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

   
-
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] uclinux with RAM size problem

2007-05-09 Thread Greg Ungerer 

Hi Will,

will wrote:
I have encoutered some problems with my coldfire m5272 board running 
uclinux of version 2.6.17-uc1.


My board has 64M sdram and I configured the "CONFIG_RAMSIZE" with the 
value of 0x0400 instead of the default value 8M. When I increase the 
ramfs image from 128k default to 2048k, system will hang up while 
expanding the ramfs image. Then, I configured the ram size back to the 
default value 8M, the system works well and never hang up again.


If you use the 128k ramfs image, but with the memory size set to
64MB does the system boot and work?

Are you sure that all 64MB of SDRAM is actually working properly?

Regards
Greg


I am very confused about this problem and does anyone can give me advice 
to solve the problem?


Thanks in advance!

PS: following is my kernel config and console output

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.17-uc1
# Wed May  9 09:56:32 2007
#
CONFIG_M68K=y
# CONFIG_MMU is not set
# CONFIG_FPU is not set
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_TIME_LOW_RES=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_SYSCTL is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_UID16=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_EMBEDDED=y
# CONFIG_KALLSYMS is not set
# CONFIG_HOTPLUG is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
# CONFIG_FUTEX is not set
# CONFIG_EPOLL is not set
CONFIG_SLAB=y
CONFIG_TINY_SHMEM=y
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
CONFIG_OBSOLETE_INTERMODULE=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set

#
# Block layer
#
# CONFIG_BLK_DEV_IO_TRACE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Processor type and features
#
# CONFIG_M68328 is not set
# CONFIG_M68EZ328 is not set
# CONFIG_M68VZ328 is not set
# CONFIG_M68360 is not set
# CONFIG_M5206 is not set
# CONFIG_M5206e is not set
# CONFIG_M520x is not set
# CONFIG_M523x is not set
# CONFIG_M5249 is not set
# CONFIG_M5271 is not set
CONFIG_M5272=y
# CONFIG_M5275 is not set
# CONFIG_M528x is not set
# CONFIG_M5307 is not set
# CONFIG_M532x is not set
# CONFIG_M5407 is not set
CONFIG_COLDFIRE=y
CONFIG_CLOCK_SET=y
CONFIG_CLOCK_FREQ=
CONFIG_CLOCK_DIV=1

#
# Platform
#
CONFIG_M5272C3=y
# CONFIG_COBRA5272 is not set
# CONFIG_CANCam is not set
# CONFIG_SCALES is not set
# CONFIG_NETtel is not set
# CONFIG_CPU16B is not set
# CONFIG_MOD5272 is not set
CONFIG_FREESCALE=y
CONFIG_LARGE_ALLOCS=y
CONFIG_4KSTACKS=y

#
# RAM configuration
#
CONFIG_RAMBASE=0x
CONFIG_RAMSIZE=0x0400
CONFIG_VECTORBASE=0x
CONFIG_KERNELBASE=0x0002
CONFIG_RAMAUTOBIT=y
# CONFIG_RAM8BIT is not set
# CONFIG_RAM16BIT is not set
# CONFIG_RAM32BIT is not set

#
# ROM configuration
#
# CONFIG_ROM is not set
CONFIG_RAMKERNEL=y
# CONFIG_ROMKERNEL is not set
CONFIG_CF_SHARED_INTS=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
# CONFIG_PCI is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PCI Hotplug Support
#

#
# Executable file formats
#
CONFIG_BINFMT_FLAT=y
# CONFIG_BINFMT_ZFLAT is not set
# CONFIG_BINFMT_SHARED_FLAT is not set
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Power management options
#
# CONFIG_PM is not set

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_GENETLINK=y
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_IPSEC_NAT_TRAVERSAL is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFI