<rqou>
uses "inline assembly" to call console.log :P
<azonenberg_work>
rqou: it basically does that already
<azonenberg_work>
when you call log it goes through a vector of sinks and calls write on each one
<azonenberg_work>
it's just a matter of making one that pushes to a std::string
<rqou>
how much would you hate an EmscriptenLogSink?
<rqou>
with "inline assembly"
<azonenberg_work>
lol
<azonenberg_work>
I probably would not be super happy
<rqou>
lol why not? :P
<azonenberg_work>
because eew javascript? :p
rohitksingh-demo has joined ##openfpga
Zorix has quit [Ping timeout: 276 seconds]
azonenberg_work has quit [Ping timeout: 256 seconds]
Zorix has joined ##openfpga
fitzsim` is now known as fitzsim
pie_ has joined ##openfpga
pie__ has quit [Ping timeout: 268 seconds]
m_w has joined ##openfpga
theMagnumOrange has quit [Ping timeout: 252 seconds]
pie_ has quit [Remote host closed the connection]
pie_ has joined ##openfpga
azonenberg_work has joined ##openfpga
theMagnumOrange has joined ##openfpga
<lain>
OT: anyone have opinions or experience with Copperhead OS? (secure android fork: https://copperhead.co/android/ )
<sorear>
no opinions on the product, but the maintainer/twitter spokesman understands politeness and human communication about as well as torvalds and spender
<lain>
lel
<azonenberg_work>
lol
<azonenberg_work>
but it compiles and runs :p
<azonenberg_work>
It doesn't DO anything yet
<azonenberg_work>
Welp, i have a protoc plugin now
<azonenberg_work>
Also my boat is docking in a minute so i gotta run
<azonenberg_work>
kc8apf: thanks for the hint
azonenberg_work has quit [Ping timeout: 256 seconds]
[X-Scale] has joined ##openfpga
X-Scale has quit [Ping timeout: 256 seconds]
[X-Scale] is now known as X-Scale
futarisIRCcloud has joined ##openfpga
digshadow has quit [Ping timeout: 252 seconds]
azonenberg_work has joined ##openfpga
soylentyellow has quit [Ping timeout: 256 seconds]
m_w has quit [Quit: Leaving]
soylentyellow has joined ##openfpga
theMagnumOrange has quit [Ping timeout: 240 seconds]
theMagnumOrange has joined ##openfpga
kristianpaul has quit [Quit: Lost terminal]
kristianpaul has joined ##openfpga
digshadow has joined ##openfpga
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined ##openfpga
FabM has quit [Ping timeout: 240 seconds]
m_w has joined ##openfpga
FabM has joined ##openfpga
Xark_ has quit [Read error: Connection reset by peer]
Xark has joined ##openfpga
Bike has quit [Quit: Lost terminal]
m_w has quit [Quit: leaving]
rohitksingh-demo has quit [Quit: Leaving.]
nrossi has joined ##openfpga
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
theMagnumOrange has quit [Ping timeout: 240 seconds]
theMagnumOrange has joined ##openfpga
pakesson has joined ##openfpga
futarisIRCcloud has joined ##openfpga
eduardo__ has joined ##openfpga
eduardo_ has quit [Ping timeout: 240 seconds]
m_t has joined ##openfpga
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<whitequark>
sorear: I actually found them to be quite polite on Twitter
<whitequark>
now on the rust IRC/ML/etc, they were not.
xdeller has joined ##openfpga
FabM has quit [Ping timeout: 256 seconds]
FabM has joined ##openfpga
m_t has quit [Quit: Leaving]
azonenberg_work has quit [Ping timeout: 240 seconds]
FabM has quit [Quit: ChatZilla 0.9.93 [Firefox 52.5.0/20171114221957]]
soylentyellow has quit [Ping timeout: 252 seconds]
<qu1j0t3>
sorear: It's possible they're influenced by the style of high profile jerks like Torvalds. that's one of the 2nd order effects of tolerating him
<awygle>
The answers already there are right - loss, dispersion, impedance control
<awygle>
Pretty sure what they're saying about the distance making it irrelevant isn't true for analog though
<pie_>
scratching mz heda at this, is it the metal lines that i thought were some kind of shielding that everzone is talking aboot_
<pie_>
_
* pie_
fixes kb layout
<pie_>
* ?
<qu1j0t3>
pie_: solder mask
<pie_>
well yeah but i mean where is the diff pair on this
<qu1j0t3>
o
<Ultrasauce>
"well it worked great in the FEM..."
<Ultrasauce>
wonder how a fingerprint affects performance
<qu1j0t3>
not good. scope people talk about oil contaminants a lot.
<qu1j0t3>
IPA baths
gnufan has joined ##openfpga
<awygle>
Flux is the worst. Nothing worse than a control loop not controlling for no discernable reason, then you wash the "no clean" flux out from under everything and it magically works again
<awygle>
pie_: yes the things that look like shielding. Shielding doesn't usually meander, that's a good clue
m_t has joined ##openfpga
<awygle>
Not sure if I would have run those lines parallel to (underneath?) the heat sink like that, speaking of impedance control
<awygle>
How would you approach automatically determining a part's orientation? Like if you have a socket that allows a chip to go in rotated 180 degrees?
<Ultrasauce>
automatically how? from what information?
<awygle>
basically imagine you have an FPGA or a microcontroller hooked up to the socket, and you want to detect whether the chip is in backwards. if not, you talk to the chip (over SPI or something) and if yes you alert the user
<awygle>
you control the board and the software, but you can't like, slap a camera on it
<qu1j0t3>
integration tests
<sorear>
if Vcc draws a near-short-circuit current, the part was probably backwared
<sorear>
[test may not apply in all situations]
m_w has quit [Ping timeout: 268 seconds]
digshadow has quit [Ping timeout: 240 seconds]
nrossi has quit [Quit: Connection closed for inactivity]
<Ultrasauce>
heh CV was definitely my first thought
<azonenberg>
Yes, CV is the way to go realistically
<azonenberg>
Bonus points if you can watch the part go in
<azonenberg>
most parts have readily identifiable markings on the underside
<azonenberg>
(BGAs at least)
<azonenberg>
for PnPs to use
<sorear>
or…key the socket?
m_w has joined ##openfpga
<Ultrasauce>
yeah that is the REAL real solution
<azonenberg>
That doesnt work for most ICs though
<azonenberg>
it isnt practical to key a dip socket or something
<azonenberg>
Better option is to trust your user to not be an idiot :p
<azonenberg>
and maybe add an overcurrent shutdown or something
<azonenberg>
Actually if you want to be nice and low current what you can do is find two pins that are both supposed to be on the same power rail
<azonenberg>
(assuming a larger IC with >1 power pin)
<Ultrasauce>
yeah now distinguish between charging the decoupling caps and the ic frying itself
<azonenberg>
measure resistance between them with a low (single digit mA) current
<azonenberg>
If it's good then apply power (and use a low-side fet to ground that last ground pin)
<azonenberg>
if bad, keep it off
<awygle>
azonenberg: yeah that seems to be approx. the answer i was looking for
<awygle>
on lots of ICs you could probably hold VCC and GND low, then pull an I/O pin to ~0.7V at low current and see if you find a clamping diode
ym has quit [Quit: Leaving]
<qu1j0t3>
is this for mass production? cuz maybe the way the math goes is that it's cheaper to do a full power test and throw away failures than it is to rework failures?
<rqou>
not the same thing, but digshadow was working on a chip inter-pin impedance characterizing thingy for a) identifying unmarked chips and b) testing *cough* *cough* "rebonded" ics to see if they were rebonded properly
<awygle>
qu1j0t3: i work for a company that makes pre-programming systems for mass manufacturing
digshadow has quit [Ping timeout: 252 seconds]
* qu1j0t3
nods
m_t has quit [Quit: Leaving]
<cyrozap>
pointfree: "Anyone here have experience & thoughts on using inkjet printers to prototype ... antenna designs?"
<pointfree>
cyrozap: It seems people are indeed using inkjet printers for antenna prototypes
<cyrozap>
pointfree: Efficient antennas are already difficult to build well using highly-controlled processes, so trying to design one that will work well using conductive fluid is far more trouble than it's worth, especially if it's just for a prototype of something that will be put on a real PCB.
<cyrozap>
pointfree: If your goal is flexible IoT stuff, you're better off using copper-on-polymide/"flex PCBs" to do it.
<cyrozap>
pointfree: If you just need a quick-and-dirty antenna to test something, cut a copper wire to a quarter of the wavelength and that'll probably work better than any antenna made out of ink :P
<cyrozap>
pointfree: Oh, the paper says they printed a 915 MHz RFID antenna. That's a little different--I thought you were interested in something like Bluetooth/WiFi and other stuff with high data rates.
inode has joined ##openfpga
<cyrozap>
pointfree: Regardless, you can't really re-use antenna designs between mediums, since the antenna properties are directly tied to its physical dimensions and material properties.