Debug Connection Error in ARM development studio

Hi, I am using ULINKpro D and JTAG connection to program a Cortex M7 baremetal device. 
Although ULINKpro D seems to be installed correctly (device manager - USB) and the connection between ULINKpro D and my DU seems okay, I cannot connect the debugger and this page shows up;


Also I get an error in Console:

Unable to connect to device ARMCS-DP



I tried a couple of changes and I have this error as well:

Detected number of devices = 136, maximum allowed = 128. This problem is usually a result of the scanchain not acting correctly when using JTAG scans to count the number of devices.


Does anyone know how to solve it?
The only thing that has to be mentioned is that I am using 20 to 20 pin adaptor provided in the package of ULINKpro D.

Thanks & regards 

Parents
  • Hi again

    There are various reasons why the debugger might be unable to read the memory/peripheral at that addresses, for example:

    * the peripheral might be powered-down

    * the peripheral might need to be explicitly enabled before use

    * the MPU might be blocking access to that address

    * the memory/peripheral might be inaccessible/disabled for the current processor mode or security state (e.g. some memory/peripherals are only accessible in secure state)

    * the memory/peripheral might require a certain access width, e.g. 8-, 16- or 32-bit access.
    For example, to read a word with a 16-bit (LDRH) access, you can use:
    x /w <width=16>:0x60000000

    You'll need to check the specification for your target to investigate what might be preventing the access.

    Stephen

Reply
  • Hi again

    There are various reasons why the debugger might be unable to read the memory/peripheral at that addresses, for example:

    * the peripheral might be powered-down

    * the peripheral might need to be explicitly enabled before use

    * the MPU might be blocking access to that address

    * the memory/peripheral might be inaccessible/disabled for the current processor mode or security state (e.g. some memory/peripherals are only accessible in secure state)

    * the memory/peripheral might require a certain access width, e.g. 8-, 16- or 32-bit access.
    For example, to read a word with a 16-bit (LDRH) access, you can use:
    x /w <width=16>:0x60000000

    You'll need to check the specification for your target to investigate what might be preventing the access.

    Stephen

Children