MCUXpresso DAC debug issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUXpresso DAC debug issue

Jump to solution
1,935 Views
Bela1
Contributor III

Ladies and gentlemen,

I discovered an interesting phenomen while debugging DAC in my application.

I just wanted to turn the OpAmp buffer of DAC0 On. During debug, I've seen in the peripheral registers, that the bit BUF_EN bit is not set, however, my code sets it.

Carefully viewing onto the hex value of DAC->GCR register, I see, that the binary value is correct, it shows that bit 17 is set to 1, as I expected. However, a few lines below, BUF_EN says that the buffer is not enabled - but it is.

Is this a bug in MCUXpresso, or am I doing something wrong?

0 Kudos
Reply
1 Solution
1,849 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my apologize for the late response, I did test it on the SDK example, and I have the same behavior that you reported, let me escalate to the SDK department when I have more information I will contact you.

Best regards,
Pavel

View solution in original post

0 Kudos
Reply
6 Replies
1,777 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, I get this information from the team.

What I meant is treat this as "Not used", since bit 17 is 0. The only part that is not right is the field  explanation from the MCUXpresso peripheral register view for GCR[BUF_EN]=0 is stated "Used"

Pavel_Hernandez_0-1721842577664.png

Same as this, bit 17 is 1 - BUF_EN. The MCUXpresso peripheral register view for GCR[BUF_EN]=1 show "Not Used" is wrong.

Pavel_Hernandez_1-1721842577663.png

The most important is the GCR register bit 17. If the GCR register bit 17 is 1 - BUF_EN (0x0002_0000), bit 17 is 0 - Buf not used (0x0000_0000).

Best regards,
Pavel

0 Kudos
Reply
1,767 Views
Bela1
Contributor III
Thank You Pavel, hope it will be corrected in the next release.
0 Kudos
Reply
1,911 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, could you let me know if your test was based on an example from the SDK? or is this issue reproducible on once example on the SDK? if yes could you let me know the steps?

Best regards,
Pavel

0 Kudos
Reply
1,883 Views
Bela1
Contributor III

Hallo Pavel,

I sent You my answers by email yesterday. Unfortunately yesterday I couldn't answer here on-line. Hopefully You got it.

0 Kudos
Reply
1,850 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my apologize for the late response, I did test it on the SDK example, and I have the same behavior that you reported, let me escalate to the SDK department when I have more information I will contact you.

Best regards,
Pavel

0 Kudos
Reply
1,844 Views
Bela1
Contributor III

Hallo Pavel,

Thank You for the response. Just as info: I installed the newest MCUXpresso, v11.10.0_3148, the same symptom is still there. Hopefully it can be corrected.

Thank You again.

0 Kudos
Reply