Uploaded image for project: 'CLI Flasher'
  1. CLI Flasher
  2. NXTFLASHER-47

Remove HW breakpoint when CLI Flasher is closed regularly

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V1.5.0
    • Fix Version/s: V1.6.3
    • Component/s: None
    • Labels:
      None
    • Account:
      SCT CLIFlasher operational (CLIFLASHER)

      Description

      inside netX 90 a hardware breakpoint is set at address 0x23ffc. This leads to the error, that a SW can not be started after a programm cycle and a normal reset via the reset button, because the JTAG part is not reset.

       

      FIX:

      remove the HW breakpoint after the programming has been finished / connection to netx has been closed.

       

      Check this also for all other netX versions.

       

       

      TODO:

      • check when the BP is set (how often it is set)
        • this could be either when the flasher is donloaded to the netx or with every flasher command
      • when it is set with every flash command: remove BP whenever the BP is reached (whenever we return to tcl-script which controls/waits for the BP)
      • when it is set with download function: set the BPO with every command instead! and also remove after reaching BP.

      Check call of m_tJtagDevice.tFunctions.tFn.pfnCommandRunLine for return value of called tcl function

      Verification for fix:

      • manually test inside print message after deinit_breakpoint
        • BP list should be empty (not contain the BP from flasher)
      • automated tests (need to be discussed)

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  GDormann Guido Dormann
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: