This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Integrating a third-party jtag debugger to keil uvision

Hello. I would like to integrate third-party debugger "emulator that supports JTAG debugging for ARM7 and ARM9 devices" to keil uvision, so I could flash LPC2214 using that debugger.
Our university has a bunch of them, so they found it easier and more educative to integrate these debuggers then buying a lot of branded jtag debuggers.
Could you please give a cue what i am to do. I guess, the point is to write a driver or modify the existed third-party driver, isn't it?

Parents
  • Okay guys, I've had the other work to do, now back to this problem:
    I've found out the JEM-ARM Debugger installs as "USB Serial Converter" and "USB Serial Port (COM10)". Information about drivers from the Windows Device Manager is below:
    USB Serial Converter
    Driver files:
    C:\Windows\system32\drivers\ftdibus.sys
    C:\Windows\system32\ftbusui.dll
    C:\Windows\system32\ftd2xx.dll
    C:\Windows\system32\FTLang.dll
    C:\Windows\system32\ftd2xx.dll

    USB Serial Port (COM10)
    Driver files:
    C:\Windows\system32\drivers\ftser2k.sys
    C:\Windows\system32\DRIVERS\serenum.sys
    C:\Windows\system32\ftcserco.dll
    C:\Windows\system32\ftserui2.dll

    Adding path to one of the dlls to the TOOLS.ini leads to the following message when I choose the device:
    Error: Cannot load driver <path to the dll here>
    Possible reasons:
    Driver DLL could not be found in the specified path
    Driver DLL requires additional DLL's which are not installed
    Required Hardware Drivers are not installed

    I suppose the 2nd reason, so how do I mention additional dlls? or am I completely wrong speaking of the driver files above and still need to write the driver?
    Thanks for your time.

Reply
  • Okay guys, I've had the other work to do, now back to this problem:
    I've found out the JEM-ARM Debugger installs as "USB Serial Converter" and "USB Serial Port (COM10)". Information about drivers from the Windows Device Manager is below:
    USB Serial Converter
    Driver files:
    C:\Windows\system32\drivers\ftdibus.sys
    C:\Windows\system32\ftbusui.dll
    C:\Windows\system32\ftd2xx.dll
    C:\Windows\system32\FTLang.dll
    C:\Windows\system32\ftd2xx.dll

    USB Serial Port (COM10)
    Driver files:
    C:\Windows\system32\drivers\ftser2k.sys
    C:\Windows\system32\DRIVERS\serenum.sys
    C:\Windows\system32\ftcserco.dll
    C:\Windows\system32\ftserui2.dll

    Adding path to one of the dlls to the TOOLS.ini leads to the following message when I choose the device:
    Error: Cannot load driver <path to the dll here>
    Possible reasons:
    Driver DLL could not be found in the specified path
    Driver DLL requires additional DLL's which are not installed
    Required Hardware Drivers are not installed

    I suppose the 2nd reason, so how do I mention additional dlls? or am I completely wrong speaking of the driver files above and still need to write the driver?
    Thanks for your time.

Children