• State Not Answered
  • Replies 11 replies
  • Subscribers 73 subscribers
  • Views 2224 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249768
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SWD with Tag-Connect on Thingy: 52

Noon

Hello,

i've made a custom shield plugged into the thingy: 52. 

There is a tag connect connector on it. I have short SWD signal from thingy debug connector.

When i try to flash the code i have the following error:

2020-05-18T11:28:26.450Z DEBUG App path: C:\Users\arnau\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2020-05-18T11:28:26.450Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.3.0)
2020-05-18T11:28:26.450Z DEBUG nRFConnect path: C:\Users\arnau\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-05-18T11:28:26.450Z DEBUG HomeDir: C:\Users\arnau
2020-05-18T11:28:26.450Z DEBUG TmpDir: C:\Users\arnau\AppData\Local\Temp
2020-05-18T11:28:26.464Z INFO Using nrfjprog library 10.8.0, pc-nrfjprog-js 1.7.2
2020-05-18T11:28:26.465Z VERBOSE Could not fetch serial number for serial port at COM3
2020-05-18T11:28:26.465Z VERBOSE Could not fetch serial number for serial port at COM8
2020-05-18T11:28:28.283Z INFO Using nrfjprog to communicate with target
2020-05-18T11:28:28.614Z INFO Using J-Link Software version 6.70
2020-05-18T11:28:30.264Z INFO Segger serial: 260115611
2020-05-18T11:28:30.264Z INFO Segger speed: 2000 kHz
2020-05-18T11:28:30.264Z INFO Segger version: J-Link V10 compiled Apr 16 2020 17:17:24
2020-05-18T11:28:30.274Z INFO Core probed: 260115611.
2020-05-18T11:28:30.274Z INFO Core RAM: 64KiB.
2020-05-18T11:28:30.274Z INFO Core ROM: 512KiB in pages of 4KiB.
2020-05-18T11:28:32.899Z ERROR Error when closing nrfjprog: Error: Error occured when close opened device. Errorcode: CouldNotResetDevice (0x5)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

2020-05-18T11:28:32.899Z INFO Model: NRF52832_xxAA_REV1.
2020-05-18T11:28:32.905Z ERROR Error when getting device info: Error: Error: Error occured when open device long term. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: INVALID_OPERATION (fffffffe)

2020-05-18T11:28:32.906Z DEBUG getDeviceMemMap: r is not iterable
2020-05-18T11:28:32.908Z ERROR Error when closing nrfjprog: Error: Error occured when close opened device. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: INVALID_OPERATION (fffffffe)

Do you have an idea of what happened?

Arnaud

