Getting Started with the DA16200 FreeRTOS SDK

Troubleshooting Tips

We have also included some troubleshooting tips, below, for issues that users may come across.

• One of our employees compiled a great list of troubleshooting tips based on the most common customer issues. This is the perfect place to start.
• Users looking for support on general FreeRTOS questions, can click on this link. There users can get started with posting a topic in FreeRTOS forum.
• Users looking for support with the DA16200 SDK specifically, should post their topic on RenesasRulz forum.

MacOSX

Unfortunately, Renesas does not provide support for their SDK on MacOSX computers. Users will need to use a computer with a Windows or Linux operating system.

Serial Terminal Frozen

We have found that users could accidentally upload code, which may not function properly and potentially bog down the serial terminal; impeding it from taking inputs. If this occurs, users will need to use the J-Link programmer to program the module (with "known good" code) through the JTAG pins.

Reset

The reset button on this board doesn't cause the module to restart the firmware operation; it is used to reset the DA16200 module to the factory setting/configuration (when held down for +5 seconds). In order to reset the firmware, users can use the following commands in the serial debug interface:

• reboot - This command will cause the module to restart the firmware execution.
• reset/boot
  1. reset - This command will take users to the MaskROM mode.
  2. boot - From the MaskROM command mode, this command will cause the module to restart the firmware execution.

Linux Driver

To get started with the DA16200MOD on RZ/G2L Linux systems using the DA16200/600's Linux driver source code, please refer to the Linux Driver Getting Started Guide

Issue with Project Builds

For users who are having issues importing or building a project for one of the application examples, they may need to delete and re-import the DA16200 SDK into the workspace.

In the Project Explorer tab of the Eclipse IDE,

WiFi Examples

To utilize example projects that are dependent on a WiFi connection, users will need to configure the WiFi settings:

• Provision the WiFi through the serial debug interface using the setup command.
• Provide the WiFi credentials in the sample_preconfig.c file of the SDK.

iPerf - Throughput Test

iPerf is an open-source, command-line network diagnostic tool. Users might be interested in this tool to perform a throughput test, which measures packet transfer performance. For more details on operating a throughput test, please refer to Section 6.3 of the Getting Started Guide:

OTA Update Example

With the OTA firmware update example, users may need to erase the firmware or swap which firmware image is currently running.

Erase the Firmware

When utilizing the OTA example, users may need to erase the firmware. This can be performed through the Net command mode.

1. From the [/DA16200] # prompt, enter net to enter the NET command mode.
2. From the [/DA16200/NET] # prompt, enter the ota_update info command to display the firmware information from the SFLASH memory
3. Users can then use the ota_update erase_sflash <start> <size> command to erase a section of the 4MB SFLASH memory.
   • Example: To remove the firmware operating in the RTOS #1 section (0x1e2000) with 117268 bytes of memory, users will use the command ota_update erase_sflash 0x1e2000 117268

Boot Index

There are two slots, in which the main firmware image FRTOS can be stored in the SFLASH memory. These locations are at RTOS #0 (0x23000) and RTOS #1 (0x1e2000). Through the serial debug interface, users can specify which firmware image that the board boots up with.

1. From the command console, the boot index can be changed using the boot_idx command
   • boot_idx 0 - sets RTOS #0 as the firmware to boot
   • boot_idx 1 - sets RTOS #1 as the firmware to boot
2. After running the boot_idx command, run the reboot command to boot the firmware that was selected.

Boot Failures

During the development process, there may be times when there is an error in the code or a problem downloading the firmware which could cause the DA16200/600 to fail to boot properly.

Please refer to Appendix D of the DA16200 FreeRTOS Getting Started Guide.

Prebuilt Images

In case users lock-up or break the firmware on their board, they can upload these prebuilt images for the DA16200 FreeRTOS SDK (version 3.2.4.0). If the board is locked up, the only way to recover the board is flash the firmware with a J-Link debug probe. Click on the buttons below to download the prebuilt images: