arm-elf-gdb or server hangs during flash programming of LPC2366

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • arm-elf-gdb or server hangs during flash programming of LPC2366


    I am pretty new at this, allthough I have managed to program my LPC2366 with J-link + GDB server + Yagarto GDB (arm-elf-gdb.exe).
    The problem is that sometimes the script stops, or the server stops (I do not know which). I start the process by typing the following in the commando prompt:
    arm-elf-gdb -x lpc2366_rom_jlink.gdb my_program.elf

    were lpc2366_rom_jlink.gdb contains:

    target remote localhost:2331
    monitor flash device = LPC2366
    monitor flash download = 1
    monitor flash breakpoints = 0
    monitor endian little
    monitor speed adaptive
    monitor reset
    monitor long 0xE01FC040 = 1

    This is what the commando prompt shows:
    C:\z>arm-elf-gdb -x lpc2366_rom_jlink.gdb my_program.elf
    GNU gdb
    Copyright (C) 2006 Free Software Foundation,
    GDB is free software, covered by the GNU Gene
    welcome to change it and/or distribute copies
    Type "show copying" to see the conditions.
    There is absolutely no warranty for GDB. Typ
    This GDB was configured as "--host=i686-pc-cy
    (no debugging symbols found)

    0x00000000 in _vectors ()
    Select flash device: LPC2366
    Flash download enabled
    Flash breakpoints disabled
    Target endianess set to "little endian"
    Select adaptive clocking instead of fixed JTA
    Resetting target
    Writing 0x00000001 @ address 0xE01FC040

    Loading section .vectors, size 0x3c lma 0x0
    <-- Here it stops!
    If I terminate the GDB server, the script exits this "hanging state".

    What can be the source to this problem?

    Thank you for any suggestions!
  • Hi!

    Thanks for the answer... I cannot find any problems in my Linker script used by the Linker in Rowley CrossStudio that I use.
    It produces a .elf file, the Entry point is reset_handler and the architecture is ARM.

    The strange thing is that the problem is not deterministic, it occurs at random occations and the simplest way of getting through the hang-up is to close down the GDB server and restart it again. I will try locate any other errors today...