thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Fri, 11 Apr 2025 13:22:53 GMT

you manage to get the Thingy with the Edge impulse FW discovered any usable as intended now?

Yes

Note.:

I'm waiting for Zephyr 3.7.99 (or latest available version) on thingy53 now

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Fri, 14 Mar 2025 15:51:16 GMT

Asbjørn Vojislav https://forum.edgeimpulse.com/t/thingy53-with-zephyr-never-appear-in-nrf-edge-impulse-android-app/13410

I'm waiting for Zephyr 3.7.99 (or latest available version) on thingy53 now

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Fri, 14 Mar 2025 13:22:20 GMT

Hello,

Q2: Glad you've found a way forward to bring the bootloader back.

Based on the follow up by you about deleting the pairing, you manage to get the Thingy with the Edge impulse FW discovered any usable as intended now?

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Wed, 05 Mar 2025 16:11:04 GMT

2) Why didn't I have to press sw2 when I changed sw1 from off to on?

This has been resolved and now I can do the procedure. Press sw2 and put sw1 in the ON position and I have the thingy53 in bootloader mode. I think I put a picture of this up there.

Regarding having the EDGE IMPULSE firmware with the latest available version of the zephyr on this computer (3.7.99) (I prepared the computer last week only for zephyr and thingy53) I get errors but I can upload the EDGE Impulse firmware in an old version (via docker) from this link: github.com/.../firmware-nordic-thingy53. And I can use the nRF EDGE impulse app to register trainings:

github.com/.../30

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Wed, 05 Mar 2025 12:00:08 GMT

Hello,

Q1: If you didn't have the Jlink Mini you could have ended up needing to get one to get back on track. The bootload in nRF53 Thingy should have been working and made it recoverable, but it's not safe from errors. We do see others that are using the Thingy variant make good use of it, but often end up getting an external debugger if they don't have another nordic DK, just because the added value of having debugging capabilities. Thingy gives you lots of features, but if you get into the corner where you did, you get stuck unless you have another programming solution.

Q2: I'm not sure what changed in between here, but it looks like the trigger for the bootloader was changed as well in the FW or the modifications you've done to the thingy board makes the button seems to be pushed all the time? Not really clear to me either what has happened, but one or both of these would be my suspects.

Edge impulse FW, I'm not sure I understand you here, your compilation of the code in the NCS 2.8.0 fails with the nRF53Thingy as build configuration? Did you update the NCS version you use compared to previous attempts?

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Mon, 03 Mar 2025 17:19:24 GMT

Asbjørn Please, don't you have anything else to say about this specific topic?

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Tue, 25 Feb 2025 02:20:28 GMT

https://www.youtube.com/watch?v=7WNH-fSC9PY

As you can see in the video above, I have some news.

I followed this video and made the blink led(using JLink Mini Edu):

https://www.youtube.com/watch?v=qNQ7tH7vga0&t=567s

Next, I changed PC, removed the JLink mini edu connections and connected the USB cable (without even pressing sw2) and thingy53 finally appeared on that screen (nrf connect for desktop -> Programmer)

Then I uploaded and wrote the dfu_application.zip(blink led app) and the rest is in the video I posted at the beginning of this answer.

The questions that remain are:

1) What if I had bought the thingy53 today and didn't have the JLink Mini Edu?

2) Why didn't I have to press sw2 when I changed sw1 from off to on?

note-01:

I need to rectify this post above (as per photo below) since I had to press sw2 to burn the firmware (Phew! I entered Bootloader mode) on the nordic thingy53 for edge impulse and now I have a new problem (both using USB-C and using JLing Mini Edu) the firmware for thingy53 for edge impulse is outdated for zephyr 3.7.99)

Configuration saved to 'C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/b0n/zephyr/.config' Kconfig header saved to 'C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/b0n/zephyr/include/generated/zephyr/autoconf.h' -- Found GnuLd: c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38") -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- The ASM compiler identification is GNU -- Found assembler: C:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe -- Setting build type to 'MinSizeRel' as none was specified. CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:2134 (message): __ASSERT() statements are globally ENABLED -- Configuring done -- Generating done -- Build files have been written to: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/b0n -- *************************************************** * Running CMake for firmware-nordic-thingy53-main * *************************************************** Loading Zephyr default modules (Zephyr base). -- Application: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main -- CMake version: 3.21.0 -- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter -- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache -- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr) -- Found west (found suitable version "1.2.0", minimum required is "0.14.0") -- Board: thingy53, qualifiers: nrf5340/cpuapp -- Found host-tools: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk) -- Found toolchain: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk) -- Found Dtc: C:/ncs/toolchains/b620d30767/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6") -- Found BOARD.dts: C:/ncs/v2.8.0/zephyr/boards/nordic/thingy53/thingy53_nrf5340_cpuapp.dts -- Found devicetree overlay: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/boards/thingy53_nrf5340_cpuapp.overlay 'label' is marked as deprecated in 'properties:' in C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/drivers/vm3011/dts/bindings\vesper,vm3011.yaml for node /soc/peripheral@50000000/i2c@9000/vm3011@60. 'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\serial\zephyr,cdc-acm-uart.yaml for node /soc/peripheral@50000000/usbd@36000/cdc_acm_uart0. node '/soc/peripheral@50000000/i2c@9000/vm3011@60' compatible 'vesper,vm3011' has unknown vendor prefix 'vesper' -- Generated zephyr.dts: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/firmware-nordic-thingy53-main/zephyr/zephyr.dts -- Generated devicetree_generated.h: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/firmware-nordic-thingy53-main/zephyr/include/generated/zephyr/devicetree_generated.h -- Including generated dts.cmake file: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/firmware-nordic-thingy53-main/zephyr/dts.cmake Parsing C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/Kconfig Loaded configuration 'C:/ncs/v2.8.0/zephyr/boards/nordic/thingy53/thingy53_nrf5340_cpuapp_defconfig' Merged configuration 'C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/prj.conf' Merged configuration 'C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/boards/thingy53_nrf5340_cpuapp.conf' Merged configuration 'C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/firmware-nordic-thingy53-main/zephyr/.config.sysbuild' error: NRFX_PDM (defined at C:/ncs/v2.8.0/zephyr/modules/hal_nordic\nrfx/Kconfig:168, modules\hal_nordic\nrfx/Kconfig:168) is assigned in a configuration file, but is not directly user- configurable (has no prompt). It gets its value indirectly from other symbols. See docs.zephyrproject.org/.../kconfig.html and/or look up NRFX_PDM in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too. CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/kconfig.cmake:396 (message): command failed with return code: 1 Call Stack (most recent call first): C:/ncs/v2.8.0/nrf/cmake/modules/kconfig.cmake:29 (include) C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include) C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include) C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate) CMakeLists.txt:50 (find_package) -- Configuring incomplete, errors occurred! CMake Error at cmake/modules/sysbuild_extensions.cmake:514 (message): CMake configure failed for Zephyr project: firmware-nordic-thingy53-main Location: C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main Call Stack (most recent call first): cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake) cmake/modules/sysbuild_default.cmake:20 (include) C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include) C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate) C:/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include) template/CMakeLists.txt:10 (find_package) -- Configuring incomplete, errors occurred! See also "C:/Users/neube/Downloads/NORDIC/firmware-nordic-thingy53-main/build/CMakeFiles/CMakeOutput.log". FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/b620d30767/opt/bin/python.exe '-Bc:\Users\neube\Downloads\NORDIC\firmware-nordic-thingy53-main\build' -GNinja -DBOARD=thingy53/nrf5340/cpuapp -DNCS_TOOLCHAIN_VERSION=NONE '-DBOARD_ROOT=c:/workspace/blinky;c:/users/neube/downloads/nordic/firmware-nordic-thingy53-main' '-SC:\ncs\v2.8.0\zephyr\share\sysbuild' '-DAPP_DIR:PATH=c:\Users\neube\Downloads\NORDIC\firmware-nordic-thingy53-main' * The terminal process terminated with exit code: 1. * Terminal will be reused by tasks, press any key to close it.

note-02: forum.edgeimpulse.com/.../13410

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Wed, 19 Feb 2025 12:50:54 GMT

Hello,

It seems like you've had your attempt at replacing the button, but if the device isn't going into bootloader mode it could be that the bootload is lost or damaged as well as part of all of this. I'd encourage you to find a programmer and connect it to the thingy53 and reprogram the bootload if that's the preferred way to interact with it or use the Segger programmer to just program it all in all.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/thingy53/building_thingy53.html#building_and_programming_using_visual_studio_code

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Mon, 17 Feb 2025 15:46:13 GMT

