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

[RandyLin at mxic dot com dot tw]

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