What 1722.1 draft is app_1772_1_device compliant with?

Sub forums for various specialist XMOS applications. e.g. USB audio, motor control and robotics.
StephenTurner
Member
Posts: 9
Joined: Fri Dec 09, 2011 11:16 pm

What 1722.1 draft is app_1772_1_device compliant with?

Post by StephenTurner »

Hi

Trying to the UNOS Vision app to "see" an AVB LC board running the 1722.1 device app. Can you tell me what draft the XMOS code is compliant with?

Thanks
Steve


User avatar
Andy
Respected Member
Posts: 279
Joined: Fri Dec 11, 2009 1:34 pm

Post by Andy »

StephenTurner wrote:Hi

Trying to the UNOS Vision app to "see" an AVB LC board running the 1722.1 device app. Can you tell me what draft the XMOS code is compliant with?

Thanks
Steve
Hi Stephen,

See below a beta binary that is compatible with UNOS Vision. It is Draft 18 of 1722.1 with AEM support. We will be releasing a fully tested version of the new 1722.1 code shortly. If you have any queries or want to know more, please contact XMOS support:

http://www.xmos.com/published/avb-refer ... liant-beta
StephenTurner
Member
Posts: 9
Joined: Fri Dec 09, 2011 11:16 pm

Post by StephenTurner »

Hi Andy

Using the code you provided the link to we get the following when trying to download:

C:\asi\sw\xcore\sw_avb\app_1722_1_device\bin>xflash xmos-avb-1722_1-beta.xe
Error: F03108 XE file for factory image (xmos-avb-1722_1-beta.xe) has an SOD lin
k in its XN. Please remove this and recompile the XE before continuing.

thanks
Steve
User avatar
Andy
Respected Member
Posts: 279
Joined: Fri Dec 11, 2009 1:34 pm

Post by Andy »

StephenTurner wrote:Hi Andy

Using the code you provided the link to we get the following when trying to download:

C:\asi\sw\xcore\sw_avb\app_1722_1_device\bin>xflash xmos-avb-1722_1-beta.xe
Error: F03108 XE file for factory image (xmos-avb-1722_1-beta.xe) has an SOD lin
k in its XN. Please remove this and recompile the XE before continuing.

thanks
Steve
Hi Steve,

Please use the 11.11 tools to flash the binary. There's a limitation in 11.2.2 that prevents flashing of binaries that have XScope enabled.
StephenTurner
Member
Posts: 9
Joined: Fri Dec 09, 2011 11:16 pm

Post by StephenTurner »

Hi Andy

OK, thanks, we now have two endpoints streaming 1722 audio between them (through a LabX AVB switch).

We notice (using the LabX switch 802.1AS webpage) that both endpoints claim to be the grandmaster. How can this be?. Is this a bug?

thanks
Steve.
User avatar
Andy
Respected Member
Posts: 279
Joined: Fri Dec 11, 2009 1:34 pm

Post by Andy »

Hi Steve,

Are you sure it isn't indicating that the endpoints are GM capable, rather than actually the GM? You're correct that there should only be one grandmaster on the network. Normally this is a switch.
StephenTurner
Member
Posts: 9
Joined: Fri Dec 09, 2011 11:16 pm

Post by StephenTurner »

Hi Andy

Even when I set the LabX switches gPTP priority to 255, one of my XMOS endpoints remains as master (the other switches to slave).

Is there a setting somewhere that would cause this?.

thanks
steve
User avatar
Andy
Respected Member
Posts: 279
Joined: Fri Dec 11, 2009 1:34 pm

Post by Andy »

This sounds like the correct behaviour. A priority1 of 255 means that the device is not grandmaster capable.

From 8.6.2.1 in the standard:
A ClockMaster A shall be deemed better than a ClockMaster B if the value of priority1 of A is numerically less than that of B
StephenTurner
Member
Posts: 9
Joined: Fri Dec 09, 2011 11:16 pm

Post by StephenTurner »

changing the switches priority back to 248, makes both XMOS endpoints be a master.

setting the switch to anything above 249 makes one of the endpoints switch to slave, but the other always stays at master.

-steve
User avatar
Andy
Respected Member
Posts: 279
Joined: Fri Dec 11, 2009 1:34 pm

Post by Andy »

Hi Steve,

What is the serial number on both your boards?

Can you post the debug print output from both boards?
Post Reply