Search Results

I have raised this question before and sort of got an acknowledgment. The problem I have is I use IAR workbench (windows 7 PC) to debug our cortex-r4f target using the Jlink USB/Jtag emulator. When just using IAR connected to Jlink, all works smoothly. So far so good. However what I am also trying to do is have a separate PC application linked to the JlinkARM.dll to simply read (JLINKARM_ReadMemU32) and write (JLINKARM_WriteMem) memory to the same target over the same physical emulator. It does …

Assuming I have a PC program with multiple threads, can these threads each call api functions like JLINKARM_ReadMemU32 in a thread safe manner?

We currently are using the CSpyBat program to reset/download/run a cortex-r4f target device. Something like the following: set CSPY="C:\Program Files\IAR Systems\Embedded Workbench 6.0\common\bin\cspybat" "C:\Program Files\IAR Systems\Embedded Workbench 6.0\arm\bin\armproc.dll" "C:\Program Files\IAR Systems\Embedded Workbench 6.0\arm\bin\armjlink.dll" set CSPYPARAMS=--plugin "C:\Program Files\IAR Systems\Embedded Workbench 6.0\arm\bin\armbat.dll" --backend -B "--endian=little" "--cpu=Cortex-R4F"…

In your post you mentioned "using the JLink SDK, which I have wrapped in managed C#" I know that segger does not offer a C# interface and I started to write a minimal C# interface to the SDK but am having some problems with the proper compile and runtime syntax with void* parameters to/from DLL and managed code. I started with the 4 api's below but again am having problems with pointers either causing stack errors or protection memory violations. Would you be willing to share or post the set of …