{"id":133636,"date":"2026-10-08T09:12:55","date_gmt":"2026-10-08T09:12:55","guid":{"rendered":"https:\/\/www.seeedstudio.com\/blog\/?p=133636"},"modified":"2026-10-08T09:12:58","modified_gmt":"2026-10-08T09:12:58","slug":"seeed-fusion-open-source-modular-pcba-testing-a-complete-guide-from-hardware-to-test-workflow","status":"publish","type":"post","link":"https:\/\/www.seeedstudio.com\/blog\/2026\/10\/08\/seeed-fusion-open-source-modular-pcba-testing-a-complete-guide-from-hardware-to-test-workflow\/","title":{"rendered":"Open-Source Modular PCBA Testing: A Complete Guide from Hardware to Test Workflow"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Building a functional test setup for one PCBA is relatively straightforward. The challenge is making it reusable across different products.<\/p>\n\n\n\n

To reduce repeated hardware and software development, we built a modular testing architecture based on three parts:<\/p>\n\n\n\n

Universal Test Box \u2192 Product-Specific<\/strong> Adapter<\/strong> Board \u2192 Configurable Test Software<\/strong><\/p>\n\n\n\n

Common test resources are integrated into the reusable Test Box, while each new product mainly requires an adapter board and its own test workflow.<\/p>\n\n\n\n

This guide explains the complete architecture and walks through a real reference project using the reSpeaker Flex XVF3800 Core Board with XIAO<\/strong>.<\/p>\n\n\n\n

Table of Contents<\/h3>\n\n\n\n
    \n
  1. How the Modular Test System Works<\/strong><\/li>\n\n\n\n
  2. Why Use a Modular Test Architecture?<\/strong><\/li>\n\n\n\n
  3. Universal Test Box Capabilities<\/strong><\/li>\n\n\n\n
  4. Software Test Framework<\/strong><\/li>\n\n\n\n
  5. How to Adapt the System to Your Own PCBA<\/strong><\/li>\n<\/ol>\n\n\n\n

    Reference Project: reSpeaker Flex XVF3800 Core Board with XIAO<\/strong><\/p>\n\n\n\n

      \n
    • Test Plan<\/li>\n\n\n\n
    • Adapter Board Design<\/li>\n\n\n\n
    • Test Software Configuration<\/li>\n\n\n\n
    • Test Fixture & Software Reference<\/li>\n<\/ul>\n\n\n\n
        \n
      1. Open-Source Resources<\/strong><\/li>\n<\/ol>\n\n\n\n
        \n
        \n

        <\/h1>\n<\/div>\n<\/div>\n\n\n\n

        1. How the Modular Test System Works<\/h2>\n\n\n\n

        The system separates reusable test resources<\/strong> from product-specific adaptation<\/strong>:<\/p>\n\n\n\n

        Your PCBA \u2192<\/strong> Adapter<\/strong> Board \u2192 Universal Test Box \u2192 Test Software \u2192 PASS \/ FAIL<\/strong><\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        Adapter Board<\/h3>\n\n\n\n

        The Adapter Board provides the product-specific connection between the PCBA and the standardized interfaces of the Test Box.<\/p>\n\n\n\n

        For a new product, you mainly need to map the required signals to the appropriate Test Box resources.<\/p>\n\n\n\n

        Universal Test Box<\/h3>\n\n\n\n

        The Universal Test Box integrates common test resources \u2014 including UART, RS485,<\/strong> USB<\/strong>,<\/strong> ADC<\/strong>,<\/strong> GPIO<\/strong>, I\u00b2C, power control, and programming interfaces<\/strong> \u2014 into one reusable platform.<\/p>\n\n\n\n

        These functions can be reused across different products instead of being redesigned for every new PCBA.<\/p>\n\n\n\n

        Test Software<\/h3>\n\n\n\n

        The software controls the test sequence and calls reusable functions for communication, programming, measurement, and result validation<\/strong>.<\/p>\n\n\n\n

        Each product can use its own test configuration, while the underlying software framework remains reusable.<\/p>\n\n\n\n

        \n
        \n

        <\/h1>\n<\/div>\n<\/div>\n\n\n\n

        2. Why Use a Modular Test Architecture?<\/h2>\n\n\n\n

        In a traditional product-specific approach, each new product often requires a dedicated companion test board designed around its specific test requirements.<\/p>\n\n\n\n

        A modular architecture separates reusable testing resources<\/strong> from the product-specific interface<\/strong>, reducing repeated hardware development and making the test system easier to reuse across different products.<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        <\/td>Traditional Product-Specific Test Board<\/td>Universal Test Box + Adapter Board<\/td><\/tr>
        Development<\/td>A complete test board must be designed, manufactured, and debugged for each product<\/td>Only a relatively simple adapter board needs to be designed<\/td><\/tr>
        Reusability<\/td>Test circuits are difficult to reuse across products<\/td>The same Test Box can support multiple products<\/td><\/tr>
        Maintenance<\/td>Multiple boards and versions need to be maintained<\/td>Core test hardware is centralized and standardized<\/td><\/tr>
        Consistency<\/td>Different products may use different circuits and layouts<\/td>Core test hardware remains consistent<\/td><\/tr>
        Scalability<\/td>New test hardware must be developed for each product<\/td>The same platform can be reused as more products are added<\/td><\/tr>
        Engineering Effort<\/td>Greater dependence on dedicated hardware development<\/td>Product adaptation focuses mainly on interface mapping<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        The result is more than a different fixture design \u2014 it is a reusable platform for functional testing<\/strong>.<\/p>\n\n\n\n

        \n
        \n

        <\/h2>\n<\/div>\n<\/div>\n\n\n\n

        3. Universal Test Box Capabilities<\/h2>\n\n\n\n

        The Universal Test Box brings commonly used hardware resources into one reusable platform, allowing different PCBAs to share the same core test hardware.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        The Test Box exposes standardized Power &<\/strong> ADC<\/strong>, Signal, and Expansion interfaces<\/strong>, allowing product-specific adapter boards to connect only the resources required for each test.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n
        \"\"<\/figure>\n\n\n\n

        Available Hardware Resources<\/h3>\n\n\n\n
        Category<\/td>Test Resource<\/td>Quantity<\/td>Notes<\/td><\/tr>
        Measurement<\/td>ADC measurement channels<\/td>18<\/td>2 channels without voltage division; external voltage division is required when the target voltage exceeds 3.3 V<\/td><\/tr>
        Power Control<\/td>Controllable power output<\/td>1<\/td>Output voltage equals the Test Box input voltage<\/td><\/tr>
        Controllable DC 5 V output<\/td>1<\/td>\u2014<\/td><\/tr>
        Controllable DC 3.3 V output<\/td>2<\/td>\u2014<\/td><\/tr>
        Controllable DC 1.8 V output<\/td>1<\/td>\u2014<\/td><\/tr>
        PMOS switches<\/td>4<\/td>\u2014<\/td><\/tr>
        Adjustable simulated battery<\/td>1<\/td>\u2014<\/td><\/tr>
        Communication<\/td>USB-to-UART<\/td>3<\/td>\u2014<\/td><\/tr>
        RS232<\/td>1<\/td>\u2014<\/td><\/tr>
        RS485<\/td>1<\/td>\u2014<\/td><\/tr>
        RS422<\/td>1<\/td>\u2014<\/td><\/tr>
        CAN<\/td>1<\/td>\u2014<\/td><\/tr>
        USB interfaces<\/td>3<\/td>One USB port supports controllable power output<\/td><\/tr>
        Programming<\/td>J-Link<\/td>4<\/td>\u2014<\/td><\/tr>
        Digital I\/O<\/td>GPIO<\/td>12<\/td>\u2014<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        These resources can be combined according to the test requirements of each product \u2014 for example, measuring power rails, verifying communication interfaces, programming firmware, checking GPIO, or testing USB functions.<\/p>\n\n\n\n

        \n
        \n

        <\/h2>\n<\/div>\n<\/div>\n\n\n\n

        4. Software Test Framework<\/h2>\n\n\n\n

        The Universal Test Box is paired with a reusable software framework, so each new product does not require a completely new test application.<\/p>\n\n\n\n

        The framework provides common functions for workflow<\/strong> control, communication, firmware programming, result validation, and test logging<\/strong>. For each product, developers can define the required test sequence through configuration and reuse the existing functions.<\/p>\n\n\n\n

        Key Software Capabilities<\/h3>\n\n\n\n
        Category<\/td>Capabilities<\/td><\/tr>
        Workflow<\/td>Test sequence execution, step control, and PASS \/ FAIL validation<\/td><\/tr>
        Communication<\/td>Serial, SSH, BLE, and other communication functions<\/td><\/tr>
        Programming<\/td>J-Link, ESP, XMODEM \/ YMODEM, and other firmware flashing tools<\/td><\/tr>
        Test Functions<\/td>GPIO, RF, audio, and product-specific functional tests<\/td><\/tr>
        Production Support<\/td>Barcode handling, product configuration, test logs, and workstation information<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Software Architecture<\/h3>\n\n\n\n

        The framework separates the user interface<\/strong>,<\/strong> workflow<\/strong> engine, reusable test modules, product configurations, firmware, and logs<\/strong>, allowing the same software foundation to be reused across different products.<\/p>\n\n\n\n

        View Full Software Architecture<\/strong><\/p>\n\n\n\n

        Seeed_Factory_Auto_Test_Tool\/\n\u251c\u2500\u2500 main.py\n\u251c\u2500\u2500 config.ini\n\u251c\u2500\u2500 function.json\n\u251c\u2500\u2500 product_list.txt\n\u251c\u2500\u2500 environment.yml\n\u251c\u2500\u2500 build.bat\n\u251c\u2500\u2500 scan_hidden_imports.py\n\u251c\u2500\u2500 zip_utf8.py\n\u251c\u2500\u2500 generate_manifest.py\n\u251c\u2500\u2500 app_icon.ico\n\u2502\n\u251c\u2500\u2500 window\/\n\u2502   \u251c\u2500\u2500 flash_window.py\n\u2502   \u251c\u2500\u2500 index_window.py\n\u2502   \u251c\u2500\u2500 operation_window.py\n\u2502   \u2514\u2500\u2500 view_interface\/\n\u2502       \u251c\u2500\u2500 home_interface.py\n\u2502       \u251c\u2500\u2500 tool_interface.py\n\u2502       \u251c\u2500\u2500 config_interface.py\n\u2502       \u251c\u2500\u2500 add_ini_interface.py\n\u2502       \u251c\u2500\u2500 add_product_interface.py\n\u2502       \u2514\u2500\u2500 edit_ini_interface.py\n\u2502\n\u251c\u2500\u2500 main_function_deal\/\n\u2502   \u2514\u2500\u2500 function_thread.py\n\u2502\n\u251c\u2500\u2500 custom_component\/\n\u2502   \u251c\u2500\u2500 sys_control\/\n\u2502   \u251c\u2500\u2500 serial_tool\/\n\u2502   \u251c\u2500\u2500 ssh_tool\/\n\u2502   \u251c\u2500\u2500 flash_firmware\/\n\u2502   \u251c\u2500\u2500 esp_tool\/\n\u2502   \u251c\u2500\u2500 other_tool\/\n\u2502   \u251c\u2500\u2500 product_special_func\/\n\u2502   \u2514\u2500\u2500 window_component\/\n\u2502\n\u251c\u2500\u2500 qfluentwidgets\/\n\u251c\u2500\u2500 product_function_ini\/\n\u251c\u2500\u2500 product_firmware\/\n\u251c\u2500\u2500 product_images\/\n\u251c\u2500\u2500 product_test_scripts\/\n\u251c\u2500\u2500 product_log\/\n\u251c\u2500\u2500 temp_log\/\n\u251c\u2500\u2500 jlink_tool\/\n\u251c\u2500\u2500 esp_tools\/\n\u251c\u2500\u2500 adafruit_tools\/\n\u251c\u2500\u2500 meshtastic_tools\/\n\u2514\u2500\u2500 wt328_wavefile\/<\/code><\/pre>\n\n\n\n
        5. How to Adapt the System to Your Own PCBA<\/h2>\n\n\n\n
        To adapt the platform to a new PCBA, the process can be divided into four steps:<\/p>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        Step 1 \u2014 Define Your Test Requirements<\/h3>\n\n\n\n
        Start by identifying what needs to be tested, how it will be tested, and what counts as PASS<\/strong>.<\/p>\n\n\n\n
        Typical functional tests may cover power rails, voltage levels, GPIO, UART, I\u00b2C, USB, buttons, LEDs, sensors, firmware programming, audio, and other product-specific functions.<\/p>\n\n\n\n
        Test Item<\/td>Method<\/td>PASS Criteria<\/td><\/tr>
        3.3 V rail<\/td>ADC measurement<\/td>3.3 V \u00b15%<\/td><\/tr>
        GPIO<\/td>Output toggle \/ input detection<\/td>Expected HIGH \/ LOW detected<\/td><\/tr>
        I\u00b2C<\/td>Scan bus<\/td>Expected device address detected<\/td><\/tr>
        Firmware<\/td>Program device<\/td>Programming completes successfully<\/td><\/tr>
        USB<\/td>Enumerate device<\/td>Device detected by PC<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        The test plan becomes the basis for both the hardware connection and the software workflow.<\/p>\n\n\n\n
        Step 2 \u2014 Map Test Requirements to Test Box Resources<\/h3>\n\n\n\n
        Next, match each test item to an available resource in the Universal Test Box.<\/p>\n\n\n\n
        Test Requirement<\/td>Test Box Resource<\/td><\/tr>
        Voltage measurement<\/td>ADC channel<\/td><\/tr>
        GPIO verification<\/td>GPIO<\/td><\/tr>
        Serial communication<\/td>USB-to-UART<\/td><\/tr>
        Firmware programming<\/td>J-Link \/ supported programming tool<\/td><\/tr>
        USB function<\/td>USB interface<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        This mapping determines which signals need to be routed through the product-specific Adapter Board.<\/p>\n\n\n\n
        Step 3 \u2014 Design the Adapter Board<\/h3>\n\n\n\n
        The Adapter Board connects the PCBA under test to the standardized interfaces of the Universal Test Box.<\/p>\n\n\n\n
        Because the common test resources are already integrated into the Test Box, the Adapter Board mainly needs to route the required product signals to the corresponding Test Box resources<\/strong>, rather than rebuilding the complete test circuitry.<\/p>\n\n\n\n
        We\u2019ll show a complete Adapter Board example in the reference project below.<\/p>\n\n\n\n
        Step 4 \u2014 Configure the Test Workflow<\/h3>\n\n\n\n
        Once the hardware connection is ready, define the test sequence in the software framework.<\/p>\n\n\n\n
        The workflow can be configured through an INI<\/strong> file<\/strong>, using predefined functions and parameters for each test step. The newer software also supports graphical drag-and-drop configuration<\/strong> to simplify workflow setup.<\/p>\n\n\n\n
        At its simplest, each step follows the same logic: Action \u2192 Expected Result \u2192 PASS \/ FAIL<\/strong><\/p>\n\n\n\n
        For example: Enable 3.3 V power \u2192 Measure TP7 \u2192 3.3 V \u00b15% \u2192 PASS<\/strong><\/p>\n\n\n\n
        The framework remains the same across products; only the test sequence and product-specific configuration need to be adapted.<\/p>\n\n\n\n
        \n
        \n
        <\/h2>\n<\/div>\n<\/div>\n\n\n\n
        Reference Project: reSpeaker Flex XVF3800 Core Board with XIAO<\/mark><\/strong><\/h2>\n\n\n\n
        To show how the platform works in a real project, we are sharing an open-source test reference based on a Seeed product \u2014 the reSpeaker Flex XVF3800 Core Board with XIAO<\/strong>.<\/p>\n\n\n\n
        The reference covers the complete workflow from test planning and resource mapping to Adapter Board design and software configuration. With multiple power paths, USB, audio, GPIO, I\u00b2C, I\u00b2S, XIAO, and XMOS firmware, it provides a practical example for adapting the platform to a complex PCBA.<\/p>\n\n\n\n
        1. Define the Test Items<\/h3>\n\n\n\n
        The original project test plan covers the following areas.<\/p>\n\n\n\n
        Test Area<\/td>Test Method<\/td>PASS Criteria<\/td><\/tr>
        LED<\/td>Visual inspection + software confirmation<\/td>Green LED turns on at power-up<\/td><\/tr>
        Power inputs<\/td>Individually power through USB 5 V, Type-C 5 V, Pad 5 V, XIAO 5 V, and 12 V; ADC measurement at TP3<\/td>TP3: 5 V \u00b15%; PVCC1: 12 V \u00b15%<\/td><\/tr>
        VDDIO<\/td>ADC at TP7<\/td>3.3 V \u00b15%<\/td><\/tr>
        AUDIO_1V8<\/td>ADC at TP6<\/td>1.8 V \u00b15%<\/td><\/tr>
        0V9<\/td>ADC at TP8<\/td>0.9 V \u00b15%<\/td><\/tr>
        XMOS firmware & SN<\/td>Flash USB test firmware through debug interface and write SN<\/td>Firmware flashing and SN writing succeed<\/td><\/tr>
        USB Type-C<\/td>Test both connector orientations<\/td>XMOS is recognized in both orientations<\/td><\/tr>
        PH connector USB<\/td>USB signal verification<\/td>PC recognizes XMOS in safe mode<\/td><\/tr>
        XMOS + FPC<\/td>Recording with microphone array<\/td>Four-channel recording data is normal<\/td><\/tr>
        Codec \/ Speaker<\/td>Audio playback<\/td>10 W \/ 4 \u03a9 speaker output is normal<\/td><\/tr>
        Mute<\/td>Insert\/remove headphone during playback and test software mute<\/td>Playback switches correctly and software mute works<\/td><\/tr>
        Pin Header GPIO<\/td>X0D00 \/ X0D11 \/ X0D39 GPIO toggle and input detection<\/td>GPIO operates normally<\/td><\/tr>
        I\u00b2C<\/td>PC controls volume<\/td>Volume can be controlled normally<\/td><\/tr>
        I\u00b2S<\/td>PC recording \/ playback<\/td>Audio data is normal<\/td><\/tr>
        RST<\/td>Button test<\/td>Pressing Reset resets XMOS<\/td><\/tr>
        Boot<\/td>Button + power-on<\/td>XMOS enters safe mode<\/td><\/tr>
        XIAO firmware<\/td>Program XIAO test firmware \/ relevant product firmware<\/td>Programming completes<\/td><\/tr>
        XIAO D0\u2013D3<\/td>GPIO verification<\/td>D1 can reset XMOS; D0\/D2\/D3 toggle normally<\/td><\/tr>
        XIAO LED<\/td>Visual + software confirmation<\/td>Red and yellow LEDs turn on as expected<\/td><\/tr>
        XIAO I\u00b2C<\/td>Scan I\u00b2C bus<\/td>Codec detected at address 0x18<\/td><\/tr>
        XIAO I\u00b2S<\/td>Record through XIAO<\/td>Recording data is normal<\/td><\/tr>
        Shipping firmware<\/td>Program XIAO shipping firmware<\/td>Programming completes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        This test plan becomes the foundation for both the adapter-board design and the software workflow.<\/p>\n\n\n\n
        2. Adapter Board Design<\/h3>\n\n\n\n
        After the test items and required signals are identified, the next step is to design the product-specific adapter board.<\/p>\n\n\n\n
        For this reference project, the adapter board only needs to route the required product signals to the standardized Test Box interface rather than recreating all of the test hardware.<\/p>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        The same principle can be applied to another PCBA:<\/p>\n\n\n\n
          \n
        1. Identify required test signals.<\/li>\n\n\n\n
        2. Select the corresponding Test Box resources.<\/li>\n\n\n\n
        3. Map those signals to the standard connector.<\/li>\n\n\n\n
        4. Build the product-specific adapter.<\/li>\n<\/ol>\n\n\n\n
          3. Test Software Configuration<\/h3>\n\n\n\n
          After the hardware is connected, the same test framework can be reused for the new product.<\/p>\n\n\n\n
          For this reference project, the test sequence is defined through an INI configuration. The workflow includes Test Box initialization, board identification, power control, XIAO firmware flashing, device verification, SN checking, and power-off handling.<\/p>\n\n\n\n
          \ud83d\udc47Below is the full configuration example provided for the reference project.<\/p>\n\n\n\n
          Full Configuration Example<\/h3>\n\n\n\n
          [configure]\nbarcoder_status=True\nupload_file_status=False\n\n[steps]\n#begin\nstart_time=custom_component.product_special_func.operation_prompt_func.time_start\n\n#test box init\ntest_init_remind=custom_component.other_tool.print_tool.print_message@Step Remind:\u6d4b\u8bd5\u76d2\u521d\u59cb\u5316....\ntest_fixture_response=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@2E8A@000A@9600@AT\ncheck_test_fixture_recall=custom_component.other_tool.temp_return_deal.check_string_in_step@test_fixture_response@OK\n\ntest_init=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@2E8A@000A@9600@AT+PINOUT=15,17,18,11,12,13|0,0,1,0,0,0\ncheck_test_init=custom_component.other_tool.temp_return_deal.check_string_in_step@test_init@OK\n\ntest_gpio_init=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@2E8A@000A@9600@AT+TCA6424AIN=5,6,7,17,18,19,20\ncheck_test_gpio_init=custom_component.other_tool.temp_return_deal.check_string_in_step@test_gpio_init@OK\n\n#scan board qrcode\nscan_board_qrcode_remind=custom_component.other_tool.print_tool.print_message@Step Remind:Scan Board SN....\nscan_board_qrcode=self.get_barcoder_input\nget_product_sn=custom_component.other_tool.temp_return_deal.deal_return_by_length@scan_board_qrcode@18\nget_product_sku=custom_component.other_tool.temp_return_deal.deal_return_by_length@get_product_sn@9\ncheck_board_sku=custom_component.other_tool.temp_return_deal.check_string_in_step_multi@get_product_sku@100070894,100026178\n\n#power on product\npower_on_product=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@2E8A@000A@9600@AT+PINOUT=15,17,18,11,12,13|0,1,1,0,1,0\ncheck_power_on_product=custom_component.other_tool.temp_return_deal.check_string_in_step@power_on_product@OK\n\n#xiao firm flash and xvf3800 firm version check, then falsh xiao blank\nput_on_remind_confirm=custom_component.product_special_func.operation_prompt_func.show_image_selector@\u4ea7\u54c1\u653e\u4e0a\u6cbb\u5177\u538b\u5408\u540e, \u5c06\u6cbb\u5177\u76d2\u5b50\u7684\u4ea7\u54c1USB\u7ebf\u8fde\u63a5\u5230XIAO\u7684typeC\u53e3, \u786e\u8ba4\u4ea7\u54c1\u7eff\u706f\u4eae,XIAO\u53ea\u4eae\u7ea2\u706f\uff0c\u70b9\u51fbOK@product_images\/product_special_images\/202004622_respeaker_flex_core\/xiao_check.jpg\n\nflash_xiao_test_firm=custom_component.esp_tool.esptool_programer.program_esp_firmware_v49@303A@1001@--chip esp32s3 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size detect 0x0 product_firmware\/respeaker_flex_xvf3800\/xiao\/respeaker_xiao.ino.bootloader.bin 0x8000 product_firmware\/respeaker_flex_xvf3800\/xiao\/respeaker_xiao.ino.partitions.bin 0xe000 product_firmware\/respeaker_flex_xvf3800\/xiao\/boot_app0.bin 0x10000 product_firmware\/respeaker_flex_xvf3800\/xiao\/respeaker_xiao.ino.bin\n\ncheck_flash_xiao_test_firm=custom_component.other_tool.temp_return_deal.check_string_in_step@flash_xiao_test_firm@True\n\nled_xiao_confirm=custom_component.product_special_func.operation_prompt_func.show_image_selector@\u786e\u8ba4XIAO\u7684\u9ec4\u706f\u4eae, \u70b9\u51fbOK@product_images\/product_special_images\/202004622_respeaker_flex_core\/xiao_led.jpg\n\nxiao=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@303A@1001@115200@XIAO\\r\\n\ncheck_xiao=custom_component.other_tool.temp_return_deal.check_string_in_step@xiao@OK\n\nxiao_info=custom_component.product_special_func.respeaker_flex_special_func.check_xiao_info@product_function_ini\\202004622_xiao_test.ini@get_product_sku\ncheck_xiao_info=custom_component.other_tool.temp_return_deal.check_string_in_step@xiao_info@True\n\nxiao_uart_close_1=custom_component.product_special_func.respeaker_flex_special_func.xiao_serial_close\n\nflash_xiao_blank_remind=custom_component.other_tool.print_tool.print_message@Step Remind: \u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014  XIAO \u51fa\u8d27\u7a7a\u767d\u56fa\u4ef6\u70e7\u5f55 \u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\n\nflash_xiao_blank=custom_component.esp_tool.esptool_programer.program_esp_firmware_v49@303A@1001@--chip esp32s3 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size detect 0x0 product_firmware\/respeaker_flex_xvf3800\/xiao\/blank.ino.bootloader.bin 0x8000 product_firmware\/respeaker_flex_xvf3800\/xiao\/blank.ino.partitions.bin 0xe000 product_firmware\/respeaker_flex_xvf3800\/xiao\/boot_app0.bin 0x10000 product_firmware\/respeaker_flex_xvf3800\/xiao\/blank.ino.bin\n\ncheck_flash_xiao_blank=custom_component.other_tool.temp_return_deal.check_string_in_step@flash_xiao_blank@True\n\n#check product sn\nread_sn_remind=custom_component.other_tool.print_tool.print_message@Step Remind: \u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014 SN\u68c0\u67e5 \u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\nread_sn=custom_component.product_special_func.respeaker_flex_special_func.read_xmos@0x000003f8@--id 0\ntest_read_sn=custom_component.other_tool.temp_return_deal.step_two_return_equal@read_sn@get_product_sn\ncheck_test_read_sn=custom_component.other_tool.temp_return_deal.check_string_in_step@test_read_sn@True\n\n#power off\npower_off_sn=custom_component.serial_tool.serial_funcbox.serial_send_and_receive@2E8A@000A@9600@AT+PINOUT=15,17,18,11,12,13|0,0,1,0,0,0\ncheck_power_off_sn=custom_component.other_tool.temp_return_deal.check_string_in_step@power_off_sn@OK\npower_off_sn_delay=time.sleep@1\n\n#end step\nend_steps=custom_component.other_tool.print_tool.print_message@writeSN END!\nend_time=custom_component.product_special_func.operation_prompt_func.time_end<\/code><\/pre>\n\n\n\n
          The important point here is not that every project uses the same configuration.<\/p>\n\n\n\n
          Instead, the framework remains reusable while the configuration changes according to the product<\/strong>.<\/p>\n\n\n\n
          4. Test Fixture and Software Reference<\/h2>\n\n\n\n
          Test Fixture<\/h3>\n\n\n\n
          The reference project uses a physical fixture to position the PCBA and make repeatable connections to the required test points and interfaces.<\/p>\n\n\n\n
          \n
          \n
          \"\"<\/figure>\n<\/div>\n\n\n\n
          \n
          \"\"\/<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n
          The mechanical fixture, product adapter, and Universal Test Box work together to turn the test plan into a repeatable manufacturing process.<\/p>\n\n\n\n
          <\/p>\n\n\n\n
          Reference Test Software<\/h3>\n\n\n\n
          In our production environment, Seeed uses an internal test application to execute configured test sequences, display test progress, and determine PASS \/ FAIL results<\/strong>.<\/p>\n\n\n\n
          Together with the Test Box hardware, it demonstrates how a complete functional test system can be built around a reusable hardware and software architecture.<\/p>\n\n\n\n
          \"\"<\/figure>\n\n\n\n
          Developers can use the same architecture and interface concepts to build their own test system. If you are interested in building a similar test setup for your own product, contact Seeed Fusion<\/strong> to discuss a customized solution.<\/p>\n\n\n\n
          A typical test application may include:<\/p>\n\n\n\n
            \n
          • hardware resource control;<\/li>\n\n\n\n
          • test-sequence execution;<\/li>\n\n\n\n
          • data collection and validation;<\/li>\n\n\n\n
          • product-specific PASS \/ FAIL criteria;<\/li>\n\n\n\n
          • test-result display and logging.<\/li>\n<\/ul>\n\n\n\n
            <\/p>\n\n\n\n
            Ready to Build Your Own Test Workflow?<\/h2>\n\n\n\n
            Use the open-source reference to adapt the architecture to your own XIAO-based expansion board or custom PCBA.<\/p>\n\n\n\n