MCBSTM32 + ULINK2 Debug Problem

Hi!

First I have to say everything worked fine till now!

Now I get the error: "cannot access memory"

When debugging a sample project like "Blinky" I get the error when starting, but debugging seems to work fine.

When debugging my own project it depends on the CPU Speed (PLL Multiplier) if debugging works or not. But everytime I get the error "cannot access memory"!!

So my question is if the ulink2 or the mcbstm32 causes the problem?

best regards
Mathias

Parents
  • To isolate the error I did following:

    * Tried different projects => same error
    * Changed the developement board => same error
    * Tried it on a different pc => same error

    So my conclusion is that the uLink2 must be the problem!

    Strangely enough the uLink2 gets correctly detected in uVison 4 (ULINK Cortex Debugger Settings)! Additional the firmware update to V1.4 finished without errors!

    I have tried to connect with all posibilities (JTAG, SW, different connect & reset options) but everytime I get the same error!

    The only thing which seems to be strange is that the uLink2 is installed under Human Interface Devices with following 2 entries:
    *HID-compliant device
    *USB Human Interface Device

    => Reinstalling the driver results in the same entries!

    My Toolchain is up to date:

    IDE-Version:
    µVision V4.00u
    Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2009

    Tool Version Numbers:
    Toolchain: RealView MDK-ARM Version: 4.03a
    Middleware: RL-ARM Real-Time Library Version V4.05
    Toolchain Path: BIN40\
    C Compiler: Armcc.Exe V4.0.0.524
    Assembler: Armasm.Exe V4.0.0.524
    Linker/Locator: ArmLink.Exe V4.0.0.524
    Librarian: ArmAr.Exe V4.0.0.524
    Hex Converter: FromElf.Exe V4.0.0.524
    CPU DLL: SARMCM3.DLL V4.03a
    Dialog DLL: DARMSTM.DLL V1.45b
    Target DLL: BIN\UL2CM3.DLL V1.62
    Dialog DLL: TARMSTM.DLL V1.43

    Best regards
    Mathias

Reply
  • To isolate the error I did following:

    * Tried different projects => same error
    * Changed the developement board => same error
    * Tried it on a different pc => same error

    So my conclusion is that the uLink2 must be the problem!

    Strangely enough the uLink2 gets correctly detected in uVison 4 (ULINK Cortex Debugger Settings)! Additional the firmware update to V1.4 finished without errors!

    I have tried to connect with all posibilities (JTAG, SW, different connect & reset options) but everytime I get the same error!

    The only thing which seems to be strange is that the uLink2 is installed under Human Interface Devices with following 2 entries:
    *HID-compliant device
    *USB Human Interface Device

    => Reinstalling the driver results in the same entries!

    My Toolchain is up to date:

    IDE-Version:
    µVision V4.00u
    Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2009

    Tool Version Numbers:
    Toolchain: RealView MDK-ARM Version: 4.03a
    Middleware: RL-ARM Real-Time Library Version V4.05
    Toolchain Path: BIN40\
    C Compiler: Armcc.Exe V4.0.0.524
    Assembler: Armasm.Exe V4.0.0.524
    Linker/Locator: ArmLink.Exe V4.0.0.524
    Librarian: ArmAr.Exe V4.0.0.524
    Hex Converter: FromElf.Exe V4.0.0.524
    CPU DLL: SARMCM3.DLL V4.03a
    Dialog DLL: DARMSTM.DLL V1.45b
    Target DLL: BIN\UL2CM3.DLL V1.62
    Dialog DLL: TARMSTM.DLL V1.43

    Best regards
    Mathias

Children
More questions in this forum