Need Help Setting Up Xiao BLE with nRF Connect for VSCode - USB Flashing

[QBSho]

Hello, community!

I'm currently trying to set up a Xiao BLE module (based on the nRF52840) for development using the nRF Connect extension in Visual Studio Code. I've been following various guides and documentation to ensure my configuration is correct, but it seems like I'm missing something crucial, as I can't get my setup to work properly.

Here's what I've done so far:

• I've installed the nRF Connect for VSCode extension and configured it according to the official documentation.
• My goal is to flash the Xiao BLE using the USB port, as I don't have access to a J-Link or SWD debugger. I've found some resources indicating that it's possible to flash nRF52840 devices using UF2 via USB, as detailed in this guide: Flash nRF52840 Using UF2 - No More Copy-Paste. This approach seems perfect for my situation.

Despite following the steps and ensuring my configurations align with the recommendations, I'm unable to successfully flash the device. Here are some specifics about my setup and the issues I'm encountering:

• Board Configuration: I've selected the appropriate board and settings in the nRF Connect extension, but I'm unsure if additional configuration is needed to support UF2 USB flashing for the Xiao BLE.
• Flashing Process: When attempting to flash the device, I either receive errors indicating the device cannot be found, or the process begins but never completes successfully.

I'm reaching out to see if anyone here has experience with this setup and can offer advice on the following:

1. Configuration Tips: Are there any specific settings or configuration steps I've overlooked for using the Xiao BLE with nRF Connect and UF2 USB flashing?
2. Troubleshooting Steps: Any common pitfalls or troubleshooting steps I can take to resolve connectivity or flashing issues?
3. Alternative Methods: If my current approach is flawed, are there any alternative methods recommended for flashing the Xiao BLE without a hardware debugger?
   
   
   
   

I appreciate any insights or advice you can provide. 

Thank you in advance for your help!

[Kenneth]

Hello,

I don't have any experience with the board in mention, but in general I always recommend to also have an nRF DK available in parallell for comparison, also the DK allow programming and debugging of third party nRF modules through the SWD interface. The typical price for an nRF52840-DK is $49. I think it's a well worth investment.

I could find a description in the zephyr documentation on how to use your board that you may try out:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/boards/arm/seeeduino_xiao/doc/index.html#programming-and-debugging 

Kenneth

[QBSho]

Hello Kenneth, 

thanks. I works partly with west build by integrated the workspace.
Indeed it makes sense to use the nRF52840-DK as I wrote the post it was already ordered, but can't wait to code.
It will arrive in 3 days - so i have to wait or copy it manual to the device.

[PjGlasso]

Hi there,

Might sound stupid , but have put into Bootloader mode(pressing the reset fast Twice) a drive will appear , then drag your Udf2 file to the drive. Reset again and , done. Rinse and repeat!

HTH

GL :-) PJ

[alefalfa]

To streamline the process a bit, I ended up wrapping it in a bash function so I can just run flash from the terminal after building. Here’s what I’m using in my .zshrc

flash() {

    local SOURCE_PATH="./build/zephyr/zephyr.uf2"

    local DEST_PATH="/Volumes/XIAO-SENSE"

    if [[ ! -f "$SOURCE_PATH" ]]; then

    echo "Error: Source file '$SOURCE_PATH' not found."

        return 1
    fi

    if [[ ! -d "$DEST_PATH" ]]; then

    echo "Error: Destination volume '$DEST_PATH' not found. Is it mounted?"

    return 1

    fi

    cp "$SOURCE_PATH" "$DEST_PATH" 2>/dev/null

}

Still have to double-tap reset to enter bootloader mode, but this saves me from drag-and-dropping every time :)