Page 1 of 1

macOS path problem with xTime

Posted: Fri Aug 30, 2019 6:50 pm
by Wavelength
All,

XMOS support just doesn't answer any questions!!!

Ok so on July 31 I had this UAC2 on XU208 working fine. I had to switch workplace to look at another product I designed years ago. When I came back I could not get the XU208 to even compile. It appears as though the compiler does not understand the folder structure for the project. I get the following error right away and when I check my code all the directives from customdefines.h are ignored:

/Users/gordonrankin/XMOS3x/X3UAC2/sc_usb_audio/module_usb_audio/endpoint0/endpoint0.c:12:10: fatal error: 'xud.h' file not found

xud.h is where it always has been in the sc_xud folder. I don't even have xud enabled???

[MBAIRJGR:~/XMOS3x/X3UAC2] gordonrankin% ls -l
total 0
drwxr-xr-x 13 gordonrankin staff 416 Sep 19 2018 lib_i2c
drwxr-xr-x 13 gordonrankin staff 416 Oct 1 2018 lib_locks
drwxr-xr-x 13 gordonrankin staff 416 Oct 1 2018 lib_logging
drwxr-xr-x@ 7 gordonrankin staff 224 Sep 18 2018 lib_mic_array
drwxr-xr-x 12 gordonrankin staff 384 Sep 17 2018 lib_xassert
drwxr-xr-x@ 8 gordonrankin staff 256 Sep 18 2018 sc_adat
drwxr-xr-x@ 9 gordonrankin staff 288 Sep 18 2018 sc_i2c
drwxr-xr-x@ 8 gordonrankin staff 256 Sep 18 2018 sc_spdif
drwxr-xr-x@ 7 gordonrankin staff 224 Sep 18 2018 sc_usb
drwxr-xr-x@ 9 gordonrankin staff 288 Sep 9 2018 sc_usb_audio
drwxr-xr-x@ 7 gordonrankin staff 224 Sep 18 2018 sc_usb_device
drwxr-xr-x@ 7 gordonrankin staff 224 Sep 18 2018 sc_util
drwxr-xr-x@ 7 gordonrankin staff 224 Sep 17 2018 sc_xud
drwxr-xr-x@ 17 gordonrankin staff 544 Aug 27 16:42 sw_usb_audio project files are under here.
drwxr-xr-x 3 gordonrankin staff 96 Aug 29 16:41 ws_wave3x this is my workplace folder.

[MBAIRJGR:X3UAC2/sw_usb_audio/XU208WA] gordonrankin% ls -l
total 8
-rw-r--r--@ 1 gordonrankin staff 1543 Jul 30 16:25 Makefile
drwxr-xr-x@ 5 gordonrankin staff 160 Oct 1 2018 src

~~~~

So does anyone know what might be happening here? I am in a real time crunch to get this done. XMOS support said it maybe path length but this worked before.

Is the MakeFile maybe screwed up?

Thanks in advance!
Gordon

Re: macOS path problem with xTime

Posted: Fri Aug 30, 2019 7:59 pm
by Wavelength
First sorry, yes of course I am using XUD???

I found out the access to xmos.com was somehow turned off. Turned that back on and got a little further and the error I had originally struggled with the last 4 weeks.

/Users/gordonrankin/XMOS3x/X3UAC2/sc_usb_audio/module_usb_audio/endpoint0/endpoint0.c:23:10: fatal error: 'dfu_types.h' file not found

DFU, which I don't have enabled. Plus is appears that it's trying to compile DFU stuff as I see it compiling flashlib_user.c

Anyone please this is really wasting a boat load of time.
Thanks,
Gordon

Re: macOS path problem with xTime

Posted: Fri Aug 30, 2019 9:51 pm
by Wavelength
Of course this doesn't help much everytime I do a clean or build all:
Process: xtimecomposer [34206]
Path: /Applications/XMOS_xTIMEcomposer_Community_14.3.3/*/xtimecomposer.app/Contents/MacOS/xtimecomposer
Identifier: org.eclipse.eclipse
Version: 4.3 (4.3)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: xtimecomposer [34206]
User ID: 503

Date/Time: 2019-08-30 16:46:03.260 -0400
OS Version: Mac OS X 10.14.6 (18G87)
Report Version: 12
Bridge OS Version: 3.6 (16P6568)
Anonymous UUID: A2D62759-11F0-E174-478B-E031189EE2F0

Sleep/Wake UUID: 87B4568B-FC82-4E4C-AAC3-C6920B1623BB

Time Awake Since Boot: 400000 seconds
Time Since Wake: 1300 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000001779fd184
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [34206]

VM Regions Near 0x1779fd184:
VM_ALLOCATE 00000001779de000-00000001779fd000 [ 124K] rw-/rw- SM=COW
-->
WebKit Malloc 0000000177a00000-0000000177f00000 [ 5120K] rw-/rwx SM=COW

Application Specific Information:
Java information:
Exception type: Bus Error (0xa) at pc=7fff5fcd7db0

Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-468 mixed mode macosx-amd64)
Only 8 crashes today... maybe part of the problem?
Thanks,
Gordon

Re: macOS path problem with xTime

Posted: Fri Aug 30, 2019 10:52 pm
by mon2
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-468 mixed mode macosx-amd64)
Hi. Would you please test with the 32 bit version of the JRE - recall observing that only the 32 bit version works with their tools. This information may be dated but worth trying. Please post your update.

Re: macOS path problem with xTime

Posted: Mon Sep 02, 2019 8:09 am
by MuellerNick
> recall observing that only the 32 bit version works with their tools

XMOS says that for Windows. With Ubuntu, 64 bit Java does work. Haven't tried on my Mac since a year, as that never worked.
Last time I tried on my Mac, it was unstable beyond usable.

Nick

Re: macOS path problem with xTime

Posted: Mon Sep 02, 2019 5:48 pm
by Wavelength
All,

I went into the Properties->C/C++ General->Path and Symbols and found a bunch of folders with this error: The selected folder does not exist or not accessible.

Thinking it was a path error I actually edited the path with the full path, but still got the same error message after changing it. Tried Refresh and Restart... no luck.

Thinking it maybe a permission thing I changed the rw access to a couple of folders.... but no luck. This looks to be an eclipse problem but I can't find anything about it and why does it happen on Windows 10 as well as macOS?

Image

So that is the Properties->C/C++ General->Paths and Symbols

~~~ interesting note... I backed up the project folder then hit the Restore Defaults and I am down from 104 warnings... like 89 folder errors to 48 warnings with 35 folder errors.

*** Yes still my big problem is my directives in customdefines.h are not working.

Image

Both U208_ONLY and AUDIO_CLASS =2 are set in customdefines.h


/* Audio class version to run in - Default is 2.0 */
#ifndef AUDIO_CLASS
#define AUDIO_CLASS (2)
#endif

#define U208_ONLY 1 // XU208

~~~

Anyone? Help!
Thanks,
Gordon

Re: macOS path problem with xTime

Posted: Mon Sep 02, 2019 9:59 pm
by Wavelength
All,

So this problem happens on my two macOS machines and Windows 10. I was looking around and I found a version of this code from last OCT that I have a sample working. I used TimeMachine to pull that entire working folder back out and do a build (not a clean) and I have the same problems.

Oh well hopefully someone can can figure this out for me.

Thanks,
Gordon

Re: macOS path problem with xTime

Posted: Mon Sep 16, 2019 4:33 pm
by Wavelength
All,
So still having really weird issues with the tools on macOS and Win10. So here is the weirdest problem. As I have been saying since I can compile the project now but for some reason none of the customdefines definitions are working I started working on that a little. I talked to someone who suggested putting customdefine.h at the top of devicedefines.h which was already done. So I looked at something a little more direct. As you may recall AUDIO_CLASS defined in customdefines.h was (2) and U208_ONLY was set to 1. Both of these did nothing in main.xc so I tried this:

#define U208_ONLY
#define AUDIO_CLASS 2

#ifdef U208_ONLY
set_core_high_priority_on();
#endif
/* USB Interface Core */
#if (AUDIO_CLASS==2)
uac_check(2);
XUD_Manager(c_xud_out, ENDPOINT_COUNT_OUT, c_xud_in, ENDPOINT_COUNT_IN,
c_sof, epTypeTableOut, epTypeTableIn, p_usb_rst,
clk, 1, XUD_SPEED_HS, XUD_PWR_CFG);
~~~
Yes that worked... but I got an infos (2 items) following interesting thing after the build all:
Description Resource Path Location Type
previous definition is here customdefines.h /app_usb_aud_xu208_xhra/src/core line 26 C/C++ Problem
previous definition is here customdefines.h /app_usb_aud_xu208_xhra/src/core line 29 C/C++ Problem

/* Audio class version to run in - Default is 2.0 */
#ifndef AUDIO_CLASS
#define AUDIO_CLASS (2)
#endif

#define U208_ONLY 1 // XU208

~~~
What the heck is going on here??? I realize that the slight difference will cause the infos.... but why are the settings in customdefines.h working???

If I remove the two defines in main.xc the damn thing compiles for Full Speed UAC and discregards the U208 ifdef???

These tools really need an update.

Thanks,
Gordon

Re: macOS path problem with xTime

Posted: Wed Oct 30, 2019 3:49 pm
by Thomas
Have you tried the commandline? This won't be affected by Java issues.
Please make sure to do a xmake clean first.