Hi,
   I think the issue is in x-loader, the version of which is ''Texas
Instruments X-Loader 1.51". I just merged some RAM related commits from
http://gitorious.org/x-load-omap3/mainline/ into this x-loader. Now the
whole 512M RAM is working fine.

   Thanks for your help.

    I am checking which commit fixed the issue.

On Tue, Aug 28, 2012 at 1:51 PM, shakti tiwari
<[email protected]>wrote:

> Hi
> we have verify memtest is working fine for 512 MB .
>
> #####################################################
> U-Boot 2010.06 (Aug 17 2012 - 12:44:39)
>
> OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  HW ECC [Kernel/FS layout] selected
> 0 MiB
> *** Warning - bad CRC or NAND, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Beagle xM Rev A/C
> Die ID #005c00029ff800000163810c1202f00b
> Hit any key to stop autoboot:  0
> OMAP3 beagleboard.org # mtest 0x90000000 0x90000400 0x5555 10000
> Pattern FFFF2AAB  Writing...  Reading...Tested 65536 iteration(s) with 0
> errors.
> OMAP3 beagleboard.org #
> #########################################################
>
> On Monday, August 27, 2012 3:44:48 PM UTC+5:30, Wendell Gong wrote:
>>
>> yes, I tested with mtest from u-boot.
>>
>> # mtest 0x90000000 0x90000400 0x5555
>>
>> mtest prints "Mem error @..."
>>
>> On Monday, August 27, 2012 5:44:45 PM UTC+8, Arun Joseph wrote:
>>>
>>>  Did you try memtest utilities from u-boot/kernel?
>>>
>>> Regards,
>>> Arun
>>>
>>> On Monday 27 August 2012 03:14 PM, Wendell Gong wrote:
>>>
>>> yes. I get the source code and built them.
>>>
>>> On Monday, August 27, 2012 5:40:16 PM UTC+8, Vishveshwar wrote:
>>>>
>>>> Do you see this issue when you use the x-loader and u-boot built from
>>>> sources too?
>>>>
>>>> On Monday, August 27, 2012 3:03:09 PM UTC+5:30, Wendell Gong wrote:
>>>>>
>>>>> beagleboard xM
>>>>>
>>>>> you know that BB-xm has 512M RAM, but mem=256M in your JB release for
>>>>> BB-xM
>>>>>
>>>>> On Mon, Aug 27, 2012 at 5:15 PM, Arun Joseph <[email protected]> wrote:
>>>>>
>>>>>>  Hi,
>>>>>>
>>>>>> Which is the platform?
>>>>>> Is it beagleboard or beaglebone?
>>>>>>
>>>>>> Regards,
>>>>>> Arun
>>>>>>
>>>>>>
>>>>>> On Monday 27 August 2012 02:47 PM, Wendell Gong wrote:
>>>>>>
>>>>>> Hi,
>>>>>>     I can not increase the RAM from 256M to 512M. I think there is
>>>>>> issue in u-boot and(or) x-loader.
>>>>>> u-boot printed "DRAM: 512MiB", but actually the 256M-512M RAM is
>>>>>> invariable. Because I called mem_ok() to test, mem_ok() failed.
>>>>>>
>>>>>> On Monday, August 20, 2012 6:51:05 PM UTC+8, khasim wrote:
>>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>> We have released a preliminary version of JB release - Android 4.1.1
>>>>>>> for beagleboard and beaglebone platforms, the sources are now
>>>>>>> available on http://gitorious.org/rowboat
>>>>>>>
>>>>>>> Beaglebone is tested with ULCD7 cape board.
>>>>>>>
>>>>>>> Please find more details on these wikis,
>>>>>>>
>>>>>>> http://code.google.com/p/**rowboat/wiki/**
>>>>>>> JellybeanOnBeagleboard_WithSGX<http://code.google.com/p/rowboat/wiki/JellybeanOnBeagleboard_WithSGX>
>>>>>>> http://code.google.com/p/**rowboat/wiki/**
>>>>>>> JellybeanOnBeaglebone_WithSGX<http://code.google.com/p/rowboat/wiki/JellybeanOnBeaglebone_WithSGX>
>>>>>>>
>>>>>>> Thank you for all the support.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Khasim
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "rowboat" group.
>>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>>> **msg/rowboat/-/BW7_xrGDV74J<https://groups.google.com/d/msg/rowboat/-/BW7_xrGDV74J>
>>>>>> .
>>>>>> To post to this group, send email to [email protected].
>>>>>> To unsubscribe from this group, send email to
>>>>>> [email protected].
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group/rowboat?hl=en <http://groups.google.com/group/rowboat?hl=en>.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to