Apr 18, 2020
08:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 18, 2020
08:56 PM
Hello Support,
In the Aurix 2G User Manual Part 1, Master TAG ID Table in doesn't have LMU Module entry for the Module Column as shown below.
Can you please provide me the updated Table with LMU entry also?
Best Regards
In the Aurix 2G User Manual Part 1, Master TAG ID Table in doesn't have LMU Module entry for the Module Column as shown below.
Can you please provide me the updated Table with LMU entry also?
Best Regards
- Tags:
- IFX
8 Replies
Apr 19, 2020
06:22 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 19, 2020
06:22 AM
The LMU isn't a bus master.
Apr 19, 2020
04:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 19, 2020
04:19 PM
Hello Support,
In the attached Matrix, DAM0 and LMU0, both are shown as Slave Connect Interface [SCI].
But DAM0 is in the Table Above from Master Tag ID, while it not shown in the MCI side of the Matrix shown below.
What is the rationale for not showing DAM0 as MCI side?
Best Regards
In the attached Matrix, DAM0 and LMU0, both are shown as Slave Connect Interface [SCI].
But DAM0 is in the Table Above from Master Tag ID, while it not shown in the MCI side of the Matrix shown below.
What is the rationale for not showing DAM0 as MCI side?
Best Regards
Apr 20, 2020
12:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 20, 2020
12:36 AM
DAM0 isn't a bus master.
Apr 20, 2020
05:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 20, 2020
05:17 AM
Hello Support,
According to the reply, LMU0 and DAM0, both are not Bus Masters.
But DAM0 is in the Master Tag Table as shown below while LMU is not there.
Can you please help me understand the rationale for this difference with some more details of behavior?
Best Regards
According to the reply, LMU0 and DAM0, both are not Bus Masters.
But DAM0 is in the Master Tag Table as shown below while LMU is not there.
Can you please help me understand the rationale for this difference with some more details of behavior?
Best Regards
Apr 20, 2020
06:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 20, 2020
06:03 AM
On further investigation: DAM0 and DAM1 can read from PFLASH, but only write to DAM memory.
Apr 20, 2020
08:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 20, 2020
08:52 AM
There was a master interface planned for DAM also. Therefore two TAG-Numbers are reserved for this. That's all. This TAG Numbers are not used, see chapter 8 for DAM implementation.
Apr 21, 2020
04:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 21, 2020
04:37 AM
Hello Support,
While reading Aurix 2G User Manual Part1 Revision 1.4, I found the following snippet shown below which mentions IOM as Bus Master.
But I am unable to find any entry for IOM within the Master Tag Table shown above in this trail.
I could find HSM=0x3 and Cerberus=0x1C for Master Tag. But nothing for IOM.
Please let me know about this discrepancy.
Best Regards
While reading Aurix 2G User Manual Part1 Revision 1.4, I found the following snippet shown below which mentions IOM as Bus Master.
But I am unable to find any entry for IOM within the Master Tag Table shown above in this trail.
I could find HSM=0x3 and Cerberus=0x1C for Master Tag. But nothing for IOM.
Please let me know about this discrepancy.
Best Regards
Apr 21, 2020
05:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 21, 2020
05:42 AM
Looks like a typo: IOM is not a bus master. Investigating whether it's supposed to be Ethernet (my best guess).
EDIT: It's supposed to be IO32E (the DAPE calibration interface). In the list to fix.
EDIT: It's supposed to be IO32E (the DAPE calibration interface). In the list to fix.