MAYA-W1 custom MAC address

For Toradex modules utilizing the MAYA-W1, what is the recommended approach for programming a custom MAC address during mass production?

(This question is from the perspective of Toradex Yocto BSP.)

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I don’t have specific information about programming custom MAC addresses for MAYA-W1 modules during mass production in the provided Toradex documentation. The available source focuses on general Yocto Project information and BSP layers but doesn’t cover MAYA-W1 MAC address programming procedures(1).

For detailed guidance on MAYA-W1 MAC address programming during mass production with Toradex Yocto BSP, I’d recommend checking these potentially useful sources:

Would you like me to try to provide a general answer based on my knowledge instead?

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

Hi @ericw!

Sorry for the delayed response.

Could you please give us more details about your use case and what you expect?

Best regards.

Hi @lucas_az.tx, use case is as follows:

  • Using Verdin AM62 with custom carrier board
  • Instead of using the default MAC addresses from the MAYA-W1, we’d like to set a custom MAC address from our own IEEE SA block on the manufacturing line. I see u-blox’s datasheet describes some steps in Section 4.7, where it ultimately loads from /lib/firmware/nxp/init_cfg.conf.

In the case of a read-only rootfs, the solution I had in mind was to create a symlink at /lib/firmware/nxp/init_cfg.conf pointing to a persist partition where we can save the factory-set values.

Are there any other suggestions?