Search Results

Search results 1-4 of 4.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi Nino, Atmel's EDBG with AS7 works fine. I had also tried removing the isolation resistors so that there was no question that the EDBG didn't pose a conflict for the SWD J-link connection. No effect. Thanks, --Dave

  • Hi Nino, There is no "project" at this time, I simply wanted to evaluate the part, so any of the testing done with J-link has been with an erased part (using AS7 and the ATMEL EDBG) OR with a simple blinking LED type test running. I tried your test with Embedded Studio and obtained identical results (can't halt, can't erase, etc.) as with Jlink commander, and AS7. As to identifying the demo board, there should be a sticker on the bottom with product code/revision and serial number on it. A09-274…

  • Hello Nino, The second attachment to my original message is a J-Link Commander dialog showing that "halt" along with "rx 0" and "r" don't work. However, I once again repeated this process, from target power on, and have limited the test to just a "halt", and attached that output to this response. The first attachment to my original message, the log file output, you referred to having the invalid memory access(s) is simply Atmel Studio 7 from the point of debugger attachment through attempted Chi…

  • Hi, With a j-link connected to a Microchip ATSAME54-XPRO using a Segger 9 pin Cortex-M adapter, the j-link is unable to halt the CPU. Using Atmel Studio 7.0 (Build 1645), programming and debugging this board is possible via Atmel's EDBG, and other ATSAM family parts work fine with the J-Link and AS7. Microchip support duplicated this and suggested advising Segger of the issue. I have tried Segger firmware/DLL versions from 6.16 through 6.22f, and I have tried removing the four isolation resistor…