[SOLVED] Atmel SAM-ICE: J-Link V4.84c Error

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

  • [SOLVED] Atmel SAM-ICE: J-Link V4.84c Error

    Since october last year I am debugging a board with two "Atmel SAM4S16B" installed. But when setting bit 31 (USEQ) in register at address 0x40038004 (ADC Mode Register) to 1, the SAM-ICE aborts the debug session with this error message:

    J-Link V4.84c Error

    The connected debug probe is not licensed for the selected device "ATSAM4S16B".
    Reason: Could not read emulator information
    Debug session will be terminated


    When this bit is set to 0, this error message will not occur and the debug session won't be terminated. But I have to set this bit to 1.

    OS: Windows10
    Development system: Atmel Studio 6.2 and Atmel Studio 7 (v. 7.0.1188)
    Updating the firmware of the SAM-ICE V8.00 with SEGGER J-Link Configurator has not changed this behaveior.

    Any help appreacheated.
    Regards, Anton
  • Hello Anton,

    Thank you for your inquiry. We are not aware of any issues like that.
    Could you please check if the issue still persists with our newest software version?
    Because the version you use is very old and we do not offer support for older releases. The current released version is V6.14
    You can download it here: segger.com/downloads/jlink

    Best regards
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Nino,

    thank you for your response. Before my first post I have downloaded the J-Link software package components and updated the firmware of the Atmel SAM-ICE V8.00. When doing this again I get this Log:

    SEGGER J-Link Configuration V6.12j
    Logging started @ 2017-02-28 09:39

    Updating firmware of 1 emulator:
    Updating firmware of emulator 1 of 1 via USB (SN: 28015796)... Not updated, emulator firmware is already up to date.
    Finished updating 1 emulator!


    When writing 0xA1080420 to address 0x40038004 (ADC Mode Register) the SAM-ICE aborts the debug session. After the firmware update without the error message.

    The same behavior when writing 0x00008020 to address 0x40038010 (ADC Channel Enable Register).

    How can I update from V6.12j to V6.14 ?
    Regards, Anton
  • Hello Anton,

    How can I update from V6.12j to V6.14 ?


    By simply downloading and installing the latest software pack from our website: segger.com/downloads/jlink


    When this bit is set to 0, this error message will not occur and the debug session won't be terminated. But I have to set this bit to 1.


    Did you clear the WPEN in Register Address: 0x400380E4 ? From the manual this write enable needs to be cleared before the ADC Mode Register can be written.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Nino,

    thanks for the info. But after updating to V6.14a the behavior is the same as before.
    The write protection (WPEN) is not set. The contents of Register 0x400380E4 = 0.

    I have tested my software on the evaluation board "Sam4S Xplained Pro" with the embedded Atmel debugger without any issues. The ADC is working with and without DMA as expected.

    Will a "Write Protection Violation" abort the debug session by the J-Link?
    Regards, Anton
  • Hello Anton,

    Will a "Write Protection Violation" abort the debug session by the J-Link?


    Generally not, it was just something i stumbled upon after reading the MCU manual for the registers you mentioned.

    Can you write to the ADC Mode Register to other Bits successfully? Is the error linked to Bit 31 in the register, or is it linked to the ADC register generally?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Nino,

    first I wrote 0x21080420 to the ADC Mode Register. The contents of the register has shown the written data, but the ADC didn't work as expected. After writing the correct value 0xA1080420 to the ADC Mode Register, the debug session was aborted.

    Then I tried a simpler way of reading channel 5 and 15 without setting bit 31 (USEQ) in the ADC Mode Register. But when writing 0x00008020 into the ADC Channel Enable Register (0x40038010), the debug session was aborted too.

    The connection from J-Link to my hardware does not contain the signal SWO. There are only VTref, SWDIO, nRESET, SWCLK and GND used.

    I hope this helps.
    Regards, Anton

    The post was edited 1 time, last by Xitacion ().

  • Hello Nino,

    Thank you for your support. This behavior was caused by a side effect of my hardware ;( .
    I have tested with a J-Link BASE too. With the same result as with the Atmel SAM-ICE.
    Both debug probes are working fine :thumbsup: .

    Best regards, Anton
  • Hello Anton,

    glad to hear that you are up and running again.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.