public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* Re: [ECOS] Memory Layout of Samsung SNDS.....??
@ 2003-11-06  9:05 RandyLin
  0 siblings, 0 replies; 7+ messages in thread
From: RandyLin @ 2003-11-06  9:05 UTC (permalink / raw)
  To: ecos-discuss


I notice a warning:
BFD:/redboot_snds_install/redboot.img:warning:allocated section '.bss' not
in segment
but still got redboot.bin redboot.elf redboot.img
I don't know how to fix it......
I use original source code to compile again, same warning
Is anyone use SNDS got same warning?



                                                                                                                    
                      Andrew Lunn                                                                                   
                      <andrew@lunn.ch>                   收件人: RandyLin@mxic.com.tw                              
                      寄件人:                           副本抄送:     ecos-discuss@sources.redhat.com             
                      ecos-discuss-owner@sources         主旨:   Re: [ECOS] Memory Layout of Samsung SNDS.....??   
                      .redhat.com                                                                                   
                                                                                                                    
                                                                                                                    
                      2003/11/04 05:43 PM                                                                           
                                                                                                                    
                                                                                                                    



On Tue, Nov 04, 2003 at 05:25:46PM +0800, RandyLin@mxic.com.tw wrote:
>
> I select Samsung SNDS template, and redboot package, then import
> redboot_rom.ecm

Thats sounds correct.

I would check what the call set_debug_comm is doing. Like i said
before, i think its a virtual vector problem. Maybe your configuration
is not causing these to be setup correctly.

I don't know the configuration options for this too well...

  Andrew

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss





^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Memory Layout of Samsung SNDS.....??
  2003-11-04  9:30 RandyLin
@ 2003-11-04  9:44 ` Andrew Lunn
  0 siblings, 0 replies; 7+ messages in thread
From: Andrew Lunn @ 2003-11-04  9:44 UTC (permalink / raw)
  To: RandyLin; +Cc: ecos-discuss

On Tue, Nov 04, 2003 at 05:25:46PM +0800, RandyLin@mxic.com.tw wrote:
> 
> I select Samsung SNDS template, and redboot package, then import
> redboot_rom.ecm

Thats sounds correct.

I would check what the call set_debug_comm is doing. Like i said
before, i think its a virtual vector problem. Maybe your configuration
is not causing these to be setup correctly.

I don't know the configuration options for this too well...

  Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Memory Layout of Samsung SNDS.....??
@ 2003-11-04  9:30 RandyLin
  2003-11-04  9:44 ` Andrew Lunn
  0 siblings, 1 reply; 7+ messages in thread
From: RandyLin @ 2003-11-04  9:30 UTC (permalink / raw)
  To: ecos-discuss


I select Samsung SNDS template, and redboot package, then import
redboot_rom.ecm
but I modify some registers value in hal_platform_setup.h, is this cause
the problem?
and I change rom from 0x1800000 to 0x2000000 at mlt_arm_snds_rom.h and
mlt_arm_snds_rom.ldi
and I use HAL_WRITE_UINT32(KS32C_IOPDATA, num) to tell where the program
stop.




                                                                                                          
                      Andrew Lunn                                                                         
                      <andrew@lunn.ch>         收件人: RandyLin@mxic.com.tw                              
                                               副本抄送:     ecos-discuss@sources.redhat.com             
                      2003/11/04 05:15         主旨:   Re: [ECOS] Memory Layout of Samsung SNDS.....??   
                      PM                                                                                  
                                                                                                          
                                                                                                          



On Tue, Nov 04, 2003 at 05:02:31PM +0800, RandyLin@mxic.com.tw wrote:
>
> Thanks for help!!
> I undo what i have done!
> PLATFORM_SETUP1 do the remap, right?
> program can run until hal_hardware_init
> program still hang at  set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
> any idea?

This is probably the first time its trying to use the virtual vectors.

What steps are you using to build your redboot image? Do you import
the .ecm file?

    Andrew




^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Memory Layout of Samsung SNDS.....??
  2003-11-04  9:05 RandyLin
