* RE: [ECOS] How to handle it???
@ 2003-12-04 5:50 RandyLin
0 siblings, 0 replies; 12+ messages in thread
From: RandyLin @ 2003-12-04 5:50 UTC (permalink / raw)
To: ecos-discuss; +Cc: wj_zheng10
hi,
In redboot, it's ok without the CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
but in ap, it should be defined.
I compile the ap with package "default",
I don't know what you select when compile?
attache file is my screenshot, u can see the
CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
and "Work with a ROM monitor" is enabled.
if u didn't add cdl_option CYGSEM_HAL_USE_ROM_MONITOR in hal_arm_snds.cdl
you can't see it.
oh, I add the cdl_option blow cdl_option CYGSEM_HAL_ROM_MONITOR
Good Luck!
I checked out and findthere is no CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
macro define in my hal.hXXXX_install/include/pkgconf/hal.h. why?
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
2003-12-04 20:45 RandyLin
@ 2003-12-04 20:50 ` Gary Thomas
0 siblings, 0 replies; 12+ messages in thread
From: Gary Thomas @ 2003-12-04 20:50 UTC (permalink / raw)
To: RandyLin; +Cc: ecos-discuss, wj_zheng10
On Wed, 2003-12-03 at 20:32, RandyLin@mxic.com.tw wrote:
> Can you check your project directory XXXX_install/include/pkgconf/hal.h
> There should be
> =======================
> #define CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE 1
> =======================
> if not, maybe that's the problem.
> I think your output is encode by mangler.
> and gdb know the format, and works fine.
> but hyperteminal know nothing about it, so ugly string output.
>
This has nothing to do with his problem. He's getting these GDB
strings because he's trying to execute code which was either loaded
into the wrong location or isn't code at all. I've already explained
both cases - "zheng wujun" (I don't know which is the family name,
sorry) needs to adjust the memory map for the SNDS platform as
obviously there is a clash between the RAM application and RedBoot.
>
>
>
> "zheng wujun"
> <wj_zheng10@hotmail.com> 收件人： RandyLin@mxic.com.tw
> 寄件人： 副本抄é€ï¼š ecos-discuss@sources.redhat.com
> ecos-discuss-owner@sources 主旨： RE: [ECOS] How to handle it???
> .redhat.com
>
>
> 2003/12/04 11:10 AM
>
>
>
>
>
>
>
>
> >From: RandyLin@mxic.com.tw
> >To: ecos-discuss@sources.redhat.com
> >CC: wj_zheng10@hotmail.com
> >Subject: RE: [ECOS] How to handle it???
> >Date: Wed, 3 Dec 2003 17:16:43 +0800
> >
> >
> >It's nice to hear that you can use gdb to run the ap:)
> >your mlt_arm_snds_ram.ldi and mlt_arm_snds_rom.ldi seems fine.
> >I add the following to hal_arm_snds.cdl, copy from hal_arm_at91.cdl
> >==================================
> >+ cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
> >+ display "Work with a ROM monitor"
> >+ flavor booldata
> >+ legal_values { "Generic" "GDB_stubs" }
> >+ default_value { CYG_HAL_STARTUP == "RAM" ? "GDB_stubs" : 0 }
> >+ parent CYGPKG_HAL_ROM_MONITOR
> >+ requires { CYG_HAL_STARTUP == "RAM" }
> >+ description "
> >+ Support can be enabled for different varieties of ROM
> >monitor.
> >+ This support changes various eCos semantics such as the
> >encoding
> >+ of diagnostic output, or the overriding of hardware
> interrupt
> >+ vectors.
> >+ Firstly there is \"Generic\" support which prevents the HAL
> >+ from overriding the hardware vectors that it does not use,
> to
> >+ instead allow an installed ROM monitor to handle them. This
> >is
> >+ the most basic support which is likely to be common to most
> >+ implementations of ROM monitor.
> >+ \"GDB_stubs\" provides support when GDB stubs are included
> in
> >+ the ROM monitor or boot ROM."
> >+ }
> >====================================
> >and add the following to redboot_ROM.ecm,
> >========================
> >+cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
> >+ inferred_value 0 0
> >+};
> >========================
> >maybe you should recompile the redboot[ROM], and ap[RAM]
> >then try again,good luck....^^
> >
> >
> >
> >Thanks RandyLin:
> >
> >here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want to
> >see:
> >
> >mlt_arm_snds_ram.ldi:
> >
> >#include <cyg/infra/cyg_type.inc>
> >
> >MEMORY
> >{
> > ram : ORIGIN = 0x000000, LENGTH = 0x01000000
> >}
> >
> >SECTIONS
> >{
> > SECTIONS_BEGIN
> > SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> > SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
> > SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> > CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> > SECTIONS_END
> >}
> >
> >and mlt_arm_snds_rom.ldi:
> >
> >#include <cyg/infra/cyg_type.inc>
> >
> >MEMORY
> >{
> > ram : ORIGIN = 0, LENGTH = 0x1000000
> > rom : ORIGIN = 0x1800000, LENGTH = 0x80000
> >}
> >
> >SECTIONS
> >{
> > SECTIONS_BEGIN
> > SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
> > SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
> > SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> > CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> > SECTIONS_END
> >}
> >
> >I did as you said(Only modified ROM and RAM config as above ),and using
> GDB
> >
> >can load app and app works perfectly fine.But when loading app using
> >redboot
> >commands "load -m xmodem"("load -m tftp" is same),and using "go" to
> execute
> >
> >app,redboot still will display strange string as
> >
> >"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> >#17$T0a0f:86000000;0d:80060"
> >
> >Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
> >hal_arm_snds.cdl,the result were same.What is your detail steps in your
> >successful executing app under redboot commands?
> >
> >Thanks lot!
> >
> >zheng
> >
> >
> >
> >
> > >From: RandyLin@mxic.com.tw
> > >To: ecos-discuss@sources.redhat.com
> > >CC: wj_zheng10@hotmail.com
> > >Subject: [ECOS] How to handle it???
> > >Date: Wed, 3 Dec 2003 10:05:08 +0800
> > >
> > >
> > >Can you use "load -m ymodem" or "load -m xmodem" to load ap??
> > >I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
> > >wrong...
> > >I assume your redboot is ROM mode, so redboot's data section is at
> >0x20000
> > >when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
> > >data section,
> > >because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
> > >section to 0x20000
> > >so that's why u got the "Ignoring packet error, continuing..",
> > >I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
> > >mlt_arm_snds_ram.ldi
> > >"-r" option is for binary data, your ap is elf format, don't use "-r"
> > >can u post the whole mlt_arm_snds_rom.ldi?
> > >I don't know why you got the message "0x20000 which is not in RAM"
> > >wish this help.
> > >
> > >
> > >
> > >
> > >Thanks RandyLin:
> > > Now my redboot can work,and I can use redboot command "load
> > >......-m
> > >
> > >tftp....."to download app to snds board.
> > > Howerer, if not using -r option,the error as displayed "
> ***Abort!
> > >Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> > > If using -r option,app looks like to be downloaded
> correctly,but
> > >the
> > >display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> > >0x00300000",and then if using redboot command "go 0x00300000" to
> execute
> > >the app,the redboot will display some strange strings as
> > >"
> > >$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> > >#17$T0a0f:8600"on
> > >console.
> > >
> > >to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> >and
> > >SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
> >mlt_arm_snds_ram.ldi
> > >
> > >and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
> >(ram,
> > >
> > >0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
> > >
> > >If using arm-elf-gdb to download app,the steps is as following:
> > >1 [root@zheng root]#arm-elf-gdb
> > >2(gdb) target remote /dev/ttyS0
> > >Remote debugging using /dev/ttyS0
> > >0x01804b30 in ?? ()
> > >(gdb) load /tftpboot/hello
> > >Loading section .rom_vectors, size 0x40 lma 0x20000
> > >Loading section .text, size 0xfe00 lma 0x20040
> > >Ignoring packet error, continuing...
> > >Ignoring packet error, continuing...
> > >Ignoring packet error, continuing...
> > >
> > >and gdb use the same serial line as the hyperspatial,the baudrate is
> >38400.
> > >
> > >
> > >Why did these error happen?Can some one have good idea to handle it?
> > >
> > >Thanks a lot!
> > >
> > >_________________________________________________________________
> > >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > >http://join.msn.com/?page=features/junkmail
> > >
> > >
> > >--
> > >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> > >
> > >
> > >
> > >
> > >
> > >
> hi,RandyLin:
> I don't know if you had done some other steps or made some other
> modification,but I did as what you had said,it seems no use.why?
>
> Thanks lot!
>
> zheng
>
> > >
> > >--
> > >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> > >
> >
> >_________________________________________________________________
> >Winterize your home with tips from MSN House & Home.
> >http://special.msn.com/home/warmhome.armx
> >
> >
> >
> >
> >
> >
>
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-04 20:45 RandyLin
2003-12-04 20:50 ` Gary Thomas
0 siblings, 1 reply; 12+ messages in thread
From: RandyLin @ 2003-12-04 20:45 UTC (permalink / raw)
To: ecos-discuss; +Cc: wj_zheng10
Can you check your project directory XXXX_install/include/pkgconf/hal.h
There should be
=======================
#define CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE 1
=======================
if not, maybe that's the problem.
I think your output is encode by mangler.
and gdb know the format, and works fine.
but hyperteminal know nothing about it, so ugly string output.
"zheng wujun"
<wj_zheng10@hotmail.com> 收件人： RandyLin@mxic.com.tw
寄件人： 副本抄送： ecos-discuss@sources.redhat.com
ecos-discuss-owner@sources 主旨： RE: [ECOS] How to handle it???
.redhat.com
2003/12/04 11:10 AM
>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>CC: wj_zheng10@hotmail.com
>Subject: RE: [ECOS] How to handle it???
>Date: Wed, 3 Dec 2003 17:16:43 +0800
>
>
>It's nice to hear that you can use gdb to run the ap:)
>your mlt_arm_snds_ram.ldi and mlt_arm_snds_rom.ldi seems fine.
>I add the following to hal_arm_snds.cdl, copy from hal_arm_at91.cdl
>==================================
>+ cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
>+ display "Work with a ROM monitor"
>+ flavor booldata
>+ legal_values { "Generic" "GDB_stubs" }
>+ default_value { CYG_HAL_STARTUP == "RAM" ? "GDB_stubs" : 0 }
>+ parent CYGPKG_HAL_ROM_MONITOR
>+ requires { CYG_HAL_STARTUP == "RAM" }
>+ description "
>+ Support can be enabled for different varieties of ROM
>monitor.
>+ This support changes various eCos semantics such as the
>encoding
>+ of diagnostic output, or the overriding of hardware
interrupt
>+ vectors.
>+ Firstly there is \"Generic\" support which prevents the HAL
>+ from overriding the hardware vectors that it does not use,
to
>+ instead allow an installed ROM monitor to handle them. This
>is
>+ the most basic support which is likely to be common to most
>+ implementations of ROM monitor.
>+ \"GDB_stubs\" provides support when GDB stubs are included
in
>+ the ROM monitor or boot ROM."
>+ }
>====================================
>and add the following to redboot_ROM.ecm,
>========================
>+cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
>+ inferred_value 0 0
>+};
>========================
>maybe you should recompile the redboot[ROM], and ap[RAM]
>then try again,good luck....^^
>
>
>
>Thanks RandyLin:
>
>here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want to
>see:
>
>mlt_arm_snds_ram.ldi:
>
>#include <cyg/infra/cyg_type.inc>
>
>MEMORY
>{
> ram : ORIGIN = 0x000000, LENGTH = 0x01000000
>}
>
>SECTIONS
>{
> SECTIONS_BEGIN
> SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
> SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> SECTIONS_END
>}
>
>and mlt_arm_snds_rom.ldi:
>
>#include <cyg/infra/cyg_type.inc>
>
>MEMORY
>{
> ram : ORIGIN = 0, LENGTH = 0x1000000
> rom : ORIGIN = 0x1800000, LENGTH = 0x80000
>}
>
>SECTIONS
>{
> SECTIONS_BEGIN
> SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
> SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
> SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> SECTIONS_END
>}
>
>I did as you said(Only modified ROM and RAM config as above ),and using
GDB
>
>can load app and app works perfectly fine.But when loading app using
>redboot
>commands "load -m xmodem"("load -m tftp" is same),and using "go" to
execute
>
>app,redboot still will display strange string as
>
>"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
>#17$T0a0f:86000000;0d:80060"
>
>Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
>hal_arm_snds.cdl,the result were same.What is your detail steps in your
>successful executing app under redboot commands?
>
>Thanks lot!
>
>zheng
>
>
>
>
> >From: RandyLin@mxic.com.tw
> >To: ecos-discuss@sources.redhat.com
> >CC: wj_zheng10@hotmail.com
> >Subject: [ECOS] How to handle it???
> >Date: Wed, 3 Dec 2003 10:05:08 +0800
> >
> >
> >Can you use "load -m ymodem" or "load -m xmodem" to load ap??
> >I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
> >wrong...
> >I assume your redboot is ROM mode, so redboot's data section is at
>0x20000
> >when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
> >data section,
> >because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
> >section to 0x20000
> >so that's why u got the "Ignoring packet error, continuing..",
> >I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
> >mlt_arm_snds_ram.ldi
> >"-r" option is for binary data, your ap is elf format, don't use "-r"
> >can u post the whole mlt_arm_snds_rom.ldi?
> >I don't know why you got the message "0x20000 which is not in RAM"
> >wish this help.
> >
> >
> >
> >
> >Thanks RandyLin:
> > Now my redboot can work,and I can use redboot command "load
> >......-m
> >
> >tftp....."to download app to snds board.
> > Howerer, if not using -r option,the error as displayed "
***Abort!
> >Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> > If using -r option,app looks like to be downloaded
correctly,but
> >the
> >display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> >0x00300000",and then if using redboot command "go 0x00300000" to
execute
> >the app,the redboot will display some strange strings as
> >"
> >$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> >#17$T0a0f:8600"on
> >console.
> >
> >to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
>and
> >SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
>mlt_arm_snds_ram.ldi
> >
> >and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
>(ram,
> >
> >0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
> >
> >If using arm-elf-gdb to download app,the steps is as following:
> >1 [root@zheng root]#arm-elf-gdb
> >2(gdb) target remote /dev/ttyS0
> >Remote debugging using /dev/ttyS0
> >0x01804b30 in ?? ()
> >(gdb) load /tftpboot/hello
> >Loading section .rom_vectors, size 0x40 lma 0x20000
> >Loading section .text, size 0xfe00 lma 0x20040
> >Ignoring packet error, continuing...
> >Ignoring packet error, continuing...
> >Ignoring packet error, continuing...
> >
> >and gdb use the same serial line as the hyperspatial,the baudrate is
>38400.
> >
> >
> >Why did these error happen?Can some one have good idea to handle it?
> >
> >Thanks a lot!
> >
> >_________________________________________________________________
> >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> >http://join.msn.com/?page=features/junkmail
> >
> >
> >--
> >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
> >
> >
> >
> >
> >
hi,RandyLin:
I don't know if you had done some other steps or made some other
modification,but I did as what you had said,it seems no use.why?
Thanks lot!
zheng
> >
> >--
> >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
>
>_________________________________________________________________
>Winterize your home with tips from MSN House & Home.
>http://special.msn.com/home/warmhome.armx
>
>
>
>
>
>
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-04 5:55 RandyLin
0 siblings, 0 replies; 12+ messages in thread
From: RandyLin @ 2003-12-04 5:55 UTC (permalink / raw)
To: ecos-discuss; +Cc: wj_zheng10
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
sorry, I forgot the attache file
(See attached file: mysnds.png)
RandyLin@mxic.com.tw
寄件人： 收件人： ecos-discuss@sources.redhat.com
ecos-discuss-owner@sources 副本抄送： wj_zheng10@hotmail.com
.redhat.com 主旨： RE: [ECOS] How to handle it???
2003/12/04 01:47 PM
hi,
In redboot, it's ok without the CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
but in ap, it should be defined.
I compile the ap with package "default",
I don't know what you select when compile?
attache file is my screenshot, u can see the
CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
and "Work with a ROM monitor" is enabled.
if u didn't add cdl_option CYGSEM_HAL_USE_ROM_MONITOR in hal_arm_snds.cdl
you can't see it.
oh, I add the cdl_option blow cdl_option CYGSEM_HAL_ROM_MONITOR
Good Luck!
I checked out and findthere is no CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
macro define in my hal.hXXXX_install/include/pkgconf/hal.h. why?
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
[-- Attachment #2: mysnds.png --]
[-- Type: image/png, Size: 57441 bytes --]
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-04 4:43 zheng wujun
0 siblings, 0 replies; 12+ messages in thread
From: zheng wujun @ 2003-12-04 4:43 UTC (permalink / raw)
To: RandyLin; +Cc: ecos-discuss
I checked out and findthere is no CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE
macro define in my hal.hXXXX_install/include/pkgconf/hal.h. why?
>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>CC: wj_zheng10@hotmail.com
>Subject: RE: [ECOS] How to handle it???
>Date: Thu, 4 Dec 2003 11:32:48 +0800
>
>
>Can you check your project directory XXXX_install/include/pkgconf/hal.h
>There should be
>=======================
>#define CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE 1
>=======================
>if not, maybe that's the problem.
>I think your output is encode by mangler.
>and gdb know the format, and works fine.
>but hyperteminal know nothing about it, so ugly string output.
>
>
>
>
> "zheng wujun"
> <wj_zheng10@hotmail.com> ¦¬¥ó¤H¡G
>RandyLin@mxic.com.tw
> ±H¥ó¤H¡G °Æ¥»§Û°e¡G
>ecos-discuss@sources.redhat.com
> ecos-discuss-owner@sources ¥D¦®¡G RE:
>[ECOS] How to handle it???
> .redhat.com
>
>
> 2003/12/04 11:10 AM
>
>
>
>
>
>
>
>
> >From: RandyLin@mxic.com.tw
> >To: ecos-discuss@sources.redhat.com
> >CC: wj_zheng10@hotmail.com
> >Subject: RE: [ECOS] How to handle it???
> >Date: Wed, 3 Dec 2003 17:16:43 +0800
> >
> >
> >It's nice to hear that you can use gdb to run the ap:)
> >your mlt_arm_snds_ram.ldi and mlt_arm_snds_rom.ldi seems fine.
> >I add the following to hal_arm_snds.cdl, copy from hal_arm_at91.cdl
> >==================================
> >+ cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
> >+ display "Work with a ROM monitor"
> >+ flavor booldata
> >+ legal_values { "Generic" "GDB_stubs" }
> >+ default_value { CYG_HAL_STARTUP == "RAM" ? "GDB_stubs" : 0 }
> >+ parent CYGPKG_HAL_ROM_MONITOR
> >+ requires { CYG_HAL_STARTUP == "RAM" }
> >+ description "
> >+ Support can be enabled for different varieties of ROM
> >monitor.
> >+ This support changes various eCos semantics such as the
> >encoding
> >+ of diagnostic output, or the overriding of hardware
>interrupt
> >+ vectors.
> >+ Firstly there is \"Generic\" support which prevents the HAL
> >+ from overriding the hardware vectors that it does not use,
>to
> >+ instead allow an installed ROM monitor to handle them. This
> >is
> >+ the most basic support which is likely to be common to most
> >+ implementations of ROM monitor.
> >+ \"GDB_stubs\" provides support when GDB stubs are included
>in
> >+ the ROM monitor or boot ROM."
> >+ }
> >====================================
> >and add the following to redboot_ROM.ecm,
> >========================
> >+cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
> >+ inferred_value 0 0
> >+};
> >========================
> >maybe you should recompile the redboot[ROM], and ap[RAM]
> >then try again,good luck....^^
> >
> >
> >
> >Thanks RandyLin:
> >
> >here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want
>to
> >see:
> >
> >mlt_arm_snds_ram.ldi:
> >
> >#include <cyg/infra/cyg_type.inc>
> >
> >MEMORY
> >{
> > ram : ORIGIN = 0x000000, LENGTH = 0x01000000
> >}
> >
> >SECTIONS
> >{
> > SECTIONS_BEGIN
> > SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> > SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
> > SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
> > SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> > CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> > SECTIONS_END
> >}
> >
> >and mlt_arm_snds_rom.ldi:
> >
> >#include <cyg/infra/cyg_type.inc>
> >
> >MEMORY
> >{
> > ram : ORIGIN = 0, LENGTH = 0x1000000
> > rom : ORIGIN = 0x1800000, LENGTH = 0x80000
> >}
> >
> >SECTIONS
> >{
> > SECTIONS_BEGIN
> > SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
> > SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
> > SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> > CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> > SECTIONS_END
> >}
> >
> >I did as you said(Only modified ROM and RAM config as above ),and using
>GDB
> >
> >can load app and app works perfectly fine.But when loading app using
> >redboot
> >commands "load -m xmodem"("load -m tftp" is same),and using "go" to
>execute
> >
> >app,redboot still will display strange string as
> >
> >"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> >#17$T0a0f:86000000;0d:80060"
> >
> >Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
> >hal_arm_snds.cdl,the result were same.What is your detail steps in your
> >successful executing app under redboot commands?
> >
> >Thanks lot!
> >
> >zheng
> >
> >
> >
> >
> > >From: RandyLin@mxic.com.tw
> > >To: ecos-discuss@sources.redhat.com
> > >CC: wj_zheng10@hotmail.com
> > >Subject: [ECOS] How to handle it???
> > >Date: Wed, 3 Dec 2003 10:05:08 +0800
> > >
> > >
> > >Can you use "load -m ymodem" or "load -m xmodem" to load ap??
> > >I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
> > >wrong...
> > >I assume your redboot is ROM mode, so redboot's data section is at
> >0x20000
> > >when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
> > >data section,
> > >because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
> > >section to 0x20000
> > >so that's why u got the "Ignoring packet error, continuing..",
> > >I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
> > >mlt_arm_snds_ram.ldi
> > >"-r" option is for binary data, your ap is elf format, don't use "-r"
> > >can u post the whole mlt_arm_snds_rom.ldi?
> > >I don't know why you got the message "0x20000 which is not in RAM"
> > >wish this help.
> > >
> > >
> > >
> > >
> > >Thanks RandyLin:
> > > Now my redboot can work,and I can use redboot command "load
> > >......-m
> > >
> > >tftp....."to download app to snds board.
> > > Howerer, if not using -r option,the error as displayed "
>***Abort!
> > >Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> > > If using -r option,app looks like to be downloaded
>correctly,but
> > >the
> > >display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> > >0x00300000",and then if using redboot command "go 0x00300000" to
>execute
> > >the app,the redboot will display some strange strings as
> > >"
> > >$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> > >#17$T0a0f:8600"on
> > >console.
> > >
> > >to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> >and
> > >SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
> >mlt_arm_snds_ram.ldi
> > >
> > >and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
> >(ram,
> > >
> > >0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
> > >
> > >If using arm-elf-gdb to download app,the steps is as following:
> > >1 [root@zheng root]#arm-elf-gdb
> > >2(gdb) target remote /dev/ttyS0
> > >Remote debugging using /dev/ttyS0
> > >0x01804b30 in ?? ()
> > >(gdb) load /tftpboot/hello
> > >Loading section .rom_vectors, size 0x40 lma 0x20000
> > >Loading section .text, size 0xfe00 lma 0x20040
> > >Ignoring packet error, continuing...
> > >Ignoring packet error, continuing...
> > >Ignoring packet error, continuing...
> > >
> > >and gdb use the same serial line as the hyperspatial,the baudrate is
> >38400.
> > >
> > >
> > >Why did these error happen?Can some one have good idea to handle it?
> > >
> > >Thanks a lot!
> > >
> > >_________________________________________________________________
> > >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > >http://join.msn.com/?page=features/junkmail
> > >
> > >
> > >--
> > >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> > >
> > >
> > >
> > >
> > >
> > >
>hi,RandyLin:
>I don't know if you had done some other steps or made some other
>modification,but I did as what you had said,it seems no use.why?
>
>Thanks lot!
>
>zheng
>
> > >
> > >--
> > >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> > >
> >
> >_________________________________________________________________
> >Winterize your home with tips from MSN House & Home.
> >http://special.msn.com/home/warmhome.armx
> >
> >
> >
> >
> >
> >
>
>_________________________________________________________________
>The new MSN 8: smart spam protection and 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>
>
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-04 3:10 zheng wujun
0 siblings, 0 replies; 12+ messages in thread
From: zheng wujun @ 2003-12-04 3:10 UTC (permalink / raw)
To: RandyLin; +Cc: ecos-discuss
>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>CC: wj_zheng10@hotmail.com
>Subject: RE: [ECOS] How to handle it???
>Date: Wed, 3 Dec 2003 17:16:43 +0800
>
>
>It's nice to hear that you can use gdb to run the ap:)
>your mlt_arm_snds_ram.ldi and mlt_arm_snds_rom.ldi seems fine.
>I add the following to hal_arm_snds.cdl, copy from hal_arm_at91.cdl
>==================================
>+ cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
>+ display "Work with a ROM monitor"
>+ flavor booldata
>+ legal_values { "Generic" "GDB_stubs" }
>+ default_value { CYG_HAL_STARTUP == "RAM" ? "GDB_stubs" : 0 }
>+ parent CYGPKG_HAL_ROM_MONITOR
>+ requires { CYG_HAL_STARTUP == "RAM" }
>+ description "
>+ Support can be enabled for different varieties of ROM
>monitor.
>+ This support changes various eCos semantics such as the
>encoding
>+ of diagnostic output, or the overriding of hardware interrupt
>+ vectors.
>+ Firstly there is \"Generic\" support which prevents the HAL
>+ from overriding the hardware vectors that it does not use, to
>+ instead allow an installed ROM monitor to handle them. This
>is
>+ the most basic support which is likely to be common to most
>+ implementations of ROM monitor.
>+ \"GDB_stubs\" provides support when GDB stubs are included in
>+ the ROM monitor or boot ROM."
>+ }
>====================================
>and add the following to redboot_ROM.ecm,
>========================
>+cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
>+ inferred_value 0 0
>+};
>========================
>maybe you should recompile the redboot[ROM], and ap[RAM]
>then try again,good luck....^^
>
>
>
>Thanks RandyLin:
>
>here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want to
>see:
>
>mlt_arm_snds_ram.ldi:
>
>#include <cyg/infra/cyg_type.inc>
>
>MEMORY
>{
> ram : ORIGIN = 0x000000, LENGTH = 0x01000000
>}
>
>SECTIONS
>{
> SECTIONS_BEGIN
> SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
> SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
> SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> SECTIONS_END
>}
>
>and mlt_arm_snds_rom.ldi:
>
>#include <cyg/infra/cyg_type.inc>
>
>MEMORY
>{
> ram : ORIGIN = 0, LENGTH = 0x1000000
> rom : ORIGIN = 0x1800000, LENGTH = 0x80000
>}
>
>SECTIONS
>{
> SECTIONS_BEGIN
> SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
> SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
> SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> SECTIONS_END
>}
>
>I did as you said(Only modified ROM and RAM config as above ),and using GDB
>
>can load app and app works perfectly fine.But when loading app using
>redboot
>commands "load -m xmodem"("load -m tftp" is same),and using "go" to execute
>
>app,redboot still will display strange string as
>
>"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
>#17$T0a0f:86000000;0d:80060"
>
>Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
>hal_arm_snds.cdl,the result were same.What is your detail steps in your
>successful executing app under redboot commands?
>
>Thanks lot!
>
>zheng
>
>
>
>
> >From: RandyLin@mxic.com.tw
> >To: ecos-discuss@sources.redhat.com
> >CC: wj_zheng10@hotmail.com
> >Subject: [ECOS] How to handle it???
> >Date: Wed, 3 Dec 2003 10:05:08 +0800
> >
> >
> >Can you use "load -m ymodem" or "load -m xmodem" to load ap??
> >I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
> >wrong...
> >I assume your redboot is ROM mode, so redboot's data section is at
>0x20000
> >when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
> >data section,
> >because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
> >section to 0x20000
> >so that's why u got the "Ignoring packet error, continuing..",
> >I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
> >mlt_arm_snds_ram.ldi
> >"-r" option is for binary data, your ap is elf format, don't use "-r"
> >can u post the whole mlt_arm_snds_rom.ldi?
> >I don't know why you got the message "0x20000 which is not in RAM"
> >wish this help.
> >
> >
> >
> >
> >Thanks RandyLin:
> > Now my redboot can work,and I can use redboot command "load
> >......-m
> >
> >tftp....."to download app to snds board.
> > Howerer, if not using -r option,the error as displayed "***Abort!
> >Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> > If using -r option,app looks like to be downloaded correctly,but
> >the
> >display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> >0x00300000",and then if using redboot command "go 0x00300000" to execute
> >the app,the redboot will display some strange strings as
> >"
> >$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
> >#17$T0a0f:8600"on
> >console.
> >
> >to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
>and
> >SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
>mlt_arm_snds_ram.ldi
> >
> >and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
>(ram,
> >
> >0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
> >
> >If using arm-elf-gdb to download app,the steps is as following:
> >1 [root@zheng root]#arm-elf-gdb
> >2(gdb) target remote /dev/ttyS0
> >Remote debugging using /dev/ttyS0
> >0x01804b30 in ?? ()
> >(gdb) load /tftpboot/hello
> >Loading section .rom_vectors, size 0x40 lma 0x20000
> >Loading section .text, size 0xfe00 lma 0x20040
> >Ignoring packet error, continuing...
> >Ignoring packet error, continuing...
> >Ignoring packet error, continuing...
> >
> >and gdb use the same serial line as the hyperspatial,the baudrate is
>38400.
> >
> >
> >Why did these error happen?Can some one have good idea to handle it?
> >
> >Thanks a lot!
> >
> >_________________________________________________________________
> >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> >http://join.msn.com/?page=features/junkmail
> >
> >
> >--
> >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
> >
> >
> >
> >
> >
hi,RandyLin:
I don't know if you had done some other steps or made some other
modification,but I did as what you had said,it seems no use.why?
Thanks lot!
zheng
> >
> >--
> >Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> >and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
>
>_________________________________________________________________
>Winterize your home with tips from MSN House & Home.
>http://special.msn.com/home/warmhome.armx
>
>
>
>
>
>
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-03 9:21 RandyLin
0 siblings, 0 replies; 12+ messages in thread
From: RandyLin @ 2003-12-03 9:21 UTC (permalink / raw)
To: ecos-discuss; +Cc: wj_zheng10
It's nice to hear that you can use gdb to run the ap:)
your mlt_arm_snds_ram.ldi and mlt_arm_snds_rom.ldi seems fine.
I add the following to hal_arm_snds.cdl, copy from hal_arm_at91.cdl
==================================
+ cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
+ display "Work with a ROM monitor"
+ flavor booldata
+ legal_values { "Generic" "GDB_stubs" }
+ default_value { CYG_HAL_STARTUP == "RAM" ? "GDB_stubs" : 0 }
+ parent CYGPKG_HAL_ROM_MONITOR
+ requires { CYG_HAL_STARTUP == "RAM" }
+ description "
+ Support can be enabled for different varieties of ROM
monitor.
+ This support changes various eCos semantics such as the
encoding
+ of diagnostic output, or the overriding of hardware interrupt
+ vectors.
+ Firstly there is \"Generic\" support which prevents the HAL
+ from overriding the hardware vectors that it does not use, to
+ instead allow an installed ROM monitor to handle them. This
is
+ the most basic support which is likely to be common to most
+ implementations of ROM monitor.
+ \"GDB_stubs\" provides support when GDB stubs are included in
+ the ROM monitor or boot ROM."
+ }
====================================
and add the following to redboot_ROM.ecm,
========================
+cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
+ inferred_value 0 0
+};
========================
maybe you should recompile the redboot[ROM], and ap[RAM]
then try again,good luck....^^
Thanks RandyLin:
here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want to
see:
mlt_arm_snds_ram.ldi:
#include <cyg/infra/cyg_type.inc>
MEMORY
{
ram : ORIGIN = 0x000000, LENGTH = 0x01000000
}
SECTIONS
{
SECTIONS_BEGIN
SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
and mlt_arm_snds_rom.ldi:
#include <cyg/infra/cyg_type.inc>
MEMORY
{
ram : ORIGIN = 0, LENGTH = 0x1000000
rom : ORIGIN = 0x1800000, LENGTH = 0x80000
}
SECTIONS
{
SECTIONS_BEGIN
SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
I did as you said(Only modified ROM and RAM config as above ),and using GDB
can load app and app works perfectly fine.But when loading app using
redboot
commands "load -m xmodem"("load -m tftp" is same),and using "go" to execute
app,redboot still will display strange string as
"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
#17$T0a0f:86000000;0d:80060"
Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
hal_arm_snds.cdl,the result were same.What is your detail steps in your
successful executing app under redboot commands?
Thanks lot!
zheng
>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>CC: wj_zheng10@hotmail.com
>Subject: [ECOS] How to handle it???
>Date: Wed, 3 Dec 2003 10:05:08 +0800
>
>
>Can you use "load -m ymodem" or "load -m xmodem" to load ap??
>I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
>wrong...
>I assume your redboot is ROM mode, so redboot's data section is at
0x20000
>when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
>data section,
>because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
>section to 0x20000
>so that's why u got the "Ignoring packet error, continuing..",
>I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
>mlt_arm_snds_ram.ldi
>"-r" option is for binary data, your ap is elf format, don't use "-r"
>can u post the whole mlt_arm_snds_rom.ldi?
>I don't know why you got the message "0x20000 which is not in RAM"
>wish this help.
>
>
>
>
>Thanks RandyLin:
> Now my redboot can work,and I can use redboot command "load
>......-m
>
>tftp....."to download app to snds board.
> Howerer, if not using -r option,the error as displayed "***Abort!
>Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> If using -r option,app looks like to be downloaded correctly,but
>the
>display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
>0x00300000",and then if using redboot command "go 0x00300000" to execute
>the app,the redboot will display some strange strings as
>"
>$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
>#17$T0a0f:8600"on
>console.
>
>to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and
>SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
mlt_arm_snds_ram.ldi
>
>and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
(ram,
>
>0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
>
>If using arm-elf-gdb to download app,the steps is as following:
>1 [root@zheng root]#arm-elf-gdb
>2(gdb) target remote /dev/ttyS0
>Remote debugging using /dev/ttyS0
>0x01804b30 in ?? ()
>(gdb) load /tftpboot/hello
>Loading section .rom_vectors, size 0x40 lma 0x20000
>Loading section .text, size 0xfe00 lma 0x20040
>Ignoring packet error, continuing...
>Ignoring packet error, continuing...
>Ignoring packet error, continuing...
>
>and gdb use the same serial line as the hyperspatial,the baudrate is
38400.
>
>
>Why did these error happen?Can some one have good idea to handle it?
>
>Thanks a lot!
>
>_________________________________________________________________
>Help STOP SPAM with the new MSN 8 and get 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>
>
>
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx
--
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] 12+ messages in thread
* RE: [ECOS] How to handle it???
@ 2003-12-03 8:52 zheng wujun
0 siblings, 0 replies; 12+ messages in thread
From: zheng wujun @ 2003-12-03 8:52 UTC (permalink / raw)
To: RandyLin; +Cc: ecos-discuss
Thanks RandyLin:
here is my mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi which you want to
see:
mlt_arm_snds_ram.ldi:
#include <cyg/infra/cyg_type.inc>
MEMORY
{
ram : ORIGIN = 0x000000, LENGTH = 0x01000000
}
SECTIONS
{
SECTIONS_BEGIN
SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
SECTION_rom_vectors (ram, 0x50000, LMA_EQ_VMA)
SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
and mlt_arm_snds_rom.ldi:
#include <cyg/infra/cyg_type.inc>
MEMORY
{
ram : ORIGIN = 0, LENGTH = 0x1000000
rom : ORIGIN = 0x1800000, LENGTH = 0x80000
}
SECTIONS
{
SECTIONS_BEGIN
SECTION_rom_vectors (rom, 0x1800000, 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, 0x20, LMA_EQ_VMA)
SECTION_data (ram, 0x20000, FOLLOWING (.gcc_except_table))
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
I did as you said(Only modified ROM and RAM config as above ),and using GDB
can load app and app works perfectly fine.But when loading app using redboot
commands "load -m xmodem"("load -m tftp" is same),and using "go" to execute
app,redboot still will display strange string as
"$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060"
Even if added the macro "CYGSEM_HAL_USE_ROM_MONITOR" in file
hal_arm_snds.cdl,the result were same.What is your detail steps in your
successful executing app under redboot commands?
Thanks lot!
zheng
>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>CC: wj_zheng10@hotmail.com
>Subject: [ECOS] How to handle it???
>Date: Wed, 3 Dec 2003 10:05:08 +0800
>
>
>Can you use "load -m ymodem" or "load -m xmodem" to load ap??
>I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
>wrong...
>I assume your redboot is ROM mode, so redboot's data section is at 0x20000
>when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
>data section,
>because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
>section to 0x20000
>so that's why u got the "Ignoring packet error, continuing..",
>I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
>mlt_arm_snds_ram.ldi
>"-r" option is for binary data, your ap is elf format, don't use "-r"
>can u post the whole mlt_arm_snds_rom.ldi?
>I don't know why you got the message "0x20000 which is not in RAM"
>wish this help.
>
>
>
>
>Thanks RandyLin:
> Now my redboot can work,and I can use redboot command "load
>......-m
>
>tftp....."to download app to snds board.
> Howerer, if not using -r option,the error as displayed "***Abort!
>Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> If using -r option,app looks like to be downloaded correctly,but
>the
>display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
>0x00300000",and then if using redboot command "go 0x00300000" to execute
>the app,the redboot will display some strange strings as
>"
>$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
>#17$T0a0f:8600"on
>console.
>
>to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and
>SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file mlt_arm_snds_ram.ldi
>
>and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data (ram,
>
>0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
>
>If using arm-elf-gdb to download app,the steps is as following:
>1 [root@zheng root]#arm-elf-gdb
>2(gdb) target remote /dev/ttyS0
>Remote debugging using /dev/ttyS0
>0x01804b30 in ?? ()
>(gdb) load /tftpboot/hello
>Loading section .rom_vectors, size 0x40 lma 0x20000
>Loading section .text, size 0xfe00 lma 0x20040
>Ignoring packet error, continuing...
>Ignoring packet error, continuing...
>Ignoring packet error, continuing...
>
>and gdb use the same serial line as the hyperspatial,the baudrate is 38400.
>
>
>Why did these error happen?Can some one have good idea to handle it?
>
>Thanks a lot!
>
>_________________________________________________________________
>Help STOP SPAM with the new MSN 8 and get 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>
>
>
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx
--
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] 12+ messages in thread
* Re: [ECOS] How to handle it???
@ 2003-12-03 6:10 zheng wujun
0 siblings, 0 replies; 12+ messages in thread
From: zheng wujun @ 2003-12-03 6:10 UTC (permalink / raw)
To: gary; +Cc: ecos-discuss
Hi, Gary
Thanks for your so fast reply.
I'll show you my target redboot_ROM.bin detailed startup screen messages
bellow:
MAC address 08:88:12:34:56:78
ks5000_ether: installInterrupts()
Ethernet eth0: MAC address 08:88:12:34:56:78
IP: 192.168.20.173/255.255.255.0, Gateway: 192.168.20.254
Default server: 0.0.0.0, DNS server IP: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 10:42:58, Dec 3
2003
Platform: Samsung SNDS (ARM 7TDMI)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
RAM: 0x00000000-0x01000000, 0x0002ff88-0x01000000 available
RedBoot>
I make my application Hello output as elf file, and then by using the
command "arm-elf-objcopy" to translate my elf formated hello into binary.
Well, I begin to download my application Hello with command bellow,and the
redboot display messages on screeen like this:
RedBoot> load -v -r -h 192.168.20.172 -m tftp -b 0x300000
/tftpdboot/hello.bin(or hello)
---
Raw file loaded 0x00300000-0x003100ff, assumed entry at
0x00300000
OK, I think every thing is very good so far.
But when I execute application hello by doing "GO 0x300000", the
application did not say "HELLO!" , instead, the redboot say:
RedBoot>go 0x300000
$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:8
note:when I use hello elf format,the same will happen.
That's all happened to my situation.
By the way, my ROM version Hello.bin burned into flash can work very well
without the redboot environment, this maybe show that my compilation of
hello with ecos kernal is allright.
Why hello doesn't run on redboot correctly?
Best Regards
----zheng
>From: Gary Thomas <gary@mlbassoc.com>
>To: zheng wujun <wj_zheng10@hotmail.com>
>CC: ecos-discuss@sources.redhat.com, RandyLin@mxic.com.tw
>Subject: Re: [ECOS] How to handle it???
>Date: 02 Dec 2003 19:23:44 -0700
>
>On Tue, 2003-12-02 at 18:25, zheng wujun wrote:
> > Thanks RandyLin:
> > Now my redboot can work,and I can use redboot command "load
>......-m
> > tftp....."to download app to snds board.
> > Howerer, if not using -r option,the error as displayed "***Abort!
> > Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> > If using -r option,app looks like to be downloaded correctly,but
>the
> > display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> > 0x00300000",and then if using redboot command "go 0x00300000" to
>execute
> > the app,the redboot will display some strange strings as
> > "
> >
>$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;#17$T0a0f:8600"on
> > console.
>
>When you startup RedBoot, what does it tell you the available RAM
>regions are? For example, on this board:
> RAM: 0x00000000-0x00800000, [0x00038de8-0x007ec000] available
>The board has 8MB of RAM, starting at 0x00000000, but RedBoot uses all of
>the memory up to 0x00038de8. So, for this board, eCos programs are linked
>to start at 0x40000.
>
>Note: eCos programs are typically *not* position independent. If the
>program
>is linked to load & run at 0x20000, that's the only location in RAM where
>you can put it. Your example above where you overrode this and put the
>code at 0x30000 will never work.
>
>Loading a file with the "-r" option tells RedBoot not to interpret the
>contents
>in any way. For an ELF file, this is deadly, as you'll be trying to
>execute
>the ELF binary file header which is just a set of illegal ARM instructions!
>
> >
> > to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
>and
> > SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file
>mlt_arm_snds_ram.ldi
> > and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data
>(ram,
> > 0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
> >
> > If using arm-elf-gdb to download app,the steps is as following:
> > 1 [root@zheng root]#arm-elf-gdb
> > 2(gdb) target remote /dev/ttyS0
> > Remote debugging using /dev/ttyS0
> > 0x01804b30 in ?? ()
> > (gdb) load /tftpboot/hello
> > Loading section .rom_vectors, size 0x40 lma 0x20000
> > Loading section .text, size 0xfe00 lma 0x20040
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> >
> > and gdb use the same serial line as the hyperspatial,the baudrate is
>38400.
> >
> >
> > Why did these error happen?Can some one have good idea to handle it?
> >
> > Thanks a lot!
> >
> > _________________________________________________________________
> > Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > http://join.msn.com/?page=features/junkmail
>--
>Gary Thomas <gary@mlbassoc.com>
>MLB Associates
>
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
--
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] 12+ messages in thread
* Re: [ECOS] How to handle it???
2003-12-03 1:25 zheng wujun
@ 2003-12-03 2:23 ` Gary Thomas
0 siblings, 0 replies; 12+ messages in thread
From: Gary Thomas @ 2003-12-03 2:23 UTC (permalink / raw)
To: zheng wujun; +Cc: ecos-discuss, RandyLin
On Tue, 2003-12-02 at 18:25, zheng wujun wrote:
> Thanks RandyLin:
> Now my redboot can work,and I can use redboot command "load ......-m
> tftp....."to download app to snds board.
> Howerer, if not using -r option,the error as displayed "***Abort!
> Attempt to load ELF data to address: 0x00020000 which is not in RAM".
> If using -r option,app looks like to be downloaded correctly,but the
> display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
> 0x00300000",and then if using redboot command "go 0x00300000" to execute
> the app,the redboot will display some strange strings as
> "
> $T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;#17$T0a0f:8600"on
> console.
When you startup RedBoot, what does it tell you the available RAM
regions are? For example, on this board:
RAM: 0x00000000-0x00800000, [0x00038de8-0x007ec000] available
The board has 8MB of RAM, starting at 0x00000000, but RedBoot uses all of
the memory up to 0x00038de8. So, for this board, eCos programs are linked
to start at 0x40000.
Note: eCos programs are typically *not* position independent. If the program
is linked to load & run at 0x20000, that's the only location in RAM where
you can put it. Your example above where you overrode this and put the
code at 0x30000 will never work.
Loading a file with the "-r" option tells RedBoot not to interpret the contents
in any way. For an ELF file, this is deadly, as you'll be trying to execute
the ELF binary file header which is just a set of illegal ARM instructions!
>
> to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and
> SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file mlt_arm_snds_ram.ldi
> and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data (ram,
> 0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
>
> If using arm-elf-gdb to download app,the steps is as following:
> 1 [root@zheng root]#arm-elf-gdb
> 2(gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> 0x01804b30 in ?? ()
> (gdb) load /tftpboot/hello
> Loading section .rom_vectors, size 0x40 lma 0x20000
> Loading section .text, size 0xfe00 lma 0x20040
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
>
> and gdb use the same serial line as the hyperspatial,the baudrate is 38400.
>
>
> Why did these error happen?Can some one have good idea to handle it?
>
> Thanks a lot!
>
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> http://join.msn.com/?page=features/junkmail
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
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] 12+ messages in thread
* [ECOS] How to handle it???
@ 2003-12-03 2:05 RandyLin
0 siblings, 0 replies; 12+ messages in thread
From: RandyLin @ 2003-12-03 2:05 UTC (permalink / raw)
To: ecos-discuss; +Cc: wj_zheng10
Can you use "load -m ymodem" or "load -m xmodem" to load ap??
I saw your mlt_arm_snds_rom.ldi and mlt_arm_snds_ram.ldi....it may be
wrong...
I assume your redboot is ROM mode, so redboot's data section is at 0x20000
when u use arm-elf-gdb to load ap(RAM mode), it overwrite the redboot's
data section,
because your mlt_arm_snds_ram.ldi locate the rom_vectors and following
section to 0x20000
so that's why u got the "Ignoring packet error, continuing..",
I modify the SECTION_rom_vectors (ram, 0x00050000, LMA_EQ_VMA) in
mlt_arm_snds_ram.ldi
"-r" option is for binary data, your ap is elf format, don't use "-r"
can u post the whole mlt_arm_snds_rom.ldi?
I don't know why you got the message "0x20000 which is not in RAM"
wish this help.
Thanks RandyLin:
Now my redboot can work,and I can use redboot command "load ......-m
tftp....."to download app to snds board.
Howerer, if not using -r option,the error as displayed "***Abort!
Attempt to load ELF data to address: 0x00020000 which is not in RAM".
If using -r option,app looks like to be downloaded correctly,but
the
display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
0x00300000",and then if using redboot command "go 0x00300000" to execute
the app,the redboot will display some strange strings as
"
$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;
#17$T0a0f:8600"on
console.
to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and
SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file mlt_arm_snds_ram.ldi
and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data (ram,
0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
If using arm-elf-gdb to download app,the steps is as following:
1 [root@zheng root]#arm-elf-gdb
2(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
0x01804b30 in ?? ()
(gdb) load /tftpboot/hello
Loading section .rom_vectors, size 0x40 lma 0x20000
Loading section .text, size 0xfe00 lma 0x20040
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
and gdb use the same serial line as the hyperspatial,the baudrate is 38400.
Why did these error happen?Can some one have good idea to handle it?
Thanks a lot!
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
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] 12+ messages in thread
* [ECOS] How to handle it???
@ 2003-12-03 1:25 zheng wujun
2003-12-03 2:23 ` Gary Thomas
0 siblings, 1 reply; 12+ messages in thread
From: zheng wujun @ 2003-12-03 1:25 UTC (permalink / raw)
To: ecos-discuss; +Cc: RandyLin
Thanks RandyLin:
Now my redboot can work,and I can use redboot command "load ......-m
tftp....."to download app to snds board.
Howerer, if not using -r option,the error as displayed "***Abort!
Attempt to load ELF data to address: 0x00020000 which is not in RAM".
If using -r option,app looks like to be downloaded correctly,but the
display is "Raw file loaded 0x00300000-0x003c6116, assumed entry at
0x00300000",and then if using redboot command "go 0x00300000" to execute
the app,the redboot will display some strange strings as
"
$T0a0f:86000000;0d:80060200;#17$T0a0f:86000000;0d:80060200;#17$T0a0f:8600"on
console.
to above,the config is SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and
SECTION_rom_vectors (ram, 0x20000, LMA_EQ_VMA) in file mlt_arm_snds_ram.ldi
and SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA) and SECTION_data (ram,
0x20000, FOLLOWING (.gcc_except_table)) in mlt_arm_snds_rom.ldi
If using arm-elf-gdb to download app,the steps is as following:
1 [root@zheng root]#arm-elf-gdb
2(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
0x01804b30 in ?? ()
(gdb) load /tftpboot/hello
Loading section .rom_vectors, size 0x40 lma 0x20000
Loading section .text, size 0xfe00 lma 0x20040
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
and gdb use the same serial line as the hyperspatial,the baudrate is 38400.
Why did these error happen?Can some one have good idea to handle it?
Thanks a lot!
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
--
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] 12+ messages in thread
end of thread, other threads:[~2003-12-04 20:50 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-04 5:50 [ECOS] How to handle it??? RandyLin
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 20:45 RandyLin
2003-12-04 20:50 ` Gary Thomas
2003-12-04 5:55 RandyLin
2003-12-04 4:43 zheng wujun
2003-12-04 3:10 zheng wujun
2003-12-03 9:21 RandyLin
2003-12-03 8:52 zheng wujun
2003-12-03 6:10 zheng wujun
2003-12-03 2:05 RandyLin
2003-12-03 1:25 zheng wujun
2003-12-03 2:23 ` Gary Thomas
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).