You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nice board! But why do you use local libraries? Some symbols (ex. 93AA46B_OT in eco_memory) exist in upstream KiCAD repository (93AAxxB in Memory_EEPROM). What do you think about my help for creating KiCAD repository PRs for the rest of the symbols (and may be footprints) with some reworkings in reasonable cases? It would be a good idea to use symbols from the repository in rev.1.1, woudn't it?
Best regards,
Anton Lysak
The text was updated successfully, but these errors were encountered:
In most cases, local libraries were used when I couldn't find a suitable symbol in the included ones, in some cases this might have been historical and an equivalent symbol is now upstream. I would certainly welcome your help in upstreaming symbols and move towards using upstreamed symbols wherever possible.
The ECP5 symbol came from a generator (https://github.com/xesscorp/KiPart/), I'm not sure how that would work in terms of upstreaming - given the large number of pins, one would want to avoid significant manual fixes.
Perfect! Do you have any BOM for producing this board, which could be used as a datasheet source? Just because any symbol in the KiCAD repository should have the datasheet link.
Hello @daveshah1
Nice board! But why do you use local libraries? Some symbols (ex. 93AA46B_OT in eco_memory) exist in upstream KiCAD repository (93AAxxB in Memory_EEPROM). What do you think about my help for creating KiCAD repository PRs for the rest of the symbols (and may be footprints) with some reworkings in reasonable cases? It would be a good idea to use symbols from the repository in rev.1.1, woudn't it?
Best regards,
Anton Lysak
The text was updated successfully, but these errors were encountered: