* changes for reducing DDR size
@ 2010-08-13 15:17 kuldeep ghan
2010-08-16 9:13 ` Sascha Hauer
0 siblings, 1 reply; 5+ messages in thread
From: kuldeep ghan @ 2010-08-13 15:17 UTC (permalink / raw)
To: barebox
[-- Attachment #1.1: Type: text/plain, Size: 575 bytes --]
Hi,
I am using PCM038 based custom board with changes in Memory
configuration. I want to know what all changes i have to do in barebox
source if I am reducing the size of DDR to 64 MB.
I have two 32MB DDR chips interfaced on CSD0 and CSD1. I am able to boot the
board with changes in pcm038 and lowlevel_init.S. I see that both the DDRs
are initialized properly and able to write and read to DDR address space.
Ping to command is failing with these changes. And I am not sure
about the changes required for stack size and malloc size.
Thanks,
Ghan Kuldeep
[-- Attachment #1.2: Type: text/html, Size: 677 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: changes for reducing DDR size
2010-08-13 15:17 changes for reducing DDR size kuldeep ghan
@ 2010-08-16 9:13 ` Sascha Hauer
2010-08-16 13:44 ` kuldeep ghan
0 siblings, 1 reply; 5+ messages in thread
From: Sascha Hauer @ 2010-08-16 9:13 UTC (permalink / raw)
To: kuldeep ghan; +Cc: barebox
Hi,
On Fri, Aug 13, 2010 at 08:47:38PM +0530, kuldeep ghan wrote:
> Hi,
> I am using PCM038 based custom board with changes in Memory
> configuration. I want to know what all changes i have to do in barebox
> source if I am reducing the size of DDR to 64 MB.
> I have two 32MB DDR chips interfaced on CSD0 and CSD1. I am able to boot the
> board with changes in pcm038 and lowlevel_init.S. I see that both the DDRs
> are initialized properly and able to write and read to DDR address space.
> Ping to command is failing with these changes. And I am not sure
> about the changes required for stack size and malloc size.
You have to adjust the TEXT_BASE in arch/arm/mach-imx/Kconfig so that the
resulting link address is is your address space. This should be
sufficient for barebox. For Linux you have to adjust the device size of
the device which is passed to armlinux_add_dram() to 64MB.
I hope this helps
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: changes for reducing DDR size
2010-08-16 9:13 ` Sascha Hauer
@ 2010-08-16 13:44 ` kuldeep ghan
2010-08-23 7:16 ` Juergen Beisert
0 siblings, 1 reply; 5+ messages in thread
From: kuldeep ghan @ 2010-08-16 13:44 UTC (permalink / raw)
To: Sascha Hauer; +Cc: barebox
[-- Attachment #1.1: Type: text/plain, Size: 3258 bytes --]
Hi Sascha,
>> You have to adjust the TEXT_BASE in arch/arm/mach-imx/Kconfig so that
the
resulting link address is is your address space.
I have changed the TEXT_BASE to 0xA1F000000. Now it is pointing to
31st MB of 1st chip select. I did not understand what do you mean by "
resulting
link address is your address space " ?
According to TEXT_BASE at 0xA1F000000, i have following stack and malloc
area's
Malloc space: 0xa1900000 -> 0xa1f00000 (size 6 MB)
Stack space : 0xa18f8000 -> 0xa1900000 (size 32 kB)
>> For Linux you have to adjust the device size of the device which is
passed to armlinux_add_dram() to 64MB.
I am adding two device using armlinux_add_dram() each with 32MB size and
map_base address of 0xA0000000 and 0xB0000000 respectively.. Is that fine or
Can I have one device registered with map_base address of 0xA0000000 and
64MB size??
I have enabled MMU in barebox. There also i have a change for
arm_create_section(). Following is section of code i have in
pcm038_mmu_init()
*static void pcm038_mmu_init(void)
{
mmu_init();
arm_create_section(0xa0000000, 0xa0000000, 32, PMD_SECT_DEF_CACHED);
arm_create_section(0xb0000000, 0xa0000000, 32,
PMD_SECT_DEF_UNCACHED);
setup_dma_coherent(0x10000000);
#if TEXT_BASE & (0x100000 - 1)
#warning cannot create vector section. Adjust TEXT_BASE to a 1M boundary
#else
arm_create_section(0x0, TEXT_BASE, 1,
PMD_SECT_DEF_UNCACHED);
#endif
mmu_enable();
}*
With all these changes, I see ping command hangs.. :(
If I replace the macro from PMD_SECT_DEF_UNCACHED to PMD_SECT_DEF_CACHED
in the function pcm038_mmu_init(), the ping command throws some
transmission timeout messages and exits saying the the destination is not
Alive.
It would be great if you can help me out!!
Thanks,
Kuldeep.
On Mon, Aug 16, 2010 at 2:43 PM, Sascha Hauer <s.hauer@pengutronix.de>wrote:
>
> Hi,
>
> On Fri, Aug 13, 2010 at 08:47:38PM +0530, kuldeep ghan wrote:
> > Hi,
> > I am using PCM038 based custom board with changes in Memory
> > configuration. I want to know what all changes i have to do in barebox
> > source if I am reducing the size of DDR to 64 MB.
> > I have two 32MB DDR chips interfaced on CSD0 and CSD1. I am able to boot
> the
> > board with changes in pcm038 and lowlevel_init.S. I see that both the
> DDRs
> > are initialized properly and able to write and read to DDR address space.
> > Ping to command is failing with these changes. And I am not
> sure
> > about the changes required for stack size and malloc size.
>
> You have to adjust the TEXT_BASE in arch/arm/mach-imx/Kconfig so that the
> resulting link address is is your address space. This should be
> sufficient for barebox. For Linux you have to adjust the device size of
> the device which is passed to armlinux_add_dram() to 64MB.
>
> I hope this helps
>
> Sascha
>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
[-- Attachment #1.2: Type: text/html, Size: 4045 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: changes for reducing DDR size
2010-08-16 13:44 ` kuldeep ghan
@ 2010-08-23 7:16 ` Juergen Beisert
2010-09-17 8:47 ` kuldeep ghan
0 siblings, 1 reply; 5+ messages in thread
From: Juergen Beisert @ 2010-08-23 7:16 UTC (permalink / raw)
To: barebox
kuldeep ghan wrote:
> [...]
> I am adding two device using armlinux_add_dram() each with 32MB size and
> map_base address of 0xA0000000 and 0xB0000000 respectively.. Is that fine
> or Can I have one device registered with map_base address of 0xA0000000 and
> 64MB size??
You are using non continuous memory. I'm not sure, if that is handled in
barebox correctly. Also Linux may have a problem with this kind of memory
organization.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-8766-939 228 |
Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: changes for reducing DDR size
2010-08-23 7:16 ` Juergen Beisert
@ 2010-09-17 8:47 ` kuldeep ghan
0 siblings, 0 replies; 5+ messages in thread
From: kuldeep ghan @ 2010-09-17 8:47 UTC (permalink / raw)
To: Juergen Beisert; +Cc: barebox
[-- Attachment #1.1: Type: text/plain, Size: 1354 bytes --]
Yes I am using Non continuous memory. I have two variants of the boards. On
one type of board. I use two DDRs of 128MB each on CSD0 and CSD1. In that
case it works, also I see Linux utilizing 256MB memory.
On board with 32MB DDRs on CSD0 and CSD1 each, I see that ping commands
calls fec_send in fec_imx.c (FEC driver for imx27) and after enabling dma it
hangs.
Is there any change required for initiazation of DMA due change id DDR size
from 128MB to 32 MB on each chipselect CSD0 and CSD1.
On Mon, Aug 23, 2010 at 12:46 PM, Juergen Beisert <jbe@pengutronix.de>wrote:
> kuldeep ghan wrote:
> > [...]
> > I am adding two device using armlinux_add_dram() each with 32MB size and
> > map_base address of 0xA0000000 and 0xB0000000 respectively.. Is that fine
> > or Can I have one device registered with map_base address of 0xA0000000
> and
> > 64MB size??
>
> You are using non continuous memory. I'm not sure, if that is handled in
> barebox correctly. Also Linux may have a problem with this kind of memory
> organization.
>
> jbe
>
> --
> Pengutronix e.K. | Juergen Beisert
> |
> Linux Solutions for Science and Industry | Phone: +49-8766-939 228
> |
> Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555
> |
> Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
>
[-- Attachment #1.2: Type: text/html, Size: 1818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-09-17 8:47 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-13 15:17 changes for reducing DDR size kuldeep ghan
2010-08-16 9:13 ` Sascha Hauer
2010-08-16 13:44 ` kuldeep ghan
2010-08-23 7:16 ` Juergen Beisert
2010-09-17 8:47 ` kuldeep ghan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox