Crazy Long delays when debug stepping

Comments

10 comments

  • Avatar
    Markus

    Hello Mark,

     

    the onboard-JTAG Adapters are rather slow. If you have opened several register- and memory-watch windows this could slow down the stepping. All this Values are reloaded at each step. If the JTAG-Connection is slow, you can face these long delays.

    Just an Idea.

    Regards

    Markus

     

    0
    Comment actions Permalink
  • Avatar
    Ms115

    Markus,


    I think you may be right,


    Crossworks’s Michael suggested I delete the .hzs file. I was convinced I had done this more than once (as you prob know this is where this stuff is held). But I guess I hadn't, as it fixed it (doh).


    I had this issue for several days and tried all sorts of things – Making the STLink use JLink drivers, even converting the project to TrueStudio (yes I know - but I was desperate).


    I’m not sure what the .hzs file held that was causing problems, but it may well have been memory watch stuff (hiding from me somehow!)


    …. now off to delete the TrueStudio version of my project :)

    Thanks
    Mark

    0
    Comment actions Permalink
  • Avatar
    Daniel Pfeil

    Hello,

    I'm also trying to build a TouchGFX project in Crossworks. Therfore I use the TouchGFX GCC toolchain in Crossworks.

    I get the following compile errors when compiling the FreeRTOS source file port.c:



    Do you have any idea?

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Try setting the Floating Point ABI to Hard

    Regards

    Michael

    0
    Comment actions Permalink
  • Avatar
    Daniel Pfeil

    Hi Michael,

    thank you for your response!

    Setting the floating point to hard solves the compile error above but brings up a lot of link errors:

    I think there are this link erros because the TouchGFX lib was built with soft floating point unit.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    There are two libraries

    libtouchgfx.a and libtouch-float-abi-hard.a

    use the latter one.

    Regards

    Michael

    0
    Comment actions Permalink
  • Avatar
    Daniel Pfeil

    Hi Michael,

    thank you, now I can build the project, but I'm not able to debug with crossworks as I get the following error when I start debugging (pressing F5).

    I think the problem is the external flash. Do you have any idea?

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    You may need to set the size of the QSPI memory in the "Memory Map Macros" property

    QUADSPI_FLASH_SIZE=0x01000000

    and a board specific loader will be required. This can be done by setting the "Project Macro" property

    LOADER=$(TargetsDir)/ST_STM32F746G_DISCOVERY/Loader.elf

    Regards

    Michael

    0
    Comment actions Permalink
  • Avatar
    Daniel Pfeil

    Now I use this loader: LOADER=$(TargetsDir)/ST_STM32F769I_DISCOVERY/Loader.elf

    With this loader every second time everything works fine (also the external flash can be earsed and programmed).

    But every second time the loader hangs up (loader exit timed out) when erasing the external flash.

    Do you have any idea?

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    I'd guess there are reset issues with the external flash.

    If this is a effectively a one-time process, e.g. to store data tables, you can use the "No Load Sections" project property to avoid programming this each time.

    0
    Comment actions Permalink

Please sign in to leave a comment.