[XK-AVB-LC-SYS] Which IP Address? How to connect with switch Topic is solved

[crappidy]

Hello,

I want to build a network with two AVB Endpoints (XK-AVB-LC-SYS), a Laptop and an AVB Switch.
An avdecc library/controller (https://github.com/audioscience/avdecc-lib) is installed on my linux system.
The avdecc controller can be used over command line. For test purposes I have connected the endpoint with my laptop over Ethernet. But the endpoint doesn't show up in the list of the connected endpoints in the controller program.
Why not?
Can I ping the endpoint?
Do I have to config the Ethernet ports of the endpoint so that they work?

Don't know what is wrong...
Pls help.

Greetz
Chris

[peter]

Hi crappidy,

The endpoint should be getting an IP address using DHCP. If you run the firmware with:

Code: Select all

xrun --xscope AVB_FIRMWARE.xe

then it should print the IP address on the console and you can try to ping it.

Regards,

Peter

[crappidy]

And where can I get the file "AVB_FIRMWARE.xe"?

[peter]

That is meant to mean the AVB firmware that you build yourself.

Regards,

Peter

[crappidy]

Okay, with your command I get this output:

WARNING: tile[0] - xSCOPE not supported by application, I/O will be via JTAG
WARNING: tile[1] - xSCOPE not supported by application, I/O will be via JTAG

The program works, but over USB.
But I want to get information about the ethernet connection..

[peter]

Hi Chris,

Sounds like your program is set up to use JTAG (slow) IO instead of xscope IO. You can change that by adding a config.xscope file to your src folder with the following contents and re-compiling:

Code: Select all

<xSCOPEconfig enabled="true" ioMode="basic">
</xSCOPEconfig>

The USB connection is for the debug information, which should hopefully be printing information about what the ethernet library is doing when negotiating its IP address.

Do you get any useful information on the console when running this program.

Regards,

Peter

[crappidy]

XScope works now.
Debug output in command prompt/debug mode:

0x00010000 in _start ()
Loading setup image to XCore 0
Loading section .text, size 0x314 lma 0x10000
Loading section .cp.rodata, size 0x18 lma 0x10314
Loading section .dp.data, size 0x24 lma 0x1032c
Start address 0x10000, load size 848
Transfer rate: 103 KB/sec, 282 bytes/write.
xSCOPE enabled on tile 0 at address 0x10348
Loading setup image to XCore 1
Loading section .text, size 0x2d8 lma 0x10000
Loading section .cp.rodata, size 0x18 lma 0x102d8
Loading section .dp.data, size 0x20 lma 0x102f0
Start address 0x10000, load size 784
Transfer rate: 95 KB/sec, 261 bytes/write.
xSCOPE enabled on tile 1 at address 0x10308
First stage multi-node boot started
First stage multi-node boot completed
Loading application image to XCore 0
Loading section .text, size 0x532 lma 0x10000
Loading section .init, size 0x1a lma 0x10532
Loading section .fini, size 0x2e lma 0x1054c
Loading section .eh_frame, size 0x24 lma 0x1057c
Loading section .cp.const4, size 0x24 lma 0x105a0
Loading section .cp.rodata.cst4, size 0x24 lma 0x105c4
Loading section .ctors, size 0x8 lma 0x105e8
Loading section .dtors, size 0x8 lma 0x105f0
Loading section .dp.data, size 0x38 lma 0x105f8
Start address 0x10000, load size 1582
Transfer rate: 73 KB/sec, 175 bytes/write.
xSCOPE enabled on tile 0 at address 0x10628
Loading application image to XCore 1
Loading section .text, size 0xc lma 0x10000
Loading section .dp.data, size 0x8 lma 0x1000c
Start address 0x10000, load size 20
Transfer rate: 6 KB/sec, 10 bytes/write.
xSCOPE enabled on tile 1 at address 0x1000c

But no information about Ethernet?

[peter]

Hi Chris,

Looking into this it looks like the AVB_LC_SYS firmware (app_avb_lc_demo) doesn't use xTCP and therefore isn't assigned an IP address. I think the only way to debug what is going on is to look at the packets on the interface using wireshark. Do you see any packets coming out of the device? What do you see?

What version of the AVB_LC_SYS are you using, and what version of the controller? Do you have access to a Mac? They have AVB support built-in and should therefore find the device in the Network Device Browser of Audio Midi Setup. I downloaded the 6.1.1 firmware, used tools 13.2.3 compiled and ran it and got the device showing up.

Regards,

Peter

[crappidy]

Hello Peter,

now the AVB Endpoint board is listed in my avdecc controller! :) -> see endpoint.png
I work on windows/linux, so I haven't the Audio Midi Network Device Browser like you have in Mac OSX.

Some output when app_avb_lc_demo is running:

PTP Port 0 Role: Master
Setting clock source: INPUT_STREAM_DERIVED
PTP Port 0 Role: Master
MAAP reserved Talker stream #0 address: 91:E0:F0:0:35:A7

I use composer tools 14.2.1, firmware 6.1.1rc1.
Wireshark gives me the following: -> see AVB.7z

But I see nothing about an IP address?

Greets
Chris

[peter]

Hi Chris,

As I said in my last response, the AVB firmware is working at the layer below IP and so it doesn't have an IP address. Devices work at the level of MAC addresses and a protocol on top of that.

So, unless you add TCP to your AVB device you won't be able to ping it.

Regards,

Peter