@ 2003-11-04  9:15 ` Andrew Lunn
  0 siblings, 0 replies; 7+ messages in thread
From: Andrew Lunn @ 2003-11-04  9:15 UTC (permalink / raw)
  To: RandyLin; +Cc: ecos-discuss

On Tue, Nov 04, 2003 at 05:02:31PM +0800, RandyLin@mxic.com.tw wrote:
> 
> Thanks for help!!
> I undo what i have done!
> PLATFORM_SETUP1 do the remap, right?
> program can run until hal_hardware_init
> program still hang at  set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
> any idea?

This is probably the first time its trying to use the virtual vectors.

What steps are you using to build your redboot image? Do you import
the .ecm file?

    Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Memory Layout of Samsung SNDS.....??
@ 2003-11-04  9:05 RandyLin
  2003-11-04  9:15 ` Andrew Lunn
  0 siblings, 1 reply; 7+ messages in thread
From: RandyLin @ 2003-11-04  9:05 UTC (permalink / raw)
  To: ecos-discuss


Thanks for help!!
I undo what i have done!
PLATFORM_SETUP1 do the remap, right?
program can run until hal_hardware_init
program still hang at  set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
any idea?




                                                                                                          
                      Andrew Lunn                                                                         
                      <andrew@lunn.ch>         收件人: RandyLin@mxic.com.tw                              
                                               副本抄送:     ecos-discuss@sources.redhat.com             
                      2003/11/04 04:29         主旨:   Re: [ECOS] Memory Layout of Samsung SNDS.....??   
                      PM                                                                                  
                                                                                                          
                                                                                                          



On Tue, Nov 04, 2003 at 10:14:52AM +0800, RandyLin@mxic.com.tw wrote:
> I am working on customize board which base on Samsung SNDS.
> I try to port redboot on target, but I have some questions.....
> 1.
> In mlt_arm_snds_rom.ldi
> MEMORY
> {
>     ram : ORIGIN = 0, LENGTH = 0x1000000
>     rom : ORIGIN = 0x1800000, LENGTH = 0x80000
> }
> I am confused, why rom locate at 0x1800000? not 0x0?
> after arm reset, it run code from 0x0, right?

At boot time the ROM will be at 0x0 so that the reset vector is in the
ROM. But once the image is running, the ROM will be remapped to a
higher address and RAM mapped down to 0x0. You need to do this so that
you can change the vectors.

> 2.
> I assume the mlt_arm_snds_rom.ldi is not correct, so I modify:

Bad assumption.... A good way to work with eCos is assume its
correct. When it appears wrong, still assume its correct and try to
work out why it correct. Generally you are missing something which is
why you think its wrong.....

> MEMORY
> {
>     ram : ORIGIN = 0x2000000, LENGTH = 0x1000000
>     rom : ORIGIN = 0, LENGTH = 0x80000
> }
> SECTIONS
> {
>     SECTIONS_BEGIN
>     SECTION_rom_vectors (rom, 0, LMA_EQ_VMA)
>     SECTION_text (rom, ALIGN (0x1), LMA_EQ_VMA)
>     SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_fixed_vectors (ram, 0x2000020, LMA_EQ_VMA)
>     SECTION_data (ram, 0x2020000, FOLLOWING (.gcc_except_table))
>     SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
>     CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
>     SECTIONS_END
> }
> also modify mlt_arm_snds_rom.h, hal_platform_setup.h
> I burn into flash and see the LED lights,
> but program hang on set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
> any suggestion?

Undo what you have done!

     Andrew




^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Memory Layout of Samsung SNDS.....??
  2003-11-04  2:17 RandyLin
