Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Issues with DSP libraries #29

Open
evanshultz opened this issue Dec 5, 2017 · 5 comments
Open

Issues with DSP libraries #29

evanshultz opened this issue Dec 5, 2017 · 5 comments
Labels
Help wanted Workforce is very welcomed KLC issue

Comments

@evanshultz
Copy link
Collaborator

See #9 (comment): missing or wrong default footprints, broken FPfilters, etc.

@evanshultz evanshultz added Help wanted Workforce is very welcomed KLC issue labels Dec 5, 2017
@SchrodingersGat
Copy link
Contributor

The DSP_ libraries require attention to fix the broken footprint associations

@antoniovazquezblanco
Copy link
Collaborator

I use Microchip DSPs and the looks are not consistent between different symbols.

Also microchip, depending on the package changes pin numbering so I think it would be a good idea to provide a symbol for each packaging option otherwise users may find problems in the future but this requires a good amount of work I cannot contribute right now.

@bobc bobc mentioned this issue Dec 12, 2017
@bobc
Copy link
Contributor

bobc commented Dec 13, 2017

DSP_Freescale contains only 1 component which is quite obsolete, not worth fixing, maybe worth moving to "old and obsolete" category. Also, all Freescale parts are now branded NXP (at time of writing !).

DSP_Texas also contains 1 component which is obsolete. Also suggest move to "legacy, not maintained" category.

I submitted PR to fix DSP_Microchip_DSPIC33. I did not change the existing packages there which seem to be correct for 44 pin QFN and TQFP.

@aracosta1
Copy link
Contributor

Hello, I can help by adding the Texas TMS320F28xxx series.
Should the multiple functions of every GPIO be indicated or it's better to just call the pin with the only GPIO number ?

Since the devices have a lot of pin should we creata a single component or a multiple unit component to have smaller object in the schematics ?

@chschlue
Copy link
Contributor

chschlue commented Aug 5, 2020

Generally, we add two pin functions max.
Whether it's better to split symbols always depends, but if you add _Split to those it's easy to add a monolithic version later.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Help wanted Workforce is very welcomed KLC issue
Projects
None yet
Development

No branches or pull requests

6 participants