Wiki

This version (23 Feb 2024 17:21) was approved by Rebecca Butler.The Previously approved version (23 Feb 2024 17:07) is available.Diff

Appendix B

Below is a list of common problems faced during setup and their solutions or workarounds. Note that some of these may be bugs that are planned (or not) to be fixed and some of them are items commonly missed during setup.

Setup Issues

SC5xx Communications Port Does Not Show Up

Issue Description

When attempting to flash the application(s) on the ADZS-SC589-MINI using the SAM Flasher, or when attempting to connect to the terminal via the shell (TeraTerm), the SC5xx port does not show up in the drop-down list.
Applies to hardware versions

ADZS-SC589-MINI - all versions
Root Cause

The device is not powered on OR the JP1 jumper has not been placed back into the 1-2 position OR the .inf file has not been installed in the device drivers in Windows.
Workaround Steps/Solution

Follow the steps described in environment_setup under CLD CDC USB Driver Setup to install the CLD CDC Driver (Note this is required for the USB/OTG to become operational.
Planned fix status - N/A

SAM Flasher - Invalid serial port!

Issue Description

When attempting to flash the application via the SAM flasher, the SC5xx port shows up, but returns an invalid serial port status when pressing the Update button.
Applies to hardware versions

ADZS-SC589-MINI - all versions
Root Cause

The device is not running in the bootloader and is currently attached to the application.
Workaround Steps/Solution

The device needs to be running in bootloader mode to flash a new application. There will be a separate SC5xx Communications port that appears that is separate from the port that appears in application mode. Follow the steps outlined in program-flash under Application Flash via SAM Flasher to enter the bootloader and proceed to the application flash.
Planned fix status - N/A


Known Issues

SC5xx Communications Port Does Not Show Up/Shows up as A2B Bus Analyzer

Issue Description

When attempting to flash the application(s) on the ADZS-SC589-MINI using the SAM Flasher, or when attempting to connect to the terminal via the shell (TeraTerm), the SC5xx port does not show up in the drop-down list. Instead, I see A2B Bus Analyzer (COM#)
Severity - Minor
Applies to hardware versions

ALL
Root Cause

The USB device VID/PID has been re-used across Audio Starter Framework and the A2B Bus Analyzer products, so this issue can occur if the user has a previous installation of the A2B Bus Analyzer on their PC.
Workaround Steps/Solution

https://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7

In Windows, set the following environment variable to 1: devmgr_show_nonpresent_devices
Launch device manager and go to the View tab and Show hidden devices
Under Ports (COM & LPT), uninstall all of the A2B Bus Analyzer (COM#).
After this, the updated port name should appear after startup of the Audio Starter on the hardware. Note that if this doesn't resolve the naming of the port, this name identifier can still be used for flashing and connection to TeraTerm (your shell) as the only issue with the port is the name.
Planned fix status - No plan

Failed to open 'pushbtn.cmd' when entering bootloader

Issue Description

When entering the bootloader on the ADZS-SC589-MINI hardware by pressing the two push-buttons, the terminal may display Failed to open 'pushbtn1.cmd'
Severity - Minor
Applies to hardware versions

ADZS-SC589-MINI (v2.0.0 and later)
Root Cause

The push-buttons on the ADZS-SC589-MINI are multi-purpose and are used for both entering the bootloader (when reset is also pressed) and executing pushbutton commands. This message can be safely ignored.
Workaround Steps

None - this message can be safely ignored. This issue description is informational only.
Planned fix status - No plan

No sound on USB Audio when changing code versions

Issue Description

When changing code versions (in Github or others), sometimes USB audio has no sound.
NA
Severity - Blocking
Applies to hardware versions

ALL
Root Cause

Whenever any of the basic sound parameters change in source code (IN channels, OUT channels or bit-depth), Windows caches these parameters and becomes confused when they change.
Workaround Steps

https://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7

In Windows, set the following environment variable to 1: devmgr_show_nonpresent_devices
Launch device manager and go to the View tab and Show hidden devices
Under Sound, video and game controllers, uninstall all of the Audio v2.0 Devices.
After this, the updated audio parameters for a new codebase should install in Windows properly.
Planned fix status - NA - It is a Windows issue

High CPU and audio distortion with high channel count on USB/A2B

Issue Description

When attempting to play USB audio or A2B audio, especially with higher channel count, the CPU utilization will be high and sometimes cause audio distortion and shell lock-up due to the high CPU load.
Severity - Major
Applies to hardware versions

ADZS-SC589-MINI v2.1
ADZS-SC584-EZLITE v1.4

Note that this is especially prominent in the Networking branches but the issue applies to all branches supported by the above hardware.
Root Cause

The reduction in the core CPU clock from 500MHz to 450MHz resulted in this side-effect of greater overhead to the system that was unaccounted for.
Workaround Steps/Solution

Enable optimizations for the ARM/SHARC cores in the makefile.
Planned fix status - Fixed for ADZS-SC589-MINI v2.1

All else: In-progress

Error: Failed erasing affected sectors

Issue Description

When attempting to flash the bootloader(s) on the ADZS-SC589-MINI using the CLDP the device returns Error: failed erasing affected sectors.
Severity - Medium
Applies to hardware versions

ADZS-SC589-MINI v1.5
ADZS-SC589-MINI v2.1
Root Cause

There is a mismatch between the external flash byte addressing mode between the application/bootloader and the DXE flasher used to re-flash via CLDP, therefore the CLDP command cannot complete the erasing/flash process.
Workaround Steps/Solution

1. Remove the JP1 jumper header.
2. Reset the board either by the reset button or by a power cycle.
3. Re-flash bootloader0 using the instructions program-flash.
4. Repeat steps for bootloader1, leaving JP1 disconnected.
5. After bootloader flashing is complete, replace JP1 back to positions 1-2 to proceed to application flashing.
Planned fix status - Fixed

Application doesn't boot

Issue Description

After following the steps for the ADZS-SC589-MINI to flash the bootloader and application, the application doesn't appear to boot. LED10 blinks twice and then there are no additional LED blinks.
Severity - Blocking
Applies to hardware versions

ADZS-SC589-MINI - v2.1 - 1.0.0-Github and Networking-1.0.0-Github
Root Cause

The device is running with an incorrect core clock (500MHz) that is out of bounds for the part given the core voltage configured for v2.1. This can cause intermittent failures for the application to run and can apply to certain batches of hardware that are more sensitive to this clock setting.
Workaround Steps/Solution

The device needs to run at a lower core clock of 450MHz Follow the steps below to adjust the application code.

1. Navigate to the directory ALL/include and open up clocks.h.
2. Modify CCLK to 450000000.
3. Navigate to the directory ARM/include and open up FreeRTOSConfig.h
4. Modify configCPU_CLOCK_HZ to 450000000
5. Recompile and reflash the program according to program-flash under Application Flash via SAM Flasher
Planned fix status - Fixed

Application doesn't run in debug session

Issue Description

After following the steps for the ADZS-SC589-MINI to run a debug session, doesn't blink the LEDs. We also cannot connect to the shell termainal. When the debugger is paused, it almost always pauses in the adi_os_vectors_start code.
Severity - Medium
Applies to hardware versions

All hardware/branches that support FreeRTOS
Root Cause

See root cause details here: https://interactive.freertos.org/hc/en-us/community/posts/115002374012-Analog-Devices-ADSP-SC5xx-Cortex-A5-using-CrossCore-Embedded-Studio-GCC-
Workaround Steps/Solution

Ensure that Enable Semihosting is Unchecked as described in debug-session
Planned fix status - No plan

Error: could not write file, load will not complete (When using verify option)

Issue Description

When attempting to use the -cmd prog v option to verify the flash writing was successful, the CLDP tool responds with Error: could not write file, load will not complete.
Severity - Minor
Applies to hardware versions

All - This issue is related to the CLDP tool itself and is not tied to a specific hardware revision
Root Cause

Unknown
Workaround Steps/Solution

Do not use the v option attached to the -cmd prog v or if verification is required, use the -compare option instead: dsp/software-and-development-tools/cces/w/documents/15436/faq-how-to-program-and-verify-using-cldp
Planned fix status - No plan


Don't see your issue or still having issues? Check out EngineerZone and/or shoot us a message!

Navigation - Advanced Audio Projects

resources/tools-software/sharc-audio-module/advanced-audio-projects/appendix-b.txt · Last modified: 23 Feb 2024 17:21 by Rebecca Butler