Hi J-,
Sorry for replying late, please go ahead with my 2 questions.
As we are using our own custom board using OMAPL138 soc and connected AIC3256 device with it.
We are booting from Linux OS and detected AIC3256 using I2C interface as already mentioned in above post.
Q1-
We are using PurePath to generate *.cfg file but in default it is made according to EVM design.
But as we our using our own custom board, what are the differences and what we need to take care while generating *.cfg file.
Please elaborate the details as we are getting some issues in getting clocks at WCLK and BCLK.
Q2-
Scenario we are making *.bin file using mkcfw utility and merging it with kernel.
When we are making *.bin file it requires 4 files as input :-
1) reg_init.cfg
2) pll_48kHz.cfg
3) *.pfw (pure path framework file)
4) *.cfg (pure path framework compiled file)
In all the files some registers are programs and some repeatedly, so what do we do in this case as our end purpose is to run application as per our custom board.
Note:-
Differences might be in the crystal used in EVM and what we are using.