[SOLVED] SAMA5D27 SOM1 Not Working Out of the Box

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

  • [SOLVED] SAMA5D27 SOM1 Not Working Out of the Box

    Having trouble with J-Link communicating with the SAMA5D27 on the eval board, ATSAMA5D27-SOM1-EK1. JLink.exe reports:

    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    **************************
    WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
    **************************

    Firmware: J-Link V10 compiled Apr 20 2018 16:47:09
    Hardware version: V10.10
    S/N: XXXXXXXX
    License(s): GDB
    VTref=3.193V


    The Eval board reports RomBOOT over serial so it's powered up. And my J-link Base works fine with my other eval board, Xplained Ultra.

    Advice?
  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    We tried to reproduce the issue using the SOM1-EK1 eval board as well and everything was working as expected and described in the eval board user manual.
    Which J-Link software version are you using?
    Does connecting via the J-Link OB (USB J10) work?
    When using the external debug header J11 did you consider the steps explained int he SOM1 Kit manual section: Disabling J-Link-OB (ATSAM3U4C)?
    There it states that the OB must be disabled by populating J7 before trying to connect via a external J-Link.
    Does it work if you do that?

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/
  • Thank you for your response.

    SEGGER J-Link Commander V6.32f (Compiled Jun 12 2018 14:47:13)
    DLL version V6.32f, compiled Jun 12 2018 14:46:40

    When I press the reset button, I see RomBOOT on the serial port, so I think J-Link OB (USB J10) works.

    Yes, I have a jumper closing J7.

    I have ordered another board, perhaps this one is defective.

    What is pin 15 (RESET)?
  • If I open J7, J-Link can see the SOM1 through the USB connection. I can program the board but debugging is limited, and I'd prefer to get the JTAG ICE working.

    With J7 closed, the emulator connected to JTAG can't see the board, as shown above.

    Should I try another J-Link emulator, as perhaps this one is faulty?

    (I received a new SOM1 eval board, and it behaves identically.)

    Any help would be appreciated.
  • Hello,

    Does the behaviour change if you update to the latest J-Link version?
    Could you provide a J-Link log of the failing session with the external J-Link? wiki.segger.com/Enable_J-Link_log_file

    40490FDB wrote:

    Why does J-Link complain about pin 15 Reset when the SOM1 datasheet lists pin 47 as Reset?
    Because J-Link sees Pin 15 on J-Link side beeing pulled high from target side. segger.com/products/debug-prob…gy/interface-description/
    This has not necessarily to do with the Reset Pin on the target side.

    How are you connecting externally? Do you use an adapter from 20 pin to 9 pin? Is it an adapter from SEGGER or a third party one?
    segger.com/products/debug-prob…s/9-pin-cortex-m-adapter/

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/
  • I downloaded 6.34g, updated the firmware, but no help.

    The connector I use is an Atmel part.



    SEGGER J-Link V6.34g Log File
    DLL Compiled: Sep 26 2018 14:45:08
    Logging started @ 2018-10-03 14:30
    T0D6C 000:000 JLINK_GetDLLVersion() returns 63407 (0000ms, 0000ms total)
    T0D6C 000:000 JLINK_GetCompileDateTime() (0000ms, 0000ms total)
    T0D6C 000:002 JLINK_SelectUSB(Port = 0) returns 0x00 (0005ms, 0005ms total)
    T0D6C 000:007 JLINK_SetWarnOutHandler(...) (0000ms, 0005ms total)
    T0D6C 000:007 JLINK_OpenEx(...)
    Firmware: J-Link V10 compiled Sep 4 2018 11:24:21
    Hardware: V10.10
    S/N: 50114432
    Feature(s): GDB
    TELNET listener socket opened on port 19021WEBSRV
    Starting webserver (2521ms, 2526ms total)
    T0D6C 000:007 WEBSRV Webserver running on local port 19080 (2522ms, 2527ms total)
    T0D6C 000:007 returns O.K. (2522ms, 2527ms total)
    T0D6C 002:530 JLINK_GetFirmwareString(...) (0000ms, 2527ms total)
    T0D6C 002:533 JLINK_GetHardwareVersion() returns 0x18A88 (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_EMU_HasCapEx(0x00000026) returns 0x00 (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_EMU_GetProductId() (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_GetHardwareVersion() returns 0x18A88 (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_GetFirmwareString(...) (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_EMU_HasCapEx(0x00000044) returns 0x01 (0000ms, 2527ms total)
    T0D6C 002:550 JLINK_ReadEmuConfigMem(..., Off = 0x9A, NumBytes = 0x01) returns 0x00 (0001ms, 2528ms total)
    T0D6C 003:939 JLINK_Api_MRU_GetList()JLINK_DEVICE_GetIndex(sDeviceName = ATSAMA5D27)XML file found at: C:\Program Files (x86)\SEGGER\JLink_V634g\JLinkDevices.xml (0001ms, 2533ms total)
    T0D6C 004:717 C:\Program Files (x86)\SEGGER\JLink_V634g\JLinkDevices.xml evaluated successfully. returns 321 (0119ms, 2651ms total)
    T0D6C 004:836 JLINK_DEVICE_GetInfo(DeviceIndex = 321) returns 0 (0000ms, 2651ms total)
    T0D6C 005:171 JLINK_ConfigJTAG(IRPre = -1, DRPre = -1) (0000ms, 2651ms total)
    T0D6C 005:347 JLINK_ExecCommand("device=ATSAMA5D27", ...). Device "ATSAMA5D27" selected. returns 0x00 (0009ms, 2660ms total)
    T0D6C 005:356 JLINK_EnableLog(...) (0000ms, 2660ms total)
    T0D6C 005:358 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 2660ms total)
    T0D6C 005:358 JLINK_TIF_GetAvailable(...) (0000ms, 2660ms total)
    T0D6C 005:358 JLINK_TIF_Select(JLINKARM_TIF_JTAG) returns 0x00 (0006ms, 2666ms total)
    T0D6C 005:364 JLINK_SetSpeed(4000) (0001ms, 2667ms total)
    T0D6C 005:365 JLINK_Connect() J-Link Script File: Executing ConfigTargetSettings() ---Setting ETB available------Setting ETB Base Address------Setting ETM Base Address--- >0x2F8 JTAG>TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 >0xC8 JTAG>RESET (pin 15) high, but should be low. Please check target hardware. J-Link Script File: Executing ConfigTargetSettings() ---Setting ETB available------Setting ETB Base Address------Setting ETM Base Address--- >0x2F8 JTAG>
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 >0xC8 JTAG> returns 0x01 (0389ms, 3056ms total)
    T0D6C 005:754 JLINK_GetIdData(...) J-Link Script File: Executing ConfigTargetSettings() ---Setting ETB available------Setting ETB Base Address------Setting ETM Base Address--- >0x2F8 JTAG>TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 >0xC8 JTAG>RESET (pin 15) high, but should be low. Please check target hardware. J-Link Script File: Executing ConfigTargetSettings() ---Setting ETB available------Setting ETB Base Address------Setting ETM Base Address--- >0x2F8 JTAG>
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 >0xC8 JTAG> (0401ms, 3457ms total)
    T0D6C 007:222 JLINK_IsOpen() returns 0x01 (0000ms, 3457ms total)
    T0D6C 007:243 JLINK_Close() (0012ms, 3469ms total)
    T0D6C 007:243 (0012ms, 3469ms total)
    T0D6C 007:243 Closed (0012ms, 3469ms total)
  • Hello,


    40490FDB wrote:

    The connector I use is an Atmel part.
    Please understand that we can't guarantee functionality with third party adapters. Make sure to either use the one shipped with J-Link or one from our shop.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/
  • Hello,

    Great to hear that you are up and running again.
    This thread will be closed now.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/