Search found 66 matches
- Fri Mar 06, 2020 3:48 pm
- Forum: Q&A
- Topic: How to use the SNIPS.ai voice service with a XMOS smart microphone?
- Replies: 2
- Views: 20181
Re: How to use the SNIPS.ai voice service with a XMOS smart microphone?
Here are some details for using SNIPS.ai on RPI together with the XK-VF3510-L71 Kit. The Kit doesn't have an audio output . The reason is that it was designed for Smart TV and Set Top Box applications where the audio output is located elsewhere. Therefore the loudspeaker has to be connected to the a...
- Wed Jan 15, 2020 10:33 am
- Forum: Voice & Conferencing
- Topic: Solving snsrNew() Error by renewing keyword license in AVS Client on RPi
- Replies: 0
- Views: 25323
Solving snsrNew() Error by renewing keyword license in AVS Client on RPi
The Alexa Client on RPi uses a keyword model from Sensory which has a limited time license. When that license expires this causes Errors: ERROR: snsrNew(): License expired Here is a solution to fix the error by renewing the license and recompiling: cd /home/pi/sdk-folder/third-party/alexa-rpi git re...
- Wed Nov 13, 2019 10:13 am
- Forum: Q&A
- Topic: Why do I get Cannot load image, XCore 0 is not enabled?
- Replies: 5
- Views: 14541
Re: Why do I get Cannot load image, XCore 0 is not enabled?
Regarding Reason number 3:
Make sure that the Oscillator value in the .xn file matches the frequency of the input CLK
Make sure that the Oscillator value in the .xn file matches the frequency of the input CLK
- Wed Oct 30, 2019 3:49 pm
- Forum: Development Tools and Programming
- Topic: macOS path problem with xTime
- Replies: 8
- Views: 5144
Re: macOS path problem with xTime
Have you tried the commandline? This won't be affected by Java issues.
Please make sure to do a xmake clean first.
Please make sure to do a xmake clean first.
- Wed Oct 30, 2019 12:32 pm
- Forum: Q&A
- Topic: xmosdfu causes error "Could not find/open device" on Linux
- Replies: 0
- Views: 17023
xmosdfu causes error "Could not find/open device" on Linux
When xmosdfu is invoked with a parameter that causes access of the USB device (e.g. --upload) then this causes an error on Linux: Could not find/open device The solution is to invoke xmosdfu as super user with sudo. E.g. sudo ./xmosdfu <device PID> --upload extracted.bin This resolves the issue on U...
- Mon Sep 30, 2019 1:21 pm
- Forum: Other XMOS Development Kits
- Topic: Getting started with the xCORE Microphone Array
- Replies: 6
- Views: 5970
Re: Getting started with the xCORE Microphone Array
There's a known issue with the sw_usb_audio (6.15.2rc1) SW on the xCORE Array Kit.
The solution is provided by this Design Advisory:
https://www.xmos.com/download/Design-ad ... d(1.0).pdf
The solution is provided by this Design Advisory:
https://www.xmos.com/download/Design-ad ... d(1.0).pdf
- Tue Feb 05, 2019 3:35 pm
- Forum: Q&A
- Topic: Debugging XMOS based systems
- Replies: 10
- Views: 23062
Re: Debugging XMOS based systems
The information you're asking about is obtained from the Processor Status Register which is documented on page 9 in
xCORE-200: The XMOS XS2 Architecture (ISA)
Note: The tilestate xgdb script reads system registers over jtag into $resregval with the resreg command.
xCORE-200: The XMOS XS2 Architecture (ISA)
Note: The tilestate xgdb script reads system registers over jtag into $resregval with the resreg command.
- Fri Feb 01, 2019 5:28 pm
- Forum: Q&A
- Topic: Debugging XMOS based systems
- Replies: 10
- Views: 23062
Re: Debugging XMOS based systems
Hi cl-b I'm glad you're asking. https://github.com/xcore/xgdb_scripts provides scripts for xgdb to read and display other System Registers via JTAG. The xlreg script reads and displays information about the XMOS links. The tilestate script reads and displays information about the hardware resources ...
- Fri Jan 25, 2019 2:12 pm
- Forum: Q&A
- Topic: Debugging XMOS based systems
- Replies: 10
- Views: 23062
Re: Debugging XMOS based systems
How to analyse the output of xrun --dump-state ?: When executing this command the internal state of the processor is read via jtag and printed on stdout. For more information about xrun and other debug tools refer to the xTIMEcomposer User Guide The dumpstate output starts with a summary of the curr...
- Fri Jan 25, 2019 2:10 pm
- Forum: Q&A
- Topic: Debugging XMOS based systems
- Replies: 10
- Views: 23062
Re: Debugging XMOS based systems
1. Determine if the XMOS device is in a valid state. Use xrun --dump-state in order to analyse a system that booted from flash. Use xgdb to boot via JTAG and debug using breakpoints, xscope messages, etc a. Check that the device has booted correctly and is executing in application space. Details abo...