RE: [ECOS] I think this is wrong........about SamSung SNDS.

[RandyLin at mxic dot com dot tw]

hi, zheng:

please send to the mailing list, and everyone can join the discuss.
I am not ready to use tftp, because in the first, redboot "load" & "go"
is not working.
I have the same conflict as you said, just click "continue".
Is your redboot working?? can u see the redboot output string on
hyperterminal?? what baudrate u use?
I suggest just ignore the tftp until u can download the ap with redboot!





hi,RandyLin:

First,I'm sorry for my disturbing your work!
I'm a newbie to ecos and use samsung snds as same as yours.I build the
redboot and application all correctly!but when I tftp my application onto
snds,the app can not work correctly.and if using gdb,the "packet error
ingored ....."will displaied on console.why?

I read your article and do as you said,but can not work correctly as
before.and new conflicts will happened as
"CYGGDB_HAL_DEBUG_GDB_INCLUDE_STUBS unsatified because requirs
!CYGSEM_HAL_USE_ROM_MONITOR" and so on.
Can you give some more detailed information?

Best regards!

zheng



>From: RandyLin@mxic.com.tw
>To: ecos-discuss@sources.redhat.com
>Subject: [ECOS] I think this is wrong........about SamSung SNDS.
>Date: Mon, 1 Dec 2003 15:51:41 +0800
>
>I recently use SamSung SNDS based board with eCos,
>I have redboot[ROM] in my flash, and ap for ram mode.
>but I can only run on arm-elf-gdb, always failed on
>redboot "load" "go" command(mangling string output)
>so I trace more deeper......and I find some thing may be modified....
>
>1. in hal_arm_snds.cdl, there is no cdl_option CYGSEM_HAL_USE_ROM_MONITOR,
>     because of this, CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE is
disable,
>     when compile application, CYGSEM_HAL_DIAG_MANGLER is set to GDB, so
>the
>     application output string encode by mangler. This is why I always see
>mangling string
>     output when using redboot "load" and "go" command.
>     So...I add cdl_option CYGSEM_HAL_USE_ROM_MONITOR in hal_arm_snds.cdl
>
>2. in mlt_arm_snds_ram.ldi:
>       SECTION_fixed_vectors (ram, 0x200, LMA_EQ_VMA)
>     in mlt_arm_snds_rom.ldi:
>       SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
>     when compile redboot[ROM], fixed_vectors locate at 0x20, but compile
>application
>     for RAM mode, fixed_vectors is locate 0x200, so ap got wrong address
>when access
>     to hal_virtual_vector_table.
>     I think fixed_vectors should be the same, at 0x20
>
>after modify the code, I can use arm-elf-gdb and redboot to run ap
>correctly.
>Application inherit the console, when connect to arm-elf-gdb, mangler
>encode the output
>string, and in redboot, raw ascii text is output.
>If i am wrong, please correct me, 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
>

_________________________________________________________________
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