Factory OTP content Topic is solved

[Oddworld]

Hi everyone,

I am working on a custom AVB project based on xCore-200 Multi-channel audio platform.

I had my PCB assembled and now I am working on the software.

I have adapted the "Gigabit Ethernet AVB endpoint example using I2S master" exemple but when trying to run it on my board I get :

xrun: Program received signal ET_ECALL, Application exception.
      0x00046e5c in __main__main_tile_0_task_15 (frame=0x7e650) at ../src/main.xc:243
      243                if (otp_board_info_get_mac(otp_ports0, 0, mac_address) == 0)
 

It seem that the core is not able to read the OTP (where should be stored the MAC address).

I wonder if this OTP memory is already factory pre-programmed whith the MAC address or not. I think the answer is no which will explain why the software cannot reachs it.

Does anyone have an idea how to programm this MAC address in OTP ? I am not able to find documentation on this subject.

Thanks

Hi everyone,

I am working on a custom AVB project based on xCore-200 Multi-channel audio platform.

I had my PCB assembled and now I am working on the software.

I have adapted the "Gigabit Ethernet AVB endpoint example using I2S master" exemple but when trying to run it on my board I get :

xrun: Program received signal ET_ECALL, Application exception.
      0x00046e5c in __main__main_tile_0_task_15 (frame=0x7e650) at ../src/main.xc:243
      243                if (otp_board_info_get_mac(otp_ports0, 0, mac_address) == 0)
 

It seem that the core is not able to read the OTP (where should be stored the MAC address).

I wonder if this OTP memory is already factory pre-programmed whith the MAC address or not. I think the answer is no which will explain why the software cannot reachs it.

Does anyone have an idea how to programm this MAC address in OTP ? I am not able to find documentation on this subject.

Thanks

[mon2]

The following document may help but is related specifically to the XCORE-200 kit:

https://www.xmos.com/download/private/D ... s(1.0).pdf

Reference:

https://www.xmos.com/search/content?ter ... ac+address

Being that you are now working with OTP and your target ( xCore-200 Multi-channel audio platform ) may be treated differently than the XCORE-200 board, take great caution before using these commands and/or wait for additional feedback from others. Treat the above as a FYI.

[Oddworld]

Hi mon2,

Thanks for your help, that is exacly what I was looking for.

You are right about beeing careful, I do not want to regret having explored the meaning of "OTP" ;).

Anyway, since my MCU is the same as the one on the eXplorer-kit board (XE216-512-TQ128), I think the risk is minor.

The only thing that bother me is the --target XCORE-200-EXPLORER argument of the command :

xburn --target XCORE-200-EXPLORER --mac-address 00:22:97:80:03:nn

I am not sure what it really implies, I guess it may only be for the debugger to check the target before burning but I will wait someone confirmation before going further.

 

 

[Vineela]

Hi,

It should be your xn file name ie,

xburn --target XE216-512-TQ128 --mac-address 00:22:97:80:03:nn

Hope this helps.

Thanks,

Vineela

[duanes]

I am having this same problem on the same eval board, assuming no MAC address has been programmed. But when I enter

xburn --target XE216-512-TQ128 --mac-address 00:22:97:80:03:2A

I get

xburn: error: Error: XN11043 Error opening file ''.

What am i doing wrong?

[matthew1]

xburn --target XE216-512-TQ128 --mac-address 00:22:97:80:03:2A

There's a missing "-C20" on the target. Try:

Code: Select all

xburn --target XE216-512-TQ128-C20 --read

to see if the MAC address is programmed.

Matthew.

[mon2]

Suggest that you wait on feedback from someone who has actually used the xburn tool but believe the issue is with your --target parameter.

See here:

https://www.xmos.com/support/tools/docu ... nent=14586

Specifically, the target details must be supplied inside a platform.xn file. So xburn is searching for a file named XE216-512-TQ128.xn in your posted example.



Proceed with caution as programming is with OTP memory !!