• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 472 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62: Conflict and build errors seen while changing McASP instance in SYSCONFIG

Dee Vee
Prodigy 100 points

Part Number: SK-AM62
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

    I am working in AM62x.  Currently the sysconfig for the loopback example code is configured as attached.

McASP1 is configured as McASP instance. The input and output AXR pins are configured for McASP1. When I see the code, MCASP1 registers are being configured. Which seems correct.  And the serializers 0 and 1 are configured for McAsp1 which also looks ok.

But why is there a reference to CONFIG_MCASP0? Is the McASP0 also configured somewhere?

So I tried to change the instance from McASP1 to McASP0.  And changed the serializer to  McASP0 And it shows conflicts and produces build errors.  

error: CONFIG_MCASP0(/drivers/mcasp/mcasp) mcaspSer[0].MCASP.$assign: Resource conflict
MCASP0 is already in use by CONFIG_MCASP0(/drivers/mcasp/mcasp) MCASP

Why is the reference to McASP0 coming here? While, McASP1 is the intended instance, the hardware pins for this instance is configured. 

Please help understand this.

Thanks

Deepa

  • 0
    TI__Genius 12895 points

    Hi Deepa,

    I am looking into this. Please expect reply by tomorrow afternoon.

    Thanks and Regards,
    Ritapravo

  • +1
    TI__Genius 12895 points

    Hi Deepa,

    I used MCASP instance as 'MCASP1' and also configured the MCASP serializer 0 and 1 to 'MCASP1'. I got the warning "Resource conflict" while selecting MCASP1 in sysConfig. But there is also an option to suppress the warning just beside it in sysConfig. I suppressed the warning and rebuilt the project and I was able to run the example without any errors. Can you please try to suppress the 'Resource conflict' warning and let us know?

    Dee Vee said:
    But why is there a reference to CONFIG_MCASP0? Is the McASP0 also configured somewhere?

    As I can see from the image you provided, CONFIG_MCASP0 is the name of the config. You can also change it to anything else (say 'CONFIG_MCASP1') if you wish. For that you will also have to change the line 95 of mcasp_loopback.c [ line 95: mcaspHandle = MCASP_getHandle(CONFIG_MCASP1);]

    Regards,
    Ritapravo

  • 0 in reply to Ritapravo Sarker
    Prodigy 100 points

    Hi Ritapravo,

         Thanks for checking this out!!

        When I suppress the warning,  I can build and run. I don't see any hardware conflicts. 

       1.  But the question is, why it should it show a conflict in the first place? I would like to understand that. 

       2.  And one more question that I have. Can you please help me understand?  

        I have a doubt. Please let me know if my understanding is correct.

        As per the document, it says there should be 16 serializers associated to AXRn pin. I am a little unsure. 

     So does this mean - 

    16 unique serializers each for AXR0-15 for MCASP2

    4 unique serializers for AXR0-3 for McASP0

    6 unique serializers for AXR0-5 for McASP1. 

    So we have 26 different serializers for the different MCASPs?

    Please let me know if this understanding is correct.

    Thanks a lot !

    Deepa

  • 0 in reply to Dee Vee
    TI__Genius 12895 points

    Hi Deepa,

    Dee Vee said:
    But the question is, why it should it show a conflict in the first place? I would like to understand that. 

    One of the roles of SysConfig is to avoid conflicts by making sure that a resource in not used multiple times. In the loopback example, we intend to use the MCASP1 instance multiple times (in MCASP instance, MCASP Serializer Configuration 0 and MCASP Serializer Configuration 1). So, the warning is expected, and should be suppressed manually.

    Regards,
    Ritapravo