I need video or something else that shows this: steps: 1) I press the sw2 button, 2) with sw2 pressed I change the switch from Off to On, 3) Always with the nrf connect desktop open, but I never see the Bootloader_thingy53, Working. Excuse my incredulity

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Thu, 13 Feb 2025 13:50:58 GMT

Do you still have the Segger device? That could be used for programming the thingy. If not, then if for some reason you have one of our development kits, they could also be used to program the Thingy if for some reason the bootload is erased or not recoverable.

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Mon, 10 Feb 2025 15:42:38 GMT

" maybe something else might be wrong in addition and that the DFU functionality isn't possible to recover anymore for some reason? " Maybe.

" Have you connected a programmer to the thingy in some way? " I have mini edu debugger segger from adafruit and I have access in thingy53 from it (mini edu jlink).

From Year Ago I used thingy53 with segger mini edu

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Mon, 10 Feb 2025 15:25:01 GMT

Hi,

So the button push doesn't out the device back into DFU mode at all? I thought you meant that with the button broken it was now difficult or not possible to put the thingy into DFU mode, but it sound now that maybe something else might be wrong in addition and that the DFU functionality isn't possible to recover anymore for some reason? Have you connected a programmer to the thingy in some way? What was the last FW update you did across DFU and was it successful?

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Fri, 07 Feb 2025 11:09:54 GMT

I need to say that I need a video just for that: ""replicate the functionality of the button on your board."

Evidently, I saw this picture. You say: "You need to short one of the bottom two corners to one of the top two corners"

The button already conducts (on the continuity scale, beep, of the multimeter) in this region, that is, in the parallel from top to bottom. So, connecting the wires ai would not solve anything after pressing the button. I made the wire connections, etc... And just lastly, I soldered the wires to the button, hoping that with the 4 wires connected, it would work. But it never works and then I asked for a video

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Fri, 07 Feb 2025 09:53:28 GMT

Hello,

I wish I could assist you with making a video on how to replace or replicate the functionality of the button on your board. We don't have the capacity to do that.

I assume you've had a look at the button layout as shown below. You need to short one of the bottom two corners to one of the top two corners (from the view of this picture). That's how the button works. It pull the gpio connected to SW2 down to indicate that it's been pressed.

How have you installed the new button? Is it a button the holds the connection or is it a click and release button? You don't need to have the button there, you can just hold two wires together to replicate the button push.

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Fri, 07 Feb 2025 02:57:01 GMT

Pls. I need video in youtube (from nordic) Showing (successfully performing these steps)steps: 1) I press the sw2 button, 2) with the sw2 pressed I change the switch from Off to On, 3) Always with the nrf connect desktop open

I'm not sure if that's really possible, at least for me here

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Wed, 05 Feb 2025 18:20:34 GMT

I soldered a button on the 4 wires (as pictured)

I have all the indexes on the continuity scale (beep) on the multimeter. OK.

I follow the steps: 1) I press the sw2 button, 2) with the sw2 pressed I change the switch from Off to On, 3) Always with the nrf connect desktop open, but I never see the Bootloader_thingy53. I've tested it on 2 different computers and with different USB-c cables, too

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Wed, 05 Feb 2025 14:21:05 GMT

The layout, schematic and BOM for the Thingy53 can be found here: https://nsscprodmedia.blob.core.windows.net/prod/software-and-other-downloads/dev-kits/thingy-53/hardware-files/thingy53---hardware-files-1_1_0.zip

This link is found under the "Download" tab on the thingy53 product page here: https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-53/Downloads?lang=en#infotabs

Best regards

Asbjørn

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

neuberfran — Tue, 04 Feb 2025 23:17:04 GMT

I need you to detail me (with pictures of the links) this region of the board (sw2 button) so I know what other smd button I can put in place or what tiny regions I should solder tiny wires to be able to short circuit

RE: thingy:53 I have damage to the sw2 pin and I am unable to enter the DFU

Asbjørn — Tue, 04 Feb 2025 10:06:11 GMT

Hello,

I'm not sure what's happened to your switch, but if it doesn't work anymore either you would have to short it in another way or removed it and solder on a new one. If you have a soldering iron, I think at this point it's better to removed the damage button and you can short the connections underneath the button with some small piece of conducting metal.

Best regards

Asbjørn