Parents
  • 0

    Hi, 

    i've made a custom shield plugged into the thingy: 52. 

    How does the custom shield connect to the thingy:52? Will it affect the voltage?

    Have you tried recovering the device using nrfjprog directly?  This can be done by issuing "nrfjprog --recover -f nrf52" with nRF-Command-Line-Tools.

    -Amanda H. 

  • 0 in reply to Amanda Hsieh

    The shield isn't supposed to affect the voltage...

    Everythings works fine when i flash/debugg from the thingy connector.

    If i try recovering the device using nrfjprog, i have this error:

    Recovering device. This operation might take 30s.
    ERROR: Recover failed. Please make sure that the correct device family is given
    ERROR: and try again.

    After, that Vdd is about 0,8 Volts.

  • 0 in reply to Noon

    Hi Cazale, 

    What is the VTref value showed in the J-Link Commander? Is it 3.3V?

    -Amanda H.

  • 0 in reply to Noon

    Hi Cazale, 

    i've made a custom shield plugged into the thingy: 52. 

    What is the custom shield for? Does it contain an nRF chip? How do you connect the custom shield and the thingy52?

    There is a tag connect connector on it. I have short SWD signal from thingy debug connector.

    Did you connect the thingy: 52 connect nRF DK with the 10-pin tag connect connector? 

    Not sure what you mean by "short". Could you elaborate on more detail? Why do you "shot" the SWD signal from the thingy debug connector? Which SWD signal have you "short", SWDIO and SWDCLK?

    Could nRF Connect programmer work on the thingy52 without the custom shield plugging in?

    -Amanda H. 

  • 0 in reply to Amanda Hsieh

    What is the custom shield for? Does it contain an nRF chip? How do you connect the custom shield and the thingy52?

    The custom shield is for monitoring force sensors. The shield is composed of some multiplexer a, digital potentiometer and amplifier. There is no nRF chip on it. All chips are I2C. The shield is connected to the Thingy throught connector P4 (VDD,GND,SCL,SDA and P0.02 for ADC_IN).

    Did you connect the thingy: 52 connect nRF DK with the 10-pin tag connect connector? 

    Yes

    Not sure what you mean by "short". Could you elaborate on more detail? Why do you "shot" the SWD signal from the thingy debug connector? Which SWD signal have you "short", SWDIO and SWDCLK?

    I have short SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors onb to top of the shield. It allow me to programm and debug from the top of the shield instead of the edge of the thingy (it's a bout a case problem).

    Could nRF Connect programmer work on the thingy52 without the custom shield plugging in?

    Everithing works great when the shield is plugged on the thingy and the programmer is plugged into the thingy programm connector.. Programmer doesn't work if i use the tag connect connector on the top of the shield.

    I hope to be clear...

  • 0 in reply to Noon

    Hi Cazale,

    Noon said:
    I have short SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors onb to top of the shield. It allow me to programm and debug from the top of the shield instead of the edge of the thingy (it's a bout a case problem).

    It is still unclear for me to the "short". Do you mean that you connect the SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors on the top of the shield? If so, why would you want to use the 10 Pins connectors on the top of the shield? Are you able to use J-Link Commander to connect the thingy 52 via the 10-Pins connectors on the shield?  Is the previous J-Link Command log with connecting the connectors on the shield?

    What is the VTref value showed in the J-Link Commander while connecting with the 10-Pins connectors on the shield? In the previous log, it didn't include that. 

    -Amanda H.

Reply
  • 0 in reply to Noon

    Hi Cazale,

    Noon said:
    I have short SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors onb to top of the shield. It allow me to programm and debug from the top of the shield instead of the edge of the thingy (it's a bout a case problem).

    It is still unclear for me to the "short". Do you mean that you connect the SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors on the top of the shield? If so, why would you want to use the 10 Pins connectors on the top of the shield? Are you able to use J-Link Commander to connect the thingy 52 via the 10-Pins connectors on the shield?  Is the previous J-Link Command log with connecting the connectors on the shield?

    What is the VTref value showed in the J-Link Commander while connecting with the 10-Pins connectors on the shield? In the previous log, it didn't include that. 

    -Amanda H.

Children
  • 0 in reply to Amanda Hsieh

    Do you mean that you connect the SWD signals (SWDIO and SWDCLK) from thingy SWD connector to a tag-connect 10 Pins connectors on the top of the shield ?

    Yes.

    If so, why would you want to use the 10 Pins connectors on the top of the shield ?

    Because the shield an thingy will be in a case, and only the top of the shield will be accessible.

    Are you able to use J-Link Commander to connect the thingy 52 via the 10-Pins connectors on the shield?

    Yes, i can "coonect", but when i download code, the transfert stop, as the previous Link Command log show.

    What is the VTref value showed in the J-Link Commander while connecting with the 10-Pins connectors on the shield?

    The VTref value is 3.3V when i connect, after trying flashing code, i have an error, and the Vref value is about 0,6 V. I have to reset before retrying to connect.

  • 0 in reply to Noon

    Hi,

    Noon said:
    after trying flashing code, i have an error, and the Vref value is about 0,6 V.

    I think this is the issue. What is the code related? What is the error code? Does it also happen when you use the thingy SWD connector to flash the code? You should figure out what caused the Vref dropdown and fix it.  

    -Amanda H.

Related
Terms of service