@ 2003-11-04  8:30 ` Andrew Lunn
  0 siblings, 0 replies; 7+ messages in thread
From: Andrew Lunn @ 2003-11-04  8:30 UTC (permalink / raw)
  To: RandyLin; +Cc: ecos-discuss

On Tue, Nov 04, 2003 at 10:14:52AM +0800, RandyLin@mxic.com.tw wrote:
> I am working on customize board which base on Samsung SNDS.
> I try to port redboot on target, but I have some questions.....
> 1.
> In mlt_arm_snds_rom.ldi
> MEMORY
> {
>     ram : ORIGIN = 0, LENGTH = 0x1000000
>     rom : ORIGIN = 0x1800000, LENGTH = 0x80000
> }
> I am confused, why rom locate at 0x1800000? not 0x0?
> after arm reset, it run code from 0x0, right?

At boot time the ROM will be at 0x0 so that the reset vector is in the
ROM. But once the image is running, the ROM will be remapped to a
higher address and RAM mapped down to 0x0. You need to do this so that
you can change the vectors.

> 2.
> I assume the mlt_arm_snds_rom.ldi is not correct, so I modify:

Bad assumption.... A good way to work with eCos is assume its
correct. When it appears wrong, still assume its correct and try to
work out why it correct. Generally you are missing something which is
why you think its wrong..... 

> MEMORY
> {
>     ram : ORIGIN = 0x2000000, LENGTH = 0x1000000
>     rom : ORIGIN = 0, LENGTH = 0x80000
> }
> SECTIONS
> {
>     SECTIONS_BEGIN
>     SECTION_rom_vectors (rom, 0, LMA_EQ_VMA)
>     SECTION_text (rom, ALIGN (0x1), LMA_EQ_VMA)
>     SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA)
>     SECTION_fixed_vectors (ram, 0x2000020, LMA_EQ_VMA)
>     SECTION_data (ram, 0x2020000, FOLLOWING (.gcc_except_table))
>     SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
>     CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
>     SECTIONS_END
> }
> also modify mlt_arm_snds_rom.h, hal_platform_setup.h
> I burn into flash and see the LED lights,
> but program hang on set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
> any suggestion?

Undo what you have done!

     Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [ECOS] Memory Layout of Samsung SNDS.....??
@ 2003-11-04  2:17 RandyLin
  2003-11-04  8:30 ` Andrew Lunn
  0 siblings, 1 reply; 7+ messages in thread
From: RandyLin @ 2003-11-04  2:17 UTC (permalink / raw)
  To: ecos-discuss

I am working on customize board which base on Samsung SNDS.
I try to port redboot on target, but I have some questions.....
1.
In mlt_arm_snds_rom.ldi
MEMORY
{
    ram : ORIGIN = 0, LENGTH = 0x1000000
    rom : ORIGIN = 0x1800000, LENGTH = 0x80000
}
I am confused, why rom locate at 0x1800000? not 0x0?
after arm reset, it run code from 0x0, right?
can anyone explain this for me?

2.
I assume the mlt_arm_snds_rom.ldi is not correct, so I modify:
MEMORY
{
    ram : ORIGIN = 0x2000000, LENGTH = 0x1000000
    rom : ORIGIN = 0, LENGTH = 0x80000
}
SECTIONS
{
    SECTIONS_BEGIN
    SECTION_rom_vectors (rom, 0, LMA_EQ_VMA)
    SECTION_text (rom, ALIGN (0x1), LMA_EQ_VMA)
    SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA)
    SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA)
    SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA)
    SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA)
    SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA)
    SECTION_fixed_vectors (ram, 0x2000020, LMA_EQ_VMA)
    SECTION_data (ram, 0x2020000, FOLLOWING (.gcc_except_table))
    SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
    CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
    SECTIONS_END
}
also modify mlt_arm_snds_rom.h, hal_platform_setup.h
I burn into flash and see the LED lights,
but program hang on set_debug_comm(CYGNUM_CALL_IF_SET_COMM_ID_EMPTY);
any suggestion?
thanks!



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2003-11-06  9:05 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-06  9:05 [ECOS] Memory Layout of Samsung SNDS.....?? RandyLin
  -- strict thread matches above, loose matches on Subject: below --
2003-11-04  9:30 RandyLin
2003-11-04  9:44 ` Andrew Lunn
2003-11-04  9:05 RandyLin
2003-11-04  9:15 ` Andrew Lunn
2003-11-04  2:17 RandyLin
2003-11-04  8:30 ` Andrew Lunn

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).