Skip to content

Latest commit

 

History

History
138 lines (92 loc) · 6.85 KB

RASynTroubleshootingGuide.md

File metadata and controls

138 lines (92 loc) · 6.85 KB

RASynBoard Out-of-Box Troubleshooting Guide

This document captures common errors that may be encountered while using/modifying the Avnet RASynBaord Out-of-Box (OOB) application

Table of Contents

NDP Failed to Load Models

ndp_core2_platform_tiny_start failed 9

How to identify this issue

  • The ML model does not load
  • You see debug similar to

How to resolve the issue

This error occurred because the *.synpkg filenames defined in the selected config.ini [Function_x] block are not found in the root directory of the microSD card.

  • Use the debug output to verify that the filenames defined in the selected config.ini [Function_x] block are spelled correctly
  • Verify that the files specified in the selected config.ini [Function_x] block exist on the microSD card in the root directory

Application flooded by inference events even though there should be none

How to identify this issue

  • The RGB LED lights and does not turn off
  • The debug terminal is flooded with "NDP MATCH!!" messages

The following debug was a result of loading V1.4.0 models while running the V1.5.0 Out-of-Box application

Syntiant SDK version mismatch

The OOB application is built using a specific Syntiant SDK version. Any ML models loaded to the NDP120 must have been generated using the same Syntiant SDK version.

SDK Versions by OOB Release

OOB Application Version Syntiant SDK Version
v1.1.0 v100
v1.2.0 v100
v1.3.0 v100
v1.4.0 v103
v1.5.0 v105

History of Edge Impulse Generated Models

Release Date Syntiant SDK Version used to generate ML models Compatible Out-of-Box Release
Oct 2022 v103 V1.4.0
Feb x 2023 v105 V1.5.0

How to resolve the issue

  1. If using the pre-built ML models that come with the OOB application verify that you're using the microSD card files that correspond with the OOB application version. Each release is delivered with compatible ML models and the matching config.ini file.
  2. If you're building the application from source, verify that your microSD card contains the files from the ndp120/synpkg_files/ directory.
  3. If using models generated by Edge Impulse, refer to the table above to identify a compatible Out-of-Box release that supports the models generated by Edge Impulse.

Debug Issues

No debug from PMOD UART even though the application is configured to do so

How to identify this issue

If the application is configured to send debug output to the PMOD UART config.ini:[Debug Print]-->Port=1 but you never see any debug from that UART, or maybe you only see one print statement FreeRTOS ndp_thread running

How to resolve the issue

  • Verify that the config.ini file is correctly configured

  • Verify that the microSD card is inserted into the RASynBoard I/O board
  • Verify that the microSD card contains the config.ini file

When the microSD card is not inserted or if the config.ini file is not found on the microSD card, the application defaults to sending debug out the Virtual COM port associated with the USB-C connector on the core board

When using the Virtual COM port associated with the USB-C connector on the core board I don't see startup debug

This is an implementation artifact. Since this COM port is implemented in software, the application must bring the hardware interface up at boot time. This action takes longer than the initial NDP120 load/boot time.

How to resolve this issue

There is an undocumented feature where the user can enter log in the terminal to dump the early debug after the fact. There's lots of room for improvement on this feature; however it works.

Development Issues

This section captures issues you may encounter when developing custom applications for the RASynBaord. The content here is specific to the Avnet RASynBoard OOB application, but should apply to other projects developed in the Renesas e^2 studio

Debugger fails to load The device R7FA2A1AB set in the launch configuration does not match . . . "

How to identify this issue

When trying to debug the application (clicking on the small green bug icon in e^2 studio) the following dialog is displayed . . .

How to resolve this issue

Debug connection failed

This error will occur if the Renesas e^2 debugger is not found on the development system

How to identify this issue

When trying to debug the application (clicking on the small green bug icon in e^2 studio) the following dialog is displayed . . .

How to resolve this issue

  • Verify that the RASynBoard is correctly configured to enable the debugger
  • Make sure to use the USB-C connector on the I/O board

If you still can't connect to the debugger, verify that the driver is correctly installed on your development PC

  • Verify the hardware configuration as above
  • Open your device manager and look for the Renesas USB Development Tools --> Renesas E2 Lite device
  • If not found . . .
    • Try to reboot your PC
    • Try reinstalling the Renesas e^2 Studio application