Discrepancies between iMX6 Platform SDK and RMs

cancel
Showing results for 
Search instead for 
Did you mean: 

Discrepancies between iMX6 Platform SDK and RMs

Jump to solution
648 Views
MichaelV
Senior Contributor II

I see quite a few discrepancies between the iMX6 Platform SDK header files and the RMs.

Just one example to show what I mean:

iMX6DQ RM pdf page 936, CCM_ANALOG_MISC2n register, shows AUDIO_DIV_LSB on bit 15 and AUDIO_DIV_MSB on bit 23, but the platform SDK header file (\sdk\include\mx6dq\registers\regspmu.h) show bit 15 and 23 as reserved.

Which one should I trust?

I think the platform SDK is final, but in that case someone might want to update the RMs because I found a lot of these discrepancies between the iMX6(SDL/DQ) RMs and the platform SDK files.

Labels (1)
Tags (2)
0 Kudos
1 Solution
181 Views
MichaelV
Senior Contributor II

Not sure... It's closed when the RMs are updated and all discrepancies are gone. From my point of view I now know to take the Platform SDK as the truth, so yes, close it I guess...

View solution in original post

0 Kudos
9 Replies
181 Views
gusarambula
NXP TechSupport
NXP TechSupport

I just received confirmation that the SDK is correct. These values should be reserved and these bits should appear as such on the Reference Manual.

Thanks for pointing this error out!

0 Kudos
181 Views
MichaelV
Senior Contributor II

The CCM_ANALOG register bit was just an example. There are many discrepancies so I'd recommend someone to take a good look at those and update the RMs. I will just take the SDK as the correct information until the RMs are updated, thanks for confirming.

0 Kudos
181 Views
billkrakar
NXP Employee
NXP Employee

Hi Michel,

This item looks closed. Please confirm.

Thanks!

Bill Krakar

0 Kudos
182 Views
MichaelV
Senior Contributor II

Not sure... It's closed when the RMs are updated and all discrepancies are gone. From my point of view I now know to take the Platform SDK as the truth, so yes, close it I guess...

View solution in original post

0 Kudos
181 Views
gusarambula
NXP TechSupport
NXP TechSupport

It all points to the Reference Manual being correct and the i.MX6 having this functionality even if not implemented on the SDK. I’m investigating; I’ll let you know as soon as I have an update.

Update: The SDK is correct. These values should be marked as reserved on the Reference Manual.

0 Kudos
181 Views
admin
Specialist II

gusarambula, can you please reply with what you have found.  Thanks.

0 Kudos
181 Views
gusarambula
NXP TechSupport
NXP TechSupport

I'm very sorry. We haven't yet received confirmation on which information is correct. I'm awaiting confirmation and update as soon as I receive it.

0 Kudos
181 Views
MichaelV
Senior Contributor II

Any update on this?

0 Kudos
181 Views
jamesbone
NXP TechSupport
NXP TechSupport

gusarambula, can you please check on this topic?

0 Kudos