ChanServ changed the topic of #glasgow to: glasgow interface explorer · code https://github.com/GlasgowEmbedded/glasgow · logs https://freenode.irclog.whitequark.org/glasgow · discord https://1bitsquared.com/pages/chat · production https://www.crowdsupply.com/1bitsquared/glasgow · no ETAs at the moment
Stormwind_mobile has quit [Ping timeout: 265 seconds]
Stormwind_mobile has joined #glasgow
pinoaffe has quit [Quit: killed]
_whitelogger has joined #glasgow
levi has quit [Ping timeout: 246 seconds]
emilazy has quit [Ping timeout: 244 seconds]
analprolapse has quit [Ping timeout: 244 seconds]
emilazy has joined #glasgow
analprolapse has joined #glasgow
analprolapse has quit [Excess Flood]
emilazy has quit [Ping timeout: 260 seconds]
electronic_eel_ has joined #glasgow
electronic_eel has quit [Ping timeout: 256 seconds]
analprolapse has joined #glasgow
levi has joined #glasgow
emilazy has joined #glasgow
PyroPeter_ has joined #glasgow
PyroPeter has quit [Ping timeout: 264 seconds]
PyroPeter_ is now known as PyroPeter
<d1b2> <tnt> @esden Apparently not :p
<d1b2> <esden> I underestimated how much time the "let me just do the tc interface boards" part will take >_<
<d1b2> <esden> I had to make photos, product description, all the posts ... yadda yadda yadda >_<
<d1b2> <esden> And now I ran out of spoons for today.
_whitelogger has joined #glasgow
electronic_eel_ is now known as electronic_eel
tomtastic has quit [Ping timeout: 265 seconds]
tomtastic has joined #glasgow
pinoaffe has joined #glasgow
bvernoux has joined #glasgow
<d1b2> <Attie> I'm looking at the BOM in more detail now... bit surprised to see an ATECC508A (crypto co-proc / U34)
<d1b2> <Attie> what's that used for here?
<whitequark> Attie: it was an experiment that i consider failed
<d1b2> <Attie> ah, shame
<whitequark> the idea is that fraudlent returns are a problem
<whitequark> for vendors commercially selling glasgows
<whitequark> so the atecc could authenticate them
<d1b2> <Attie> i see, thanks - certainly intriguing
<whitequark> but... it's expensive, takes board space, and actual vendors like 1b2 are not really interested in it
<d1b2> <Attie> nice, in that case i might leave no-fit if that won't cause any problems
<whitequark> you can just DNP it yes
<whitequark> it's not actually used
<d1b2> <Attie> thanks for bunnie's article, i'll add it to my reading list
<whitequark> in fact i don't believe anyone has ever communicated with the ATECC on glasgow
<d1b2> <Attie> ha, fair enough
<d1b2> <Attie> mind me asking why / how it failed, or what didn't work out?
<d1b2> <Attie> or was it largely driven by lack of interest
<d1b2> <Attie> or was it largely driven by lack of interest
<whitequark> latter
<whitequark> it's also a piece of complex crypto that i could have just gotten wrong in the end
<whitequark> but i mostly never got around to actually using it
<whitequark> and the lack of interest led me to the conclusion it's unnecessary
<whitequark> it was always contentious
<whitequark> i think we can drop it from revC2, if we didn't already (cc electronic_eel)
<d1b2> <Attie> ok, thanks for the info!
<noopwafel> I think it is long-gone in C2
<noopwafel> yes
<electronic_eel> yes, it is gone from revC2
<electronic_eel> I think the space will be re-used for the new button (the eeproms will be moved to where the ATECC was to make space for the button)
<electronic_eel> but esden wanted to do this part of the layout
<whitequark> sgtm
_whitenotifier-3 has joined #glasgow
Sellerie has quit [Quit: The Lounge - https://thelounge.chat]
kmehall has quit [Remote host closed the connection]
Sellerie has joined #glasgow
Sellerie has quit [Client Quit]
Sellerie has joined #glasgow
Sellerie has quit [Client Quit]
Sellerie has joined #glasgow
<d1b2> <Attie> does anyone have a part number for J5? the schematic references Amphenol 20021321-00040T4LF as a suggested mating connector, and I've located 20021121-00044T4LF that appears to be suitable (the without pg version)
<d1b2> <Attie> *s/pg/post/
<d1b2> <Attie> I'm also wondering about alternate parts for the Pink LED (OSK40603C1E) - I'd like to keep the flag
<d1b2> <Attie> (it seems to be a little obscure, but I'm hoping the cm can source from LCSC)
<tnt> the 20021121-00044T4LF is 44 pins not 40.
<d1b2> <Attie> oop, did i miscount?
<tnt> I think FTSH-110-01-L-DV-K-TR is the originally planned connector with keying.
<tnt> As for the leds beware that changing them might unbalance their brightness. Each resistor has been manually calibrated for that specific led part number to provide uniform brightness and not too dim, not too bright.
<d1b2> <Attie> J5 is 44 pins, correct? (2x22)
<tnt> Didn't check ... Ijust know that the 2 references you posted have different pin count :p
<d1b2> <Attie> the schematic seems to reference the 40-pin mating connector
<d1b2> <Attie> ha, okay, yes. i think the "suggested mating connector" part number is incorrect in that case
<d1b2> <Attie> re LEDs, yes I was aware of that - i'm hoping to source from LCSC, so we should be fine
<d1b2> <Attie> FTSH-110-01-L-DV-K-TR is also a 40 pin part... hmm
<d1b2> <Attie> oh, no... it's a 20 pin part - I'll use the FTSH series 40-pin equivelant with keying
<d1b2> <Attie> gosh, I shouldn't be doing this now... I'll use the FTSH series 44-pin equiv, with key
<d1b2> <Stary> just checked - j5 (lvds connector) is 44 pins http://9net.org/screenshots/1597511860.png
<d1b2> <Attie> agreed - thanks for confirming, I can be bad with numbers as may have been evidenced above
<electronic_eel> Attie: there was a bug in the schematics regarding the suggested mating connector. I think it has been corrected now in the kicad files, but not in the pdf in the revC1-subdir
<d1b2> <Attie> ah, thanks - I was indeed looking at the PDF
<electronic_eel> just use the kicad files, there you also find the suggested part for J5, which is FTS-122-01-L-DV
<d1b2> <Attie> will do, I hadn't expected the PDF / BOM to be out of alignment with the KiCAD files - I presume these are changes since revC1?
<electronic_eel> It might be
<electronic_eel> I don't remember
<d1b2> <Attie> ok, no problem
<electronic_eel> I just remember that I fixed the suggested mating connector at some time
<electronic_eel> for revC2 esden has also added holes to the board, so you can uses connectors with alignment pins
<d1b2> <Attie> ok - i was going to run with the revC1 files, would you advise using the revC2, even though it's WIP?
<electronic_eel> revC2 is nearly finished design wise, maybe 1 or 2 weeks till it is done and esden orders test boards
<electronic_eel> it will have several design-for-manufacture improvements and also new features
<electronic_eel> but we changed the adc and there is no firmware support for the new one yet, so the prototypes will not immediately work
<electronic_eel> so the question is how fast do you need the boards
<d1b2> <Attie> interesting, thanks - I had a feeling they were a little further out than that
<d1b2> <Attie> i'll put it to the group, I'd personally be happy to have a revC1 sooner (even if only by a few weeks - month or two), and potentially get a C2 once they're in production
<electronic_eel> you can take a look at the progress in the wip-revC2 branch
<electronic_eel> if you plan to build more than a handful of boards, you'll probably prefer the revC2 because of the dfm improvements. the old footprints for the level shifters, tvs diodes and resistor arrays weren't optimal and caused many people problems
<d1b2> <Attie> i see, thanks
<electronic_eel> now I can't guarantee that revC2 will fix them all, but at least we tried :)
<d1b2> <Attie> ha 🙂
<d1b2> <Attie> do you know if the issues were primarily around hand assembly, or if getting someone to do a pnp run reduced the issues?
<electronic_eel> it was mostly reported from people doing hand assembly and probably having non ideal soldering profiles
<d1b2> <Attie> I've already had people express interest in ~50 boards, so I wouldn't call it a small run...
<electronic_eel> but even esden with his pnp and experience with his solder profile had to do several reworks IIRC
<d1b2> <Attie> I was planning to over-order by a margin to deal with some level of problems, but if the failure rate might be higher than 5-10%, then it may be problematic
<d1b2> <Attie> ok, good to know, thank you
<d1b2> <Attie> rework isn't a scary prospect, but I'd obviously like to avoid it if possible
<electronic_eel> oh, and the selftest isn't fixed yet. so it is more complicated to figure out where the problems with the shifters, tvs and resistors are
<electronic_eel> but that is "just" a software thing that can be fixed with some effort of re-thinking the selftest procedure
<electronic_eel> about "scary": have a look at the level shifter size and footprint, they are tiny and love to create shorts. so you need proper equipment and a bit of experience for reworking them
<electronic_eel> with revC2 we switched to sot-363 / sc-70 for the shifters, which is easy to solder even by hand and shouldn't create any problems
<d1b2> <Attie> understood
<noopwafel> they are definitely ok to rework but it's a bit annoying and impractical if you want a lot of them
Stormwind_mobile has quit [Ping timeout: 260 seconds]
Stormwind_mobile has joined #glasgow
Stormwind_mobile has quit [Ping timeout: 265 seconds]
martling has joined #glasgow
GregNGM has joined #glasgow
Stormwind_mobile has joined #glasgow
bvernoux has quit [Quit: Leaving]
<awygle> woohoo, i am a team boi now (for some reason)!