00:39 <awygle> marcan: re: the PPU board for byuu: i just learned that that PSoC5LPs are 1.71 to 5.5 volts, up to 4 power domains. might be good level shifting options. dropping this info here as much to remind myself as to let you know :p.

07:35 <esden> Hey! (Probably mainly a question for marcan) I have a question about how you would like me to submit PCB changes. I have located a few things that I would like to change before ordering the next revision of the board, to improve manufacturing reliability. Things that I figured out in the last run. The main things to change are: Remove grounding pads under the ESD diodes. Change the SOT-666 footprint to make sure there is

07:35 <esden> solder stop between the pads. Change all remaining rectangular pads to roundrect for better solder coverage. (and better looks ;) ) I also have some cosmetic changes I would like to make. Like making slight changes to Hana so that she looks right on white/light solder stop, making her an outline without filled polygons (I created that version already just not pushed to the repo yet.). Add an anchor footprint for the

07:35 <esden> manufacturer information. Should I just make a fork on my own repository and start committing those changes? Also should we bump the revision number of the board before or after I do the changes? Just for reference here is my branch so you can judge what I was up to: https://github.com/esden/Glasgow/tree/revC2

07:35 <esden> Sorry for the massive block of text... ;)

07:39 <whitequark> grounding pads and SOT-656 footprint are clear DFM improvements that should definitely go upstream here

07:39 <whitequark> what's an anchor footprint?

07:40 <whitequark> cosmetic changes like rect->roundrect i think are best kept to the vendor fork, since we're trying to stay close to upstream KiCAD repos where possible

07:41 <whitequark> sometimes it's just not practical because they (understandably) don't want a million footprint variants for cheaper processes, and we (understandably) don't want to use footprints that decrease yield with 5/5 rules

07:41 <esden> I will cross check the footprints I have against the newest versions in the kicad library. I think the librarians did make some improvements since the version included in the current stable.

07:41 <whitequark> updating footprints to match kicad libraries is always super welcome.

07:42 <esden> I am trying to stay as close as I can to the up stream libraries. I will have to do some research how many of the changes I want to make can be sent up stream. Indeed the desire is there to push as much as possible up stream. But I have to also be bit careful to not delay other timelines with that desire. :D

07:44 <whitequark> yes, that makes sense

08:02 <esden> ohh right. Anchor footprints: small placeholders that can be replaced with a silkscreen footprint or text. Essentially as a coordinate placeholder so that the logo or text can be added in a more automatic manner before generating gerber files for manufacturing.

08:06 <whitequark> gotcha. that would be good to have upstream.

10:14 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647663771?utm_source=github_status&utm_medium=notification

18:54 <_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/JvnHd

18:54 <_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark fd03951 - applet.interface.i2c_target: fix test.

19:11 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647801981?utm_source=github_status&utm_medium=notification

19:29 <_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/Jvn7m

19:29 <_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark b317e45 - applet: migrate to nmigen, fix coroutine-related issue.

19:45 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647810630?utm_source=github_status&utm_medium=notification

20:14 <furan-> hio

20:15 <furan-> anyone want to sell me a glasgow board?

20:15 <furan-> :-)

20:16 <furan-> I signed up for the production version

20:16 <whitequark> btw it would't quite help you with the intel board

20:16 <whitequark> because of the large amount of pins on that connector

20:17 <furan-> I was thinking for just the 4 pins. unfortunately the board is made using the high density interconnect process, the layers are *crazy* thin and the pads are very very fragile

20:17 <whitequark> ah yeah

20:17 <whitequark> magnet wire seems the way to go for this

20:17 <furan-> yeah, taht's what I used last time

20:18 <whitequark> i normally use PTFE insulated wire but that has enough springback it can tear off pads

20:18 <whitequark> well

20:18 <whitequark> it can tear off 0.5 mm pitch BGA pads, which are a bit smaller than what you have there

20:19 <furan-> actually I think I used PTFE/bodge wire last time, not my magnet wire. I'd remember the polyurethane enamel smell if I'd used magnet wire.

20:19 <furan-> but I have magnet wire, will use it this time, good idea

21:34 <_whitenotifier-3> [glasgow] emilazy opened issue #182: gateware.analyzer: FIFO tests are broken - https://git.io/Jvnd5

21:36 <_whitenotifier-3> [glasgow] emilazy opened pull request #183: Add test runner script and disable broken tests - https://git.io/JvndA

21:37 <_whitenotifier-3> [glasgow] emilazy synchronize pull request #183: Add test runner script and disable broken tests - https://git.io/JvndA

21:39 <_whitenotifier-3> [glasgow] emilazy synchronize pull request #183: Add test runner script and disable broken tests - https://git.io/JvndA

21:52 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647841253?utm_source=github_status&utm_medium=notification

21:52 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647841059?utm_source=github_status&utm_medium=notification

21:55 <_whitenotifier-3> [glasgow] emilazy synchronize pull request #183: Add test runner script and disable broken tests - https://git.io/JvndA

21:55 <_whitenotifier-3> [glasgow] emilazy commented on issue #182: gateware.analyzer: FIFO tests are broken - https://git.io/JvnF4

22:06 <_whitenotifier-3> [glasgow] Failure. The Travis CI build failed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647842093?utm_source=github_status&utm_medium=notification

22:12 <_whitenotifier-3> [glasgow] Success. The Travis CI build passed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647845937?utm_source=github_status&utm_medium=notification

22:35 <_whitenotifier-3> [glasgow] whitequark closed pull request #183: Add test runner script and disable broken tests - https://git.io/JvndA

22:35 <_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark pushed 2 commits to master [+1/-0/±2] https://git.io/Jvnb3

22:35 <_whitenotifier-3> [GlasgowEmbedded/glasgow] emilazy f2546d8 - test: add script to run tests.

22:35 <_whitenotifier-3> [GlasgowEmbedded/glasgow] emilazy 2a8bfc9 - gateware.analyzer: disable broken FIFO tests.

22:50 <_whitenotifier-3> [glasgow] Success. The Travis CI build passed - https://travis-ci.org/GlasgowEmbedded/glasgow/builds/647855180?utm_source=github_status&utm_medium=notification