Suggestions about the Wiki Websites

[MatthewJeffson]

Welcome to our product documentation platform! We value user feedback and contributions, so we couldn’t be more grateful that you can help us improving the documentation.

Hence, if you find obvious errors in the product documentation, or you have additional ideas and insights about using products, please contribute to us.

As you may guess already, once you comment at the bottom of the wiki, a new discussion will arise here in the GitHub 'Discussions' channel. We want this function alive, as presenting the questions and solutions regarding the product you are looking at.

Nonetheless, we hope you find it helpful with the help of others. We will clean it up on a monthly basis.

[SoothingMist]

Am developing proofs-of-concept in precision irrigation (https://github.com/SoothingMist). Have successfully used Seeed sensors in LoRa remote monitoring. Want now to demonstrate Arduino Mega 2560 and sending complex data structures via LoRa. The sensor in question is an RGB camera. To date, I have been unable to find a combination of Mega, LoRa, and camera that is workable. Incombatibilities prevent the combinations tried to date. Does Seeed offer a camera/lora "kit" that is compatible with the Arduino Mega 2560?

[MatthewJeffson]

Hi, it indeed is an interesting idea. If you want to build it with us together, you can refer to here for getting more help!
Regards!

[mneuhaus]

I really love your little Seeed Modules, i'd love to use them for some projects, but sadly i'm currently running around it in circles because somehow i'm either to stupid or there are some problems deeper down i can't figure out.

i'd love to use these Modules, especially the esp32c3 and esp32s3 with [ESPHome)(https://esphome.io/) and i saw, that you have a small example for the C3 Variant in the Wiki, sadly both of these boards seem to be quite unreliable running ESPHome, either they don't boot at all, go into bootloops, don't connect to Wifi, etc.

I also had quite some problems to actually get logs out of these little boards through the usb connection because of the serial chip used, with the arduino platform i mostly got really low level bootloader logs that did not really help, the jtag/cdc was kinda only available with the esp-idf platform which on the other hand doesn't support the webserver yet.

Could you please create a working example with working wifi/bluetooth & webserver for the s3 and c3 boards, that would be so awesome and also open these budget friendly little boards to so many possibilites.

Thank you!

[MatthewJeffson]

Thank you for your interest in our products! Our development is progressing according to plan. :D

[mneuhaus]

Hey, i'm not really sure what you want to convey with that message, are there documentations/examples in development right now for esphome?

[MatthewJeffson]

We are developing various application examples based on our boards, take esphome as examples:
1. Using "24GHz mmWave Human Static Presence Module Lite" and "XIAO ESP32C3" to build a Home Assistant with human presence detection.
2. Using all kinds of Grove modules and "ODYSSEY board" and "XIAO ESP32C3" to connect Grove modules to Seeed Studio XIAO ESP32C3 so that users can display sensor data or control the devices using Home Assistant
We are developing all kinds of applications, according to our plan, including but not limited to the esphome.
Hope this can make it clearer. :D

[jims1234]

I just received a few XAIO ESP32 C3 devices and a " Grove Beginner Kit for Arduino" and am very excited to learn more using them. But, frankly was taken back by the fact that the sensor kit is seems entirely dependent on use of your Arduino UNO clone board to interface them thru it ( while I want to wire C3 modules directly to each sensor module instead.) And, so far the only ESP23 C3 compatible demo code seems to be wrapped around a very complex ( to me) Home Assistant iOT Network app that I don't need or want right now..

In spite of that.. I am very encouraged by what I see here in this Wiki including some detail on some of the sensor modules and their pin-outs, data sheet and sample code so I hope I can make progress in figuring hot how to use these very cool little modules like the XIAO ESP32 C3 directly with sensors.

[MatthewJeffson]

Hi, we will try to make our wiki as better as possible and provide more detailed content so you can use it more conveniently and clearly.
If you have good ideas, you are welcome to submit(pull request) them to us.

[MatthewJeffson]

Welcome to our product documentation platform! We value user feedback and contributions, so we couldn’t be more grateful that you can help us improving the documentation.

Hence, if you find obvious errors in the product documentation, or you have additional ideas and insights about using products, please contribute to us.

If you need technical support, you can email it to fae@seeed.cc.

If you want to discuss the product, I recommend the Seeed Studio Forum and Seeed Studio Discord Channel

The "Discussion channel" in Github here is a relatively new addition and may not receive much attention.

Nonetheless, we hope you find it helpful with the help of others. We will clean it up on a monthly basis.

[Parkre01]

I got my MPU5060 accelerometer working (thru I2C) but now, I cannot for the life of me figure out how to get the MQTT protocol working. Any directions or tuturials would be extremely helpful.

[johnpiker]

Why I am not able to start the recording wen i plug the ESP32 S3 to the power plug

[faizannazir]

Nrf52 library mentioned in documentation is not available in arduino ide library manager and zip file link is not provided in ddocumentation

[Yjppj]

The echo cancellation effect of Respeaker Mic v2 is very poor

[thecalle]

I'm developing a software with "fluent talking" using a SpeexAEC based on libspeexdsp.so on Respeaker Mic v2. Software echo cancellation is really difficult because card echo cancellation is really poor as told by @Yjppj .
I need to stop an AI speaker during dialogue when the card is playing the answer to a question and the answer is annoying or too long. The idea is simple = SPEAKER AUDIO - (SPEAKER AUDIO captured by the microphone) = USER AUDIO.
If user audio level is over the background noise taken during silence time slots, the SPEAKER stops and starts to listen to the USER again. This process is now a day used by any AI audio interface such as Gemini or ChatGPT when the live mic button is pressed.
Any suggestions? Can the CHIP be programmed (via I2C or else) to accommodate this requirement. The current setup seems more telephony oriented instead of room speaker oriented.

[jamesdinsmore]

I found a code error on the Grove Light Sensor Wiki for the Arduino code:
It reads:
#include <Grove_LED_Bar.h>

Grove_LED_Bar bar(3, 2, 0); // Clock pin, Data pin, Orientation
it should be:
#include <Grove_LED_Bar.h>
Grove_LED_Bar bar(3, 2, 0, LED_BAR_10); // Clock pin, Data pin, Orientation

Without the LED_BAR_10 it will not work.

James

[djairjr]

I adapted Marcelo Rovai's code using the Seeed Xiao ESP32-S3 Sense and the Round Display to display bounding boxes on the display while detecting objects using Edge Impulse Arduino Library.

In my case, I noticed that the bounding boxes were appearing very small on the TFT display. After much investigation, I understood that, although the camera was set to a frame size of 240x240, somehow the coordinates on the display did not reflect this and gave the impression of being set to the camera's maximum resolution of 1600x1200. That's why I had to make the compensation, multiplying the width by 6 (6,667....) and the height by 5.

Here is my code:

/* Adding TFT Support Libraries */
#include <Arduino.h>
#include <TFT_eSPI.h>
#include <SPI.h>

/* Adding Edge Impulse Inferencing Library */
#include <Add_Your_inferencing_here.h> // Remember to change this line!
#include "edge-impulse-sdk/dsp/image/image.hpp"

/* Adding ESP32S3 Sense Camera Support */
#include "esp_camera.h"

#define CAMERA_MODEL_XIAO_ESP32S3 // Has PSRAM

#define PWDN_GPIO_NUM     -1
#define RESET_GPIO_NUM    -1
#define XCLK_GPIO_NUM     10
#define SIOD_GPIO_NUM     40
#define SIOC_GPIO_NUM     39
#define Y9_GPIO_NUM       48
#define Y8_GPIO_NUM       11
#define Y7_GPIO_NUM       12
#define Y6_GPIO_NUM       14
#define Y5_GPIO_NUM       16
#define Y4_GPIO_NUM       18
#define Y3_GPIO_NUM       17
#define Y2_GPIO_NUM       15
#define VSYNC_GPIO_NUM    38
#define HREF_GPIO_NUM     47
#define PCLK_GPIO_NUM     13

#define TOUCH_INT D7

/* Original EDGE IMPULSE example parameters 
*  Change Camera Capture to display same size as TFT 
*/
#define EI_CAMERA_RAW_FRAME_BUFFER_COLS           240
#define EI_CAMERA_RAW_FRAME_BUFFER_ROWS           240
#define EI_CAMERA_FRAME_BYTE_SIZE                 3

/* Private variables */
static bool debug_nn = false; // Set this to true to see e.g. features generated from the raw signal
static bool is_initialised = false;
uint8_t *snapshot_buf; //points to the output of the capture

/* Camera Config Parameters */
static camera_config_t camera_config = {
  .pin_pwdn = PWDN_GPIO_NUM,
  .pin_reset = RESET_GPIO_NUM,
  .pin_xclk = XCLK_GPIO_NUM,
  .pin_sscb_sda = SIOD_GPIO_NUM,
  .pin_sscb_scl = SIOC_GPIO_NUM,

  .pin_d7 = Y9_GPIO_NUM,
  .pin_d6 = Y8_GPIO_NUM,
  .pin_d5 = Y7_GPIO_NUM,
  .pin_d4 = Y6_GPIO_NUM,
  .pin_d3 = Y5_GPIO_NUM,
  .pin_d2 = Y4_GPIO_NUM,
  .pin_d1 = Y3_GPIO_NUM,
  .pin_d0 = Y2_GPIO_NUM,
  .pin_vsync = VSYNC_GPIO_NUM,
  .pin_href = HREF_GPIO_NUM,
  .pin_pclk = PCLK_GPIO_NUM,

  //XCLK 20MHz or 10MHz for OV2640 double FPS (Experimental)
  .xclk_freq_hz = 10000000,
  .ledc_timer = LEDC_TIMER_0,
  .ledc_channel = LEDC_CHANNEL_0,

  /* This config pixel format needed to be the same in function ei_camera_capture ()
                                                        HERE 
     bool converted = fmt2rgb888(fb->buf, fb->len, PIXFORMAT_RGB565, snapshot_buf);

  */
  .pixel_format = PIXFORMAT_RGB565,     //YUV422,GRAYSCALE,RGB565,JPEG
  .frame_size = FRAMESIZE_240X240,      //QQVGA-UXGA Do not use sizes above QVGA when not JPEG

  .jpeg_quality = 12, //0-63 lower number means higher quality
  .fb_count = 2,       //if more than one, i2s runs in continuous mode. Use only with JPEG
  .fb_location = CAMERA_FB_IN_PSRAM, // Frame Buffer in PSRAM - YES!
  .grab_mode = CAMERA_GRAB_WHEN_EMPTY,
};

/* Function definitions ------------------------------------------------------- */
bool ei_camera_init(void);
void ei_camera_deinit(void);
bool ei_camera_capture(uint32_t img_width, uint32_t img_height, uint8_t *out_buf) ;

/* Create TFT_SPI object */
TFT_eSPI tft = TFT_eSPI();

/* Bounding Boxes Coordinates need to be uint32_t in TFTeSPI Library */
uint32_t x;
uint32_t y;
uint32_t w;
uint32_t h;

/**
  @brief      Arduino setup function
*/
void setup()
{
  // put your setup code here, to run once:
  Serial.begin(115200);
  //comment out the below line to start inference immediately after upload
  // while (!Serial);

  /* Init TFT */
  tft.init();
  tft.setRotation(3); // This is needed too. In order to get correct positions for bounding boxes
  tft.fillScreen(TFT_WHITE);

  if (ei_camera_init() == false) {
    ei_printf("Failed to initialize Camera!\r\n");
  }
  else {
    ei_printf("Camera initialized\r\n");
  }

  ei_printf("\nStarting continious inference in 2 seconds...\n");
  ei_sleep(2000);
}

/**
  @brief      Get data and run inferencing

  @param[in]  debug  Get debug info if true
*/
void loop()
{

  // instead of wait_ms, we'll wait on the signal, this allows threads to cancel us...
  if (ei_sleep(5) != EI_IMPULSE_OK) {
    return;
  }

  snapshot_buf = (uint8_t*)malloc(EI_CAMERA_RAW_FRAME_BUFFER_COLS * EI_CAMERA_RAW_FRAME_BUFFER_ROWS * EI_CAMERA_FRAME_BYTE_SIZE);

  // check if allocation was successful
  if (snapshot_buf == nullptr) {
    ei_printf("ERR: Failed to allocate snapshot buffer!\n");
    return;
  }

  /* The signal that will be inferred is this one */
  ei::signal_t signal;
  signal.total_length = EI_CLASSIFIER_INPUT_WIDTH * EI_CLASSIFIER_INPUT_HEIGHT;
  signal.get_data = &ei_camera_get_data;

  /*  Makes the call to the ei_camera_capture function, 
   *  which captures the image to the framebuffer, 
   *  converts the image to the correct format and resizes it. 
  */
  if (ei_camera_capture((size_t)EI_CLASSIFIER_INPUT_WIDTH, (size_t)EI_CLASSIFIER_INPUT_HEIGHT, snapshot_buf) == false) {
    ei_printf("Failed to capture image\r\n");
    free(snapshot_buf);
    return;
  }

  // Run the classifier
  ei_impulse_result_t result = { 0 };

  EI_IMPULSE_ERROR err = run_classifier(&signal, &result, debug_nn);
  if (err != EI_IMPULSE_OK) {
    ei_printf("ERR: Failed to run classifier (%d)\n", err);
    return;
  }

  // Print the predictions to Serial Debug
  ei_printf("TFT Example -  Predictions (DSP: %d ms., Classification: %d ms., Anomaly: %d ms.): \n",
            result.timing.dsp, result.timing.classification, result.timing.anomaly);

#if EI_CLASSIFIER_OBJECT_DETECTION == 1
  bool bb_found = result.bounding_boxes[0].value > 0;

  for (size_t ix = 0; ix < result.bounding_boxes_count; ix++) {
    auto bb = result.bounding_boxes[ix];
    if (bb.value == 0) {
      continue;
    }
    /* 
      commenting this line, just to compare dimensions above
      ei_printf("   %s (%f) [ x: %u, y: %u, width: %u, height: %u ]\n", bb.label, bb.value, bb.x, bb.y, bb.width, bb.height);
    
    */
    
    /* Create Coordinates and Size for Bounding Boxes */
    x = bb.x;
    y = bb.y;
    w = bb.width * 6; // Do compensations. The camera resize the frame to 240x240 but this does not reflect in 
    h = bb.height * 5; // TFT display coordinates. So you need to multiple this values...

    /* Checking Sizes */ 
    ei_printf("BB Coord [ x: %u, y: %u, width: %u, height: %u ]\n",  bb.x, bb.y, bb.width, bb.height);
    ei_printf("TFT Coord [ x: %u, y: %u, width: %u, height: %u ]\n",  x, y, w, h);

    /* Draw Bounding Boxes in Display */
    tft.drawRect (x, y, w, h, TFT_GREEN);
    
  }
  if (!bb_found) {
    ei_printf("TFT Example -     No objects found\n");
   
  }
#else
  for (size_t ix = 0; ix < EI_CLASSIFIER_LABEL_COUNT; ix++) {
    ei_printf("    %s: %.5f\n", result.classification[ix].label,
              result.classification[ix].value);
  }
#endif

#if EI_CLASSIFIER_HAS_ANOMALY == 1
  ei_printf("TFT Example -     anomaly score: %.3f\n", result.anomaly);
#endif


  free(snapshot_buf);

}

/**
   @brief   Setup image sensor & start streaming

   @retval  false if initialisation failed
*/
bool ei_camera_init(void) {

  if (is_initialised) return true;

#if defined(CAMERA_MODEL_ESP_EYE)
  pinMode(13, INPUT_PULLUP);
  pinMode(14, INPUT_PULLUP);
#endif

  //initialize the camera
  esp_err_t err = esp_camera_init(&camera_config);
  if (err != ESP_OK) {
    Serial.printf("Camera init failed with error 0x%x\n", err);
    return false;
  }

  sensor_t * s = esp_camera_sensor_get();
  // This is needed too. In order to get correct positions for bounding boxes
  s->set_vflip(s, 1);
  s->set_hmirror(s, 1);

  is_initialised = true;
  return true;
}

/**
   @brief      Stop streaming of sensor data
*/
void ei_camera_deinit(void) {

  //deinitialize the camera
  esp_err_t err = esp_camera_deinit();

  if (err != ESP_OK)
  {
    ei_printf("Camera deinit failed\n");
    return;
  }

  is_initialised = false;
  return;
}


/**
   @brief      Capture, rescale and crop image

   @param[in]  img_width     width of output image
   @param[in]  img_height    height of output image
   @param[in]  out_buf       pointer to store output image, NULL may be used
                             if ei_camera_frame_buffer is to be used for capture and resize/cropping.

   @retval     false if not initialised, image captured, rescaled or cropped failed

*/
bool ei_camera_capture(uint32_t img_width, uint32_t img_height, uint8_t *out_buf) {
  bool do_resize = false;

  if (!is_initialised) {
    ei_printf("ERR: Camera is not initialized\r\n");
    return false;
  }

  camera_fb_t *fb = esp_camera_fb_get();

  if (!fb) {
    ei_printf("Camera capture failed\n");
    return false;
  }
/*  Write camera captured framebuffer into TFT Display */
  tft.startWrite();
  tft.setAddrWindow(0, 0, EI_CAMERA_RAW_FRAME_BUFFER_COLS, EI_CAMERA_RAW_FRAME_BUFFER_ROWS);
  tft.pushColors(fb->buf, fb->len);
  tft.endWrite();

/*  Pay attention to this PIXFORMAT_RGB565 parameter in camera config. Need to be equal or convertion will fail  */
  bool converted = fmt2rgb888(fb->buf, fb->len, PIXFORMAT_RGB565, snapshot_buf);

  esp_camera_fb_return(fb);

  if (!converted) {
    ei_printf("Conversion failed\n");
    return false;
  }

  if ((img_width != EI_CAMERA_RAW_FRAME_BUFFER_COLS)
      || (img_height != EI_CAMERA_RAW_FRAME_BUFFER_ROWS)) {
    do_resize = true;
  }

  if (do_resize) {
    ei::image::processing::crop_and_interpolate_rgb888(
      out_buf,
      EI_CAMERA_RAW_FRAME_BUFFER_COLS,
      EI_CAMERA_RAW_FRAME_BUFFER_ROWS,
      out_buf,
      img_width,
      img_height);
  }

  return true;
}

static int ei_camera_get_data(size_t offset, size_t length, float *out_ptr)
{
  // we already have a RGB888 buffer, so recalculate offset into pixel index
  size_t pixel_ix = offset * 3;
  size_t pixels_left = length;
  size_t out_ptr_ix = 0;

  while (pixels_left != 0) {
    out_ptr[out_ptr_ix] = (snapshot_buf[pixel_ix] << 16) + (snapshot_buf[pixel_ix + 1] << 8) + snapshot_buf[pixel_ix + 2];

    // go to the next pixel
    out_ptr_ix++;
    pixel_ix += 3;
    pixels_left--;
  }
  // and done!
  return 0;
}

#if !defined(EI_CLASSIFIER_SENSOR) || EI_CLASSIFIER_SENSOR != EI_CLASSIFIER_SENSOR_CAMERA
#error "Invalid model for current sensor"
#endif

[MatthewJeffson]

Wow! @djairjr Djair, this looks really interesting!

[qrstu]

Hello you missed for XIAO ESP32C6 in Wiki that the external antenna gets aktive.
GPIO 3 has to be OUTPUT LOW --> Missing in Wiki
GPIO 14 has to be OUTPUT HIGH
See --> https://forum.seeedstudio.com/t/xiao-esp32c6-switching-between-builtin-and-external-antenna/276374
https://wiki.seeedstudio.com/xiao_esp32c6_getting_started/

[acostach]

Hi @MatthewJeffson , I see the provisioning methods have changed for the J4012 and J3010. These are devices that we support in balenaOS on L4T 35.4.1 and 35.5.0, and we'd like to update to Jetpack 6. Would it be possible to share:

1. The patch on top of standard L4T 36.3 BSP for J4012 and J3010, similar to how it was provided for Jetpack 5 (i.e : "Step 4: Open the file "tegra234-mb2-bct-scr-p3767-0000.dts" and add the following lines under tfc section")

2. The method that should be used for generating UEFI Update capsules in L4T 36.3, so we can provide updates. If you give us the diffs at step 1) we should be able to generate the capsules using standard Jetpack + the Seeed changes.

Thanks!

[MatthewJeffson]

Wow! Thank you @acostach for your kindly offer! We have actually launched the Jetpack Flash for the J401 Carrier Board, i.e.
reComputer J3010, reComputer J3011, reComputer J4011, reComputer J4012 are all supporting Jetpack 6.0 now:D
Best Regards,
Matthew

reComputer J3010 reComputer J3011 reComputer J4011 reComputer J4012

[acostach]

Hi @MatthewJeffson and thanks for the links. I've seen that you launched Jetpack flash but what I would actually need is the patches Seeed applies for J3010 and J4012 on top of the standard Nvidia BSP for Jetpack 6.

We need the diffs or patches, so we can integrate these two devices on Jetpack 6 too, and build UEFI capsule updates to OTA transition from Jetpack 5 to Jetpack 6 for the customers who are already using the J3010 and J4012 in their balena fleets.

Perhaps you could help me by sharing these patches?

Thank you

[acostach]

Just for clarity, the patches we'd need are the same as the ones you already provide for Jetpack 5 at https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/ -> click on JP5.1.2 -> Steps 1 -> 6, i.e:

Here we will use NVIDIA L4T 35.4.1 to install Jetpack 5.1.2 on the reComputer

Step 1: [Download](https://developer.nvidia.com/embedded/jetson-linux-r3541) the NVIDIA drivers on the host PC. The required drivers are shown below:

Step 2: Extract Jetson_Linux_R35.4.1_aarch64 and Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64 by navigating to the folder containing these files, apply the changes and install the necessary prerequisites

tar xf Jetson_Linux_R35.4.1_aarch64
sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64 -C Linux_for_Tegra/rootfs/
cd Linux_for_Tegra/
sudo ./apply_binaries.sh
sudo ./tools/l4t_flash_prerequisites.sh

Now we need to apply a patch from NVIDIA which is needed for JP5.1.2 and explained [here](https://docs.nvidia.com/jetson/archives/r35.4.1/ReleaseNotes/Jetson_Linux_Release_Notes_r35.4.1.pdf) in section 4.2.3 of the official NVIDIA JetPack Release Notes.

Step 3: Navigate to the following directory

cd Linux_for_Tegra/bootloader/t186ref/BCT

Step 4: Open the file "tegra234-mb2-bct-scr-p3767-0000.dts" and add the following lines under tfc section

tfc {
    reg@322 { /* GPIO_M_SCR_00_0 */
    exclusion-info = <2>;
    value = <0x38008080>;
    };

Also, if it's only the reg@322 that needs to be applied on Jetpack 6 too, please let me know.

[Teodor-Ciobanu]

Hi there, great stuff!
I wander if this, or perhaps there is other project which would record a few seconds and based on the recording to trigger if matched found. I mean not voice but some other sound like whistle, claps, multiple knocks...

[techbel]

Hi, I adapted a micropython library for grove I2C motor driver TB6612FNG on ESP32. I especially wanted stepper motor control.
My first project on Github. The main work is done, tested with Thonny IDE and wroom ESP32. I will add examples for basic use.
https://github.com/techbel/ESP32_TB6612FNG

[rei-vilo]

Compiling the example provided at https://wiki.seeedstudio.com/xiao_mg24_sense_built_in_sensor/#code-implementation against Xiao MG24 Sense raises the error

'SPI_CLOCK_DIV4' was not declared in this scope.

See Seeed-Studio/Seeed_Arduino_LSM6DS3#20

[rei-vilo]

One more problem for the example provided at https://wiki.seeedstudio.com/xiao_mg24_sense_built_in_sensor/#code-implementation against Xiao MG24 Sense.

Device error

because according to the schematics, the IMU is connected to pins PB2 PB3 and not default Wire on pins PC4 PC5.

A special condition should be added for the Xiao MG24.

https://github.com/Seeed-Studio/Seeed_Arduino_LSM6DS3/blob/a4a046cec9b1c5dfea994884e521194dabdb29d0/LSM6DS3.cpp#L35-L37

Trying TARGET_SEEED_XIAO_MG24_SENSE does not work.

[nfs0619]

Thank you so much for pointing out the issues. We will look into them and address the concerns. We also highly encourage developers like you to contribute to our project!

You can find more information about becoming a contributor here:

• Contributors Introduction
• Contributor Project Page

We look forward to your participation!

[grilliiiii]

Hi @rei-vilo, The IMU within MG24 Sense is connected to the chip's PDO5(IMU_PW) pin, so the code within the library is not directly usable.

You need to enable PDO5. The correct code we have shown within the Wiki. Then, you can use the built-in IMU normally.
https://wiki.seeedstudio.com/xiao_mg24_sense_built_in_sensor/#code-implementation

[rei-vilo]

Hi @grilliiiii

Thank you for your answer. Actually, I used the code from the wiki and checked the schematics.

I did notice PB5 powered the IMU. The issues were the library was not up to date and had two issues: one undefined constant, wrong Wire port used.

As the example was available on the wiki, I was expecting it to work seamlessly. It is now the case.

[grilliiiii]

Since this library is still needed for another Grove sensor, we did not completely change it to a version compatible with MG24 Sense. I will also go ahead and submit your suggestion to the product manager. We apologize for the inconvenience!

[mhornsby]

Ok thanks so the Wio-WM6180 is for the XIAO ? From: Frank Nie ***@***.***> Date: Tuesday, 4 November 2025 at 4:54 pm To: Seeed-Studio/wiki-documents ***@***.***> Cc: Michael Hornsby ***@***.***>, Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] Suggestions about the Wiki Websites (Discussion #69) Hi Michael, Thanks for your comment! Perhaps you were referring to this Wiki page instead: https://wiki.seeedstudio.com/cn/getting_started_with_wifi_halow_mini_pcie_module/ The link you mentioned earlier is for the XIAO version of the HaLow module. Hope this helps clarify! — Reply to this email directly, view it on GitHub<#69 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEL7I3XX5KTUCSDGPBPZTOT33A5QHAVCNFSM6AAAAAAVYQVB5CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBWGU2TSMQ>. You are receiving this because you commented.

[nfs0619]

Yes, the device in that Wiki page is designed to be used with the XIAO boards.

[LoopOverlord1453]

Dear Seeed Studio Technical Team,

We have purchased two Wio-E5 Development Kits from Digi-Key with the part number 1597-113990934-ND, and we are experiencing range issues in P2P communication. When using the default LoRa settings with the AT firmware that comes preloaded on the devices, we observe good signal levels with RSSI: -2 dBm and SNR: 14. However, when I flash both LoRa devices with the FreeRTOS_LoRaWAN_AT project (Link: Seeed-Studio/LoRaWan-E5-Node at qian provided on your GitHub and linked on the Wio-E5 Dev Kit Wiki page) using STM32CubeProgrammer and run the firmware, the signal quality drops significantly — RSSI starts at around -70 dBm and SNR: 5. I’ve tested all the source code examples from your GitHub in STM32CubeIDE, but unfortunately, the results remain the same. At these signal levels, the communication link drops at about 50 meters.Additionally, when testing with Arduino using the RadioLib library (as discussed in this Seeed Studio Forum post), I again achieve strong signal readings of RSSI: -2 dBm and SNR: 14. Could you please share a working STM32CubeIDE example project for the Wio-E5 Development Kit where the RSSI and SNR values are at normal levels during P2P communication?

Best regards,

[goodbhm]

Hello,

I purchased a Grove Vision AI V2 module (including the camera module).

I tried to run the Gesture Detection model among the pretrained models by following the tutorial.

The USB connection and flashing process completed without any issues.
However, when I click Invoke, I get a “Response timed out” message, and neither the Preview nor the Device Logger appears.

I have confirmed that my USB cable supports data transfer, and I have also verified that the FPCB is correctly connecting the two modules.

Despite this, I have not been able to identify the cause of the issue.

Could you please suggest any troubleshooting steps or methods I could try?

Thank you.

[grilliiiiii]

Hello,

I purchased a Grove Vision AI V2 module (including the camera module).

I tried to run the Gesture Detection model among the pretrained models by following the tutorial.

The USB connection and flashing process completed without any issues. However, when I click Invoke, I get a “Response timed out” message, and neither the Preview nor the Device Logger appears.

I have confirmed that my USB cable supports data transfer, and I have also verified that the FPCB is correctly connecting the two modules.

Despite this, I have not been able to identify the cause of the issue.

Could you please suggest any troubleshooting steps or methods I could try?

Thank you.

Hello, you may try the following steps for troubleshooting:

1. Remove the FPC cable and check whether it is damaged. A damaged cable may also cause issues such as “invoke error” or “Response timed out.”
2. Clear your browser cookies or open the browser in incognito/private mode (Google Chrome is recommended).
3. Please send us a photo of your current FPC connection so we can double‑check it.
4. If possible, try using a different camera module with the Grove Vision AI V2. This cross‑testing will help determine which component is causing the issue.

Thank you for your cooperation!

[RaptorT77]

⚠️ XIAO ESP32-S3 + Expansion Board Base: Short Circuit Risk

Author: Jose Antonio Galicia, HCAA Industrial Automation
Date: February 20, 2026

Issue Summary
Inserting XIAO ESP32-S3 into the Expansion Board Base causes immediate permanent damage due to 3V3-GND short circuit. The board's 4 gold spring pins (designed for SAMD21 SWD pads) contact ESP32-S3 central thermal/strapping pads, creating destructive current surge. Two ESP32-S3 units destroyed.

Root Cause
text
Expansion Board: 4 spring pins → SAMD21 SWD pads (SWCLK, SWDIO, GND, VDD)
XIAO ESP32-S3: Central 4 bottom pads → thermal pad + internal strapping (GPIO0/45/46)
Result: 3V3 ↔ GND short → voltage regulator/chip failure
Solution (100% Effective)
Cover ONLY the 4 central bottom pads of XIAO ESP32-S3 with Kapton tape (0.05mm):

text
Bottom View (cover shaded area only):
┌─────────────────────────────┐
│ [BAT-] [EXPOSED] [BAT+]│ ← Battery pads
│ │
│ ┌──────────────┐ │
│ │ KAPTON TAPE │ │ ← Cover THESE 4 ONLY
│ └──────────────┘ │
│ │
└─────────────────────────────┘
Steps:

Clean pads with IPA

Apply tape precisely over 4 central pads (spares BAT+/- lateral pads)

Insert into Expansion Board (center headers)

Power via USB-C

Verified Functionality Post-Fix
✅ 2x Grove (I2C: GPIO8/9, UART: GPIO16/17)

✅ 0.96" OLED (I2C)

✅ MicroSD (CS=D2/GPIO2)

✅ Buzzer PWM, User button, Servo

✅ RTC + LiPo battery support

Recommendation to Seeed Studio
Add warning to Expansion Board documentation:

ESP32-S3 USERS REQUIRED: Cover 4 central bottom pads with Kapton tape before insertion

Prevents $10 brick per user. Perfect for industrial IoT (sensors + MQTT + battery autonomy).

[limengdu]

Thank you for providing such a thorough analysis and detailed reproduction of this issue — it is very valuable to us.

The problem you've described is indeed a design flaw in the earlier version of the Expansion Board, where the bottom spring pins contact the ESP32-S3's central thermal/strapping pads and cause a short circuit. We have identified this issue and addressed it in subsequent product revisions — the current version of the Expansion Board no longer has this problem.

For users whose XIAO ESP32-S3 units were damaged as a result of this issue, we are happy to provide the necessary after-sales support. If you or any other users have experienced similar damage, please reach out to our technical support team at techsupport@seeed.io, and our after-sales team will assist accordingly.

Thank you again for the detailed feedback and for sharing your workaround solution.

[littlepcgogogo]

Respeaker Lite的USB固件没有回声消除，产品虚假宣传！

[nfs0619]

感谢你的反馈，也抱歉影响了你的使用体验。

Respeaker Lite 本身是支持回声消除功能的。不过我们也注意到，在部分使用场景下回声消除效果还有优化空间。目前团队正在对相关算法进行持续优化，后续会通过固件更新进一步提升效果。

感谢你指出这个问题和提供反馈。

[gitnub-other]

666,你还好意思说

[gitnub-other]

我的评价是不如拼多多上3元的杂牌USB麦克风

[gitnub-other]

我说的是nfs0619

[gitnub-other]

给littlepcgogogo顶上去

[DirkKramer]

Is it possible to upgrade the j501 carrier board with Orin AGX 64gb module to the latest JetPack 6.2.2 for Jetson Orin.

It fixes a CUDA memory allocation bug.

[bleaaach]

Hi, we're sorry but we don't provide version 6.2.2 at the moment. However, we will pass your feedback on to our engineers.

[rommo911]

Technical guidance to replace Secure DFU Bootloader on T1000-E for loraWAN :
Hi ,
I am developing custom firmware for the SenseCAP T1000-E (LoRaWAN). I am currently blocked because the stock Secure DFU Bootloader prevents me from flashing a custom bootloader.uf2 (based on the Adafruit nRF52 repository) via USB DFU U2F.
To enable the community and developers to use their own cryptographic signature keys and custom firmware, we need a way to replace the factory bootloader.
This is essential for those of us needing to move beyond the stock firmware environment.

Would you please advice on best way to achieve this ?

[1cecO1]

We do not recommend this. The Secure DFU Bootloader on the T1000-E is designed to ensure the device's security and stability in LoRaWAN scenarios. Replacing it with a custom bootloader may cause the device to fail to recover or upgrade, and any issues could render it permanently bricked.

[rommo911]

Thank you very much for your reply. this is quit normal that a wrong bootloader could brick the device. as hard as it seems but unfortunately this is very limiting to open source project. user can take responsibility of bricking device, but also user being able to sign application and bootloader is very important.
for example :
current bootloader does not support validating new application signature ( VERY IMPORTANT )
current bootloader does not support OTA over Bluetooth ( jump to bootloader OTA over Bluetooth from application trigger as in latest https://github.com/adafruit/adafruit_nrf52_bootloader ) ESSENTIAL FOR ENABLING OTA
and other features as well.

I believe it could be very helpful, even though dangerous, to get a workaround to flash custom bootloader in order to enable open source community to have at least application signature verification as an essential security feature.

Best regards.

[lhanneus]

Please add a LoRaWan with deepsleep example for the Wio-SX1262 with XIAO ESP32S3 Kit ! Extra & greatly appreciated would be an example wirth wake up on a time basis (ever 15 minutes) AND on an external trigger (an on/off switch for example).

https://wiki.seeedstudio.com/wio_sx1262_xiao_esp32s3_for_lora_sensor_node/

[hack-embed]

Thank you very much for your suggestion.

I have already received your request and feedback regarding the LoRaWAN + deep sleep example for the Wio-SX1262 with XIAO ESP32S3 kit, including the use case with periodic wake-up and external interrupt.

We really appreciate this detailed input. I will forward it to our internal engineering team for further review and possible future documentation or example development.

[mavproductions]

Discord invite invalid?

https://discord.com/invite/QqMgVwHT3X

[Frank-Nie02]

Hi, thanks for reporting this.

We tested the Discord invite link on our side and it appears to be working normally. The issue may be related to your Discord account or access status.

Please try again with your Discord account. If the problem persists, feel free to contact our technical support team at techsupport@seeed.io and we’ll help check it further.

[gitnub-other]

What the Hell,Seeed Studio, doesn't your conscience hurt? I spent over a hundred CNY on a total piece of junk. You hyped up echo cancellation and noise reduction, but they don't even work. Forget everything else, the background noise alone is enough to blow out the mic. I might as well have bought a 3-CNY microphone from some no-name brand on TaoBao. I was planning to mess around with TTS after my final exams, so you'd better give me a damn good explanation.(ReSpeaker Lite without ESP32S3 From China).By the way ,I am from China and I cannot use the fucking discord.gg.You explain on GitHub

[gitnub-other]

(╯▔皿▔)╯

[nfs0619]

Hi, sorry for the bad experience.

ReSpeaker Lite does have echo cancellation, but we understand the result may not be what you expected.

Since you purchased it from Taobao, please contact our Taobao technical support through your order page. Our support team can help you check and debug the issue.

Discord is not required.

[gitnub-other]

Seeed studio always says that .But they haven't give an useable solution.On WiKi(Giscuss) ,you says so too.

[gitnub-other]

Almost everyone who owns a ReSpeaker Lite has the problem.Now I need a real firmware which has all features or another ReSpeaker models.

[jacobdesforges]

For the 3D CAD files, please consider hosting them on the Wiki itself like other files, or at least GitHub or Printables. The Seeed Studio EE04 3D file only appears to be available on GrabCAD, which is an annoying site requiring email and other personal information to sign up before downloading any models.

[xzsw666]

Thank you for your suggestion! I've already passed it along to the relevant team internally for consideration.😁

[acostach]

Hi, the mfi package archive https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/ for Jetpack 7.2 doesn't contain the super mode for J3010, nor the super dtb. Is this intentional?

The archive name is mfi_recomputer-orin-nano-4g-j401-7.2.0-39.2.0-2026-06-18.tar.gz

[acostach]

@6zsz6 maybe you know the answer here ^ ? Thanks

[zhousizhao]

Thank you for your feedback. Our engineers will investigate this issue shortly and will reply to you as soon as there is any progress.

[jjjadand]

https://seeedstudio88-my.sharepoint.com/:u:/g/personal/youjiang_yu_seeedstudio88_onmicrosoft_com/IQD7ePv8Ukz7S7cD_IQ03sGBAe0TO1NPI1XF_gHs3zVX9GY

hi bro, u can try this one.

[asadm]

Hello. Are there open schematic or pcb design files for reCamera Pro?

[zhousizhao]

What do you need these materials for? Could you please let me know their intended use?

[asadm]

For debugging purpose (how are SYNC pins wired etc on Cam->IMU->board etc?). I want to use reCamera for devkit purpose and then have ability to build my own variant if I ever need it. Just having the schematic would be nice.

[zhousizhao]

Sorry, there are no plans for open-source hardware at the moment.

[rhinostar]

Seriously, though , cmon ... theres nothing secretive about your product. You should be fully transparent about the product so we can get an understanding on how it is constructed, schematics should be the basics. Besides, its not like you guys reinvented anything... and the question on sync asked in genuine. You yourselves probably had a good look at XYlinker RV1126B AI-IPC reference schematic

[atinfinity]

I bought reComputer J4012(Orin NX 16GB). I tried to install JetPack 7.2. So, I read the following page.
https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/

I executed the following command.

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1 --network usb0  --showlogs

As a result, l4t_initrd_flash.sh failed to load the following files.

• usb0.conf
• p3768-0000-p3767-0000-a0.conf

Are your packaging and instructions correct?

---

It appears that this package does not contain iwlwifi-modules.
I think that JP 6.0 contain iwlwifi-modules.

[bleaaach]

Hi, missing these two files will not trigger flashing errors. If you encounter any flashing‑related failures, please refer to this wiki article:https://wiki.seeedstudio.com/usb_timeout_during_flash/#before-you-start
Besides, JetPack 6.0 comes with this driver included.

[atinfinity]

Thanks.

Hi, missing these two files will not trigger flashing errors.

It seems unlikely that there is an issue with Flash. However, the message in question feels misleading to end users.

Besides, JetPack 6.0 comes with this driver included.

I know that point. I was confused because it stopped working again in JetPack 7.2.

[bleaaach]

Yes, JetPack 6.0 comes with this driver pre-installed, but it is not preloaded in JetPack 7.2 for now. You can refer to this Wiki page to install the driver. https://wiki.seeedstudio.com/jetpack72_ax210_ax200_wifi_setup_guide/

[atinfinity]

This page cannot be reached from https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/. So, it is difficult to reach this information. And, I used Intel Dual Band Wireless-AC 8265. Does this page cover this product?

[inoxas78]

Hello,
Is in the future plans to have a native home assistant support (wysiwyg editor etc)

Best regards

[DitingAfel]

Currently, our devices are able to connect to Home Assistant using ESPHome. There are no corresponding native support plans available for now. We will forward your proposal to our team for further assessment.Thank you for your suggestion.