Hey guys,
I work at the moment with the 200 MC Audio board and the I2S Gibabit AVB Demo. AN00202, I think.
This example has one absolutely interresting part. Updating over ethernet (AVB).
So I tried to "update" my board with Riedel AVB Manager, chose the bin\*.xe file and wait. ...
After 2.7% the AVB Manager gave me an error:
The value in the address field is within the memory map but is part of an invalid region.
So I thougt, make should get an special argument. But I couldn´t find anything in this direktion. Even in the tutorials, datasheet or anywhere else (TSN lib).
So if someone had an idea where I could look at, would embellish my weekend :)
Cheers,
Sebastian
Firmware Update over AVB Topic is solved
-
- XCore Addict
- Posts: 230
- Joined: Wed Mar 10, 2010 12:46 pm
Have you tried using the avdecc controller (https://github.com/audioscience/avdecc-lib)?
There is a guide of how to flash, create upgrade images and do the upgrade using it in the AVB Daisy Chain Design Guide.
I can confirm that I managed to build the avdecc controller from scratch yesterday (just need to remember to do the git submodule init / git submodule update).
It enumerated my device, and I attempted to upgrade the firmware but it failed. Re-reading the document, I missed out the following step:
so that may be what caused it to fail. Let me know how you get on.
Unfortunately, for me the Riedel AVB Manager just doesn't even see my MC Audio Board (running AN00202 firmware) as an AVB device.
Peter
There is a guide of how to flash, create upgrade images and do the upgrade using it in the AVB Daisy Chain Design Guide.
I can confirm that I managed to build the avdecc controller from scratch yesterday (just need to remember to do the git submodule init / git submodule update).
It enumerated my device, and I attempted to upgrade the firmware but it failed. Re-reading the document, I missed out the following step:
Code: Select all
$ select 0 0 0
Unfortunately, for me the Riedel AVB Manager just doesn't even see my MC Audio Board (running AN00202 firmware) as an AVB device.
Peter
thank you for the link to the XMOS AVB-DC Design Guide. I didn't know that before.
So I tried it like descriped in 6.3
Take a while to compile the avdecc :)
->factory Image
->upgrade Image
When I now use avdecccmdline, the program gives me the error:
On next step I tried to use Riedel. This program "updates" the board with an reboot after finishing it.
But nothing happend. The board boots with the same version than before.
And an "normal" switch without AVB to my PC.
So I tried it like descriped in 6.3
Take a while to compile the avdecc :)
->factory Image
->upgrade Image
When I now use avdecccmdline, the program gives me the error:
Maby there are some differences to the xflash tool for the xCore-200.Erasing image...
[NOTIFICATION] (RESPONSE_RECEIVED, 0x2297fffe800806, START_OPERATION, ENTITY, 0, IN_PROGRESS, 0x2)
[LOG] ERROR (RESPONSE_RECEIVED, 0x2297fffe800806, START_OPERATION, ENTITY, 0, 37, IN_PROGRESS)
Error: Erase failed.
On next step I tried to use Riedel. This program "updates" the board with an reboot after finishing it.
But nothing happend. The board boots with the same version than before.
I use the version 1.11.1.0Unfortunately, for me the Riedel AVB Manager just doesn't even see my MC Audio Board (running AN00202 firmware) as an AVB device.
And an "normal" switch without AVB to my PC.
-
- XCore Addict
- Posts: 230
- Joined: Wed Mar 10, 2010 12:46 pm
I'm using version 1.12.2.0, and an AVB switch (Extreme Networks Summit X440-8t). I'll have to try with a non-AVB switch...
-
- XCore Addict
- Posts: 230
- Joined: Wed Mar 10, 2010 12:46 pm
I can confirm that having the following to originally flash my image:
The I can successfully do an EFU of my device using Riedel AVB Manager Version 1.12.2.0.
I had to plug the board directly into my PC (no switch used) in order for it to be seen and work. I have yet to try it through a switch.
I was using lib_tsn, firmware 7.0.3 (not publicly available yet) but there should be no changes between 7.0.2 and 7.0.3 that will affect this.
Code: Select all
xflash -- boot-partition-size 262144 <binary>.xe[code]
Then using the following to create an image:
[code]xflash --factory-version 14.0 --upgrade 1 <binary>.xe -o image.bin
I had to plug the board directly into my PC (no switch used) in order for it to be seen and work. I have yet to try it through a switch.
I was using lib_tsn, firmware 7.0.3 (not publicly available yet) but there should be no changes between 7.0.2 and 7.0.3 that will affect this.
It worked.
A big thank to you peter :)
A big thank to you peter :)