Armaan Chowfin commented on a discussion on spec/build/bsps/arm/tms570/optboardlchxl2.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1434#note_157753 > +- env-enable: null > +build-type: option > +copyrights: > +- Copyright (C) 2020 embedded brains GmbH & Co. KG > +default: > +- enabled-by: true > + value: false > +description: | > + If set to true, then the board specific setup selects the > LAUNCHXL2-570LC43 > + LaunchPad wiring instead of the Hercules Development Kit (HDK) wiring. > The > + two boards use the same TMS570LC4357 chip but route the EMAC MII signals > to > + different terminals, and the LaunchPad drives its PHY reference clock and > + reset from the chip. Only meaningful when TMS570_VARIANT is 4357. > +enabled-by: true > +links: [] > +name: TMS570_BOARD_LCHXL2_570LC43 1. The pin mappings are now complete for the 4357. @ppisa wanted a new board option. 2. EMAC pin mappings are a binary choice for HDK and launchpad, but `BOARD_LCHXL2` right now also controls some PHY wiring options. (ex. which clk drives PHY - `TMS570_PHY_REFCLK_ECPDIV` , PHY power down pins - `TMS570_PHY_PWRDOWN_GIOA_PIN` ). An option just for EMAC pin mappings could be a better choice. 3. A terminology note: https://www.ti.com/lit/ds/symlink/tms570lc4357.pdf?ts=1787465610186&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTMS570LC4357 table 4-29 names "default" and "alternate" terminals ("default" used by launchpad, "alternate" used by HDK). -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1434#note_157753 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-20qnpgtgpqvjqlgc2qtnwgotb-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
