<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en" style="--code-editor-font: var(--default-mono-font, "GitLab Mono"), JetBrains Mono, Menlo, DejaVu Sans Mono, Liberation Mono, Consolas, Ubuntu Mono, Courier New, andale mono, lucida console, monospace;">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title>
GitLab
</title>
<style data-premailer="ignore" type="text/css">
a { color: #1068bf; }
</style>
<style>img {
max-width: 100%; height: auto;
}
body {
font-size: .875rem;
}
body {
-webkit-text-shadow: hsla(0,0%,100%,.01) 0 0 1px;
}
body {
font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji"; font-size: inherit;
}
</style>
</head>
<body style="font-size: inherit; -webkit-text-shadow: hsla(0,0%,100%,.01) 0 0 1px; font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji";">
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.rtems.org/ppisa">Pavel Pisa</a>
<a href="https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1271#note_155420">commented</a>:
</p>
<div class="md" style="position: relative; z-index: 1; color: #3a383f; word-wrap: break-word;">
<p dir="auto" style="color: #3a383f; margin: 0px 0px 1rem;" align="initial">Generally it worth to resolve conflicting pins in TMS570LC4357 header. But I expect that they are result of mapping all pins described on TMS570LC43 HDK where some groups of pin have alternatives. So may it be the conflicting pins should be listed on some alternatives fragments.</p>
<p dir="auto" style="color: #3a383f; margin: 0px 0px 1rem;" align="initial">There seems to be problem, that even definitions of some pins and functions combinations are missing. I think (not sure) that we have that right on TMS570LS3137... It would worth to add at least definitions of pins/balls used for MII on 43 Launchpad see <a href="https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/48" title="rtemslwip/tms570: Bringup lwIP network stack on TI TMS570LC4357 BSP (LaunchXL2-570LC43)" class="gfm gfm-merge_request" data-original="https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/48" data-link="false" data-link-reference="true" data-merge-request="2791" data-project="15" data-project-path="rtems/pkg/rtems-lwip" data-iid="48" data-container="body" data-placement="top" data-reference-type="merge_request" style="margin-top: 0px;">rtems/pkg/rtems-lwip!48</a> and commit <a href="https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/48/diffs?commit_id=a92a54494dde3d5c1f1fb5aa36c03231a37dad28" title="rtemslwip/tms570: Bringup lwIP network stack on TI TMS570LC4357 BSP (LaunchXL2-570LC43)" class="gfm gfm-merge_request" data-original="temslwip/tms570: Bringup lwIP network stack on TI TMS570LC4357 BSP (LaunchXL2-570LC43)" data-link="true" data-original-href="https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/48/diffs?commit_id=a92a54494dde3d5c1f1fb5aa36c03231a37dad28" data-link-reference="true" data-merge-request="2791" data-project="15" data-project-path="rtems/pkg/rtems-lwip" data-iid="48" data-container="body" data-placement="top" data-reference-type="merge_request">temslwip/tms570: Bringup lwIP network stack on TI TMS570LC4357 BSP (LaunchXL2-570LC43)</a>. If I remember well we have prepared some really basic list of pins for 4357 somehow after main 3137 work by some scripting, but we have not own 4357 at that time nor finished pins and BSP, it has been done by others. Important part to allows pimux with separate inputs mapping specific to 4357 has been introduced</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style="display: block; font-size: 14px; color: #3a383f; line-height: 1.6em; overflow-x: auto; border-radius: .25rem; position: relative; font-family: "GitLab Mono", "JetBrains Mono", "Menlo", "DejaVu Sans Mono", "Liberation Mono", "Consolas", "Ubuntu Mono", "Courier New", "andale mono", "lucida console", monospace; font-variant-ligatures: none; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0px 0 1rem; padding: 12px; border: 1px solid #dcdcde;"><code style="font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: .25rem; white-space: pre; margin-top: 0px; font-family: "GitLab Mono", "JetBrains Mono", "Menlo", "DejaVu Sans Mono", "Liberation Mono", "Consolas", "Ubuntu Mono", "Courier New", "andale mono", "lucida console", monospace; font-variant-ligatures: none; overflow-wrap: normal; padding: unset;"><span id="LC1" class="line" lang="plaintext" style="margin-top: 0px;">#define TMS570_PIN_WITH_IN_ALT(pin_num_and_fnc, pin_in_alt_num_and_fnc) \</span>
<span id="LC2" class="line" lang="plaintext"> ((pin_num_and_fnc) | ((pin_in_alt_num_and_fnc) << TMS570_PIN_IN_ALT_SHIFT))</span></code></pre>
<copy-code></copy-code><insert-code-snippet></insert-code-snippet>
</div>
<p dir="auto" style="color: #3a383f; margin: 0px 0px 1rem;" align="initial">So for pins which have this another register to choose input from peripheral it is necessary to define what should be written to regular MMR (0 to 37) and what into this another direction MMR (80 to 80).</p>
<p dir="auto" style="color: #3a383f; margin: 0px 0px 1rem;" align="initial">It would be ideal to coordinate changes with <a href="https://gitlab.rtems.org/ar-in0" title="Armaan Chowfin" class="gfm gfm-project_member js-user-link" data-user="2058" data-original="@ar-in0" data-container="body" data-placement="top" data-reference-type="user" style="color: #284779; background-color: #cbe2f9; border-radius: .25rem; margin-top: 0px; padding: 0 2px;">@ar-in0</a> to get correct names into RTEMS system, and add an option for build to switch to Launchpad from default HDK. Then the LwIP change can be more readable and work for both Lauchapd and HDKs.</p>
<p dir="auto" style="color: #3a383f; margin: 0px;" align="initial">I try to help as my time allows.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #626168;">
—
<br>
<a href="https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1271#note_155420">View it on GitLab</a>.
<br>
You're receiving this email because of your account on <a target="_blank" rel="noopener noreferrer" href="https://gitlab.rtems.org">gitlab.rtems.org</a>. <a href="https://gitlab.rtems.org/-/sent_notifications/4-3wu0jo1paaatlf9nwf6qjm17h-1d/unsubscribe" target="_blank" rel="noopener noreferrer">Unsubscribe</a> from this thread · <a href="https://gitlab.rtems.org/-/profile/notifications" target="_blank" rel="noopener noreferrer" class="mng-notif-link">Manage all notifications</a> · <a href="https://gitlab.rtems.org/help" target="_blank" rel="noopener noreferrer" class="help-link">Help</a>
<span style="color: transparent; font-size: 0; display: none; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0;">
Notification message regarding https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1271#note_155420 at 1784931985
</span>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1271#note_155420"}}</script>
</p>
</div>
</body>
</html>