infineon4engi@twitter infineon4engineers infineon@linkedin infineon@youtube
twitter Facebook Linkedin Youtube

Banner_Aurix_Competition Banner_AURIX_Security-Solution Banner_AURIX_Safety_Products ShieldBuddy TC275 Banner_AURIX_OnzerOS Banner_AURIX_DevelopmentStudio


+ Reply to Thread
Results 1 to 9 of 9

Thread: What are the differences between an Infineon MC-ISAR product and iLLD?

  1. #1
    New Member New Member Lina is on a distinguished road
    Join Date
    Oct 2019
    Posts
    27
    Points
    187.5

    What are the differences between an Infineon MC-ISAR product and iLLD?

    Hi AURIX community,

    What are the differences between an Infineon MC-ISAR product and iLLD?

    Thank you!
    Regards
    Lina



    #8042000 13349

  2. #2
    Intermediate Intermediate Mr.AURIX is on a distinguished road
    Join Date
    Oct 2019
    Posts
    137
    Points
    1405
    Hi Lina,


    Infineon offer both MC-ISAR Product, the AUTOSAR compliant MCAL, and Low Level Driver (iLLD) package. Although both MC-ISAR and iLLD are considered to be low level drivers abstracting parts of the hardware layer, the former is AUTOSAR compliant and undergoes validation, while the latter is offered without validation and any liability responsibility, and it is not developed according to AUTOSAR standards. Furthermore, Infineon iLLD is free-of-charge, while MC-ISAR product is not.

    Best regards

    Mr. AURIX™

  3. #3
    Beginner Beginner bbogdanmircea is on a distinguished road
    Join Date
    Nov 2019
    Posts
    39
    Points
    347.5
    Hello Mr.AURIX, I have a question related to MC-ISAR and iLLD.
    I see that iLLD has for some module some additional functionality that is not included in the MC-ISAR, for example for the CCU6 in the iLLD there are the PwmHl functions that make it
    quite easy to implement PWMs for driving MOSFET for inverters, but there is no such an implementation in MC-ISAR.
    In this case, is it possible to take the implementation from iLLD?
    Is there any guide for integrating iLLD together with MC-ISAR or how should this be done, as the structure for the iLLD and the MC-ISAR is totally different for CCU6 for example.

  4. #4
    Advanced Advanced UC_wrangler will become famous soon enough
    Join Date
    Jun 2019
    Posts
    287
    Points
    5980
    The Infineon MCAL only includes the components defined by AUTOSAR. The iLLD includes code for nearly every AURIX peripheral.

    I wouldn't attempt integrating MCAL and iLLD for the same peripheral (e.g., GTM PWM). Including an iLLD component is otherwise easy.

  5. #5
    Beginner Beginner bbogdanmircea is on a distinguished road
    Join Date
    Nov 2019
    Posts
    39
    Points
    347.5
    Ok, thanks for the answer, then if I want to implement PwmHl as it is done in the iLLD but keep the MC-ISAR how should I do it?
    The obvious way would be to copy the iLLD files for PwmHl and interface them with the MC-ISAR somehow without redefining the configuration for the PWM in 2 places?

  6. #6
    Advanced Advanced UC_wrangler will become famous soon enough
    Join Date
    Jun 2019
    Posts
    287
    Points
    5980
    This type of iLLD / MCAL hack is a common question, but of course there's no blanket answer. The configuration would have to be defined twice, and you'd have to dive into the MCAL source code to make sure there weren't hidden dependencies between interrupts, etc. Tricky business.

  7. #7
    Beginner Beginner bbogdanmircea is on a distinguished road
    Join Date
    Nov 2019
    Posts
    39
    Points
    347.5
    Thanks for the answer.
    If my application sw is not AUTOSAR but I will use the MCAL ISAR in the hope that in the future the application will be also AUTOSAR, what is then a good solution to integrate the PwmHl?

  8. #8
    Advanced Advanced UC_wrangler will become famous soon enough
    Join Date
    Jun 2019
    Posts
    287
    Points
    5980
    Hi bbogdanmircea. In my personal opinion, you should just incorporate the iLLD as-is, and switch to the AUTOSAR PWM driver when the time comes. You could take on the task of creating an AUTOSAR-compatible PWM API and translate that to iLLD, but that would be a Herculean effort when you're going to end up paying for the MCAL anyway.

  9. #9
    Beginner Beginner bbogdanmircea is on a distinguished road
    Join Date
    Nov 2019
    Posts
    39
    Points
    347.5
    Just let me know if I understood this correctly: I should disable the PWM driver from the MCAL and integrate the iLLD for PWM together with the PWMHl?
    Currently I have both of them both active, I could compile and test the PWMHl without any problems, as I will use only the PWMHl and no other PWM functionality for MCAL.
    Anyway I will double check if disabling the PWM in MCAL will not totally break the setup.
    Now I see in MCAL that there is a reference in Mcu/Ccu to the Ccu60 and Ccu61 which I think are used also by the PwmHl in the iLLD.
    I wonder what happens if the the Ccu in the Mcal is not synced to what is done in the PwmHl ...
    I see that there is a possibility that Ccu60 is used by the ADC Driver with T12 or T13 Clk, is this for triggering ADC sampling synced with the PWMHl?
    Last edited by bbogdanmircea; Jan 17th, 2020 at 01:35 AM.

+ Reply to Thread
Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.