i.MX6: How do I get from the Pinmux Utility XML to a DCD

[floriandoerfler]

I understand that I have to configure the pins used for loading the Bootloader in the DCD, so that they get configured correctly before the Bootloader starts. The hardware developers use the Pin Muxing Utility to manage the pins of the device. The barebox bootloader (and I expect also others) takes an ".imxcfg" file at compile time to build a binary DCD. So my desired Workflow is:

Pin Muxing Itility -> ? -> ".imxcfg" -> Boot Loader Tool -> Binary DCD

So the question is, what is the tool in the question mark. Does it exist or do I have to write the DCD input (.imxcfg) file by hand? Or do I go about it the wrong way?

Regards Florian

[igorpadykov]

Hi Florian

in general Processor Expert tool was designed for such purpose

and as replacement of Pin Muxing Utility

Processor Expert for i.MX|Freescale

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[floriandoerfler]

Hi Igor

Thank you for the hint! I have the Processor Expert running. So I have two hurdles to tackle:

1. My hardware developers use the Pin Muxing Utility and I should use the Processor Expert. Do you know of a way to import the Pin Muxing Utility XML into the Processor Expert?
2. From the Processor Expert I can generate C code but the input to the DCD generation tool (it looks like it's just gcc with some special arguments) seems to be a kind of Assembler. Is there a way to either get Assembler from the Processor Expert?

Cheers Florian

Here's a snippet from the start of an ".imxcfg" file for reference:

soc imx6

loadaddr 0x20000000

dcdofs 0x400

wm 32 0x020e05a8 0x00000030

wm 32 0x020e05b0 0x00000030

wm 32 0x020e0524 0x00000030

wm 32 0x020e051c 0x00000030

wm 32 0x020e0518 0x00000030

wm 32 0x020e050c 0x00000030

wm 32 0x020e05b8 0x00000030

<much more of this...>