| ID: | 5918 |
| From: | Wojciech Krutnik <wo...@gmail.com> |
| Date: | Thu, 19 Jan 2023 01:28:17 +0100 |
| Subject: | [pcb-rnd] [sch-rnd] wishlist: terminal alternate function selection |
| replies: | 5919 from rn...@igor2.repo.hu |
--000000000000ab4ec605f29301c9 Content-Type: text/plain; charset="UTF-8" Hi, In microcontrollers, pins, beside of GPIO functionality, often have multiple alternate functions of MCU's peripherals, eg. SPI, UART, TIMER, etc. When drawing a schematic with an MCU, there's a process of assigning GPIOs. If alt functions are used, then you have to open the datasheet and find out on which pins can you connect, for example, an SPI memory. What if this data could have been embedded in symbol (probably already can in a terminal's attribute) and the user could select terminal's active alt function? The advantages I see in this approach: - Faster (don't have to relate to datasheet) - Less prone to errors, because the alt function would be directly associated with terminals, so there's no way to assign it on a wrong pin (maybe there also would be a way to prevent a situation where the same peripheral is used twice) - Ability to auto-generate gpio config for the firmware (would be nice if additional data, like direction, pull-up/dn, open drain, etc. are also provided) There are already tools from MCU manufacturers which provide similar functionality, but I think, that the schematic editor is the right place where it should be done. Regards Wojciech --000000000000ab4ec605f29301c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi,</div><div><br></div><div>In microcontrollers, pin= s, beside of GPIO functionality, often have multiple alternate functions of= MCU's peripherals, eg. SPI, UART, TIMER, etc.</div><div>When drawing a= schematic with an MCU, there's a process of assigning GPIOs. If alt fu= nctions are used, then you have to open the datasheet and find out on which= pins can you connect, for example, an SPI memory.</div><div>What if this d= ata could have been embedded in symbol (probably already can in a terminal&= #39;s attribute) and the user could select terminal's active alt functi= on?</div><div>The advantages I see in this approach:</div><div>- Faster (do= n't have to relate to datasheet)<br></div><div>- Less prone to errors, = because the alt function would be directly associated with terminals, so th= ere's no way to assign it on a wrong pin (maybe there also would be a w= ay to prevent a situation where the same peripheral is used twice)</div><di= v>- Ability to auto-generate gpio config for the firmware (would be nice if= additional data, like direction, pull-up/dn, open drain, etc. are also pro= vided)<br></div><div><br></div><div>There are already tools from MCU manufa= cturers which provide similar functionality, but I think, that the schemati= c editor is the right place where it should be done.<br></div><div><br></di= v><div>Regards<br></div><div>Wojciech<br></div></div> --000000000000ab4ec605f29301c9--
Reply subtree:
5918 [pcb-rnd] [sch-rnd] wishlist: terminal alternate function selection from Wojciech Krutnik <wo...@gmail.com>
5919 Re: [pcb-rnd] [sch-rnd] wishlist: terminal alternate function from rn...@igor2.repo.hu