DocScrutinizer05 changed the topic of #neo900 to: http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900
`John has quit [Ping timeout: 246 seconds]
cybiko1231 has quit [Quit: Leaving.]
modem has joined #neo900
modem has quit [Ping timeout: 260 seconds]
modem has joined #neo900
fling has joined #neo900
Humpelstilzchen has quit [Ping timeout: 250 seconds]
Defiant has joined #neo900
modem has quit [Quit: Quitte]
<R0b0t1> wat toolin
<DocScrutinizer05> eagle, scripts for BOM, stuff like that
<DocScrutinizer05> multiple PCBs in one project
sparetire_ has joined #neo900
cybiko123 has joined #neo900
cybiko123 has quit [Changing host]
cybiko123 has joined #neo900
<DocScrutinizer05> wpwrak: http://www.silego.com/
<DocScrutinizer05> ballpark figure: 0.50 @ 250 customer "programmed"
<DocScrutinizer05> MOQ: 10
<DocScrutinizer05> quiescent VDD: 0.5µA
<DocScrutinizer05> some come with a 1A FET
<DocScrutinizer05> heck, who needs a display LED driver?
<DocScrutinizer05> ;-)
<wpwrak> *hmm*
<wpwrak> OTP isn't so nice, though
<wpwrak> ah, not OTP-only, though
<DocScrutinizer05> aiui you can load config to ram, and when you think it's ok you fuse it
<wpwrak> yup. just ran the video. there, they say you can just load a config into volatile storage
<DocScrutinizer05> aren't they lovely lil bugs?
<wpwrak> let's see how good the documentation is ...
<DocScrutinizer05> looks decent
<DocScrutinizer05> on a first cursory glance
<DocScrutinizer05> 80 pages
<wpwrak> reg <xxx:yyy> looks encouraging, yes
<wpwrak> i wonder if they also document the programming. we'll see. at 50% atm
<DocScrutinizer05> yep, I think they do
<wpwrak> no programming in the DS, it seems
<DocScrutinizer05> prolly in the devkit docs, or a dedicated paper
<DocScrutinizer05> >>Their datasheets even fully document the bitstream the chips use for programming; this chip is just dying for someone to write a VHDL or Verilog compiler for it<<
<wpwrak> indeed :)
<wpwrak> nicely detailed errata. you can tell they come from the engineering department, not legal :)
<DocScrutinizer05> :-D
<wpwrak> devel sw also available for linux. presumably closed, but it's at least a good sign
<DocScrutinizer05> a company that builds chips and sells them MOQ:10 is driven by the engineers
<DocScrutinizer05> those guys must love their product
<DocScrutinizer05> and heck, why not? those *are* lovely chips
<DocScrutinizer05> and marketed in a great way
<DocScrutinizer05> devboard 50 bucks!
<DocScrutinizer05> or was it 60?
<DocScrutinizer05> ZIF even
<wpwrak> small MOQ isn't uncommon for new products
<wpwrak> alas, no programming info to see. they have a high programming voltage. not sure if that's for OTP only or also for volatile programming
<wpwrak> let's try the power of google ...
<wpwrak> hmm. a search for SRDWB (programming signal with a distinctive name) and silego only finds data sheets :-(
<wpwrak> they've been around for a while. here's an article from 2011: http://www.eetimes.com/document.asp?doc_id=1316797
<DocScrutinizer05> yeah, they don't look like a startup to me
<wpwrak> can't find anything on the programming protocol
<DocScrutinizer05> me neither. But they *must* have documented it somewhere, no?
<wpwrak> well, could be secret or under NDA
<DocScrutinizer05> I highly doubt that
<wpwrak> having to ask for documentation is usually a bad sign
<DocScrutinizer05> I wonder where's their designer software
<wpwrak> i.e., it's unlikely that they just forgot to release it
<DocScrutinizer05> http://www.silego.com/softdoc/software.html here the sw
<wpwrak> "AN-1028 Single Wire Interface/GPIO Expander" ;-)
<DocScrutinizer05> HEHE
<DocScrutinizer05> well, it's a different SWI protocol
<wpwrak> yea, a slightly odd one. not the worst idea, though, for a small range of values
<DocScrutinizer05> they prolly could have done smarter, with same chip, by discerning between long and short pulses
* DocScrutinizer05 wonders if the programming specs are included in the software package download you have to register to get it
<DocScrutinizer05> heck, that other guy must have seen them somewhere or he wouldn't say "Their datasheets even fully document the bitstream the chips use for programming"
<wpwrak> the bitstream is the res <xxx,yyy> stuff
<DocScrutinizer05> ?
<wpwrak> look at the DS. the register settings are the bitstream
<wpwrak> i.e., there is one very large "register"
<DocScrutinizer05> could you share a page number?
<DocScrutinizer05> aaah
<DocScrutinizer05> found it
<DocScrutinizer05> anyway p.23 is it
<DocScrutinizer05> 8.0 Connection Matrix
<DocScrutinizer05> SLG46110
<wpwrak> it's on a lot of other places, too :)
<wpwrak> starting with page 16, i think
<DocScrutinizer05> yes, what's lacking is the actual programming signal definition
<wpwrak> yup
<DocScrutinizer05> or I didn't find it yet
<wpwrak> i looked at all the likely places, including app notes - nothing
<DocScrutinizer05> yeah, I completely scrutinized the SLG46110 DS Nr 000-0046110-100 and there's zilch info about programming in it
<DocScrutinizer05> mailto: info@silego.com
<DocScrutinizer05> LOL! " 5/26/2016 1.0 Production Release"
<DocScrutinizer05> " 5/21/2015 0.66 Updated ACMP Diagrams and added Timing Characteristics Diagrams"
<DocScrutinizer05> they actually might have gone 'public' only a 2 months ago
<DocScrutinizer05> so quite possibly they just haven't made it yet to release the programming specs
<DocScrutinizer05> they have nice FETs (switches) too: up to 9A, 7.3 mR
<DocScrutinizer05> 1x3x0.55mm
infobot has quit [Read error: Connection reset by peer]
rjeffries has quit [Ping timeout: 252 seconds]
cybiko123 has quit [Ping timeout: 246 seconds]
silviof has quit [Quit: WeeChat 1.2]
Pali has joined #neo900
vakkov has quit [Ping timeout: 250 seconds]
paulk-aldrin has joined #neo900
xes_ has joined #neo900
xes has quit [Ping timeout: 246 seconds]
vakkov has joined #neo900
<R0b0t1> those are neat
mvaenskae has quit [Ping timeout: 244 seconds]
mvaenskae has joined #neo900
`John has joined #neo900
illwieckz has joined #neo900
xes_ has quit [Quit: bye]
`John has quit [Ping timeout: 246 seconds]
silviof has joined #neo900
louisdk has joined #neo900
louisdk has quit [Remote host closed the connection]
louisdk has joined #neo900
illwieckz has quit [Quit: Ça va couper chérie…]
_whitelogger has quit [Ping timeout: 240 seconds]
_whitelogger has joined #neo900
rjeffries has joined #neo900
cybiko123 has joined #neo900
cybiko123 has quit [Changing host]
cybiko123 has joined #neo900
cybiko123 has quit [Ping timeout: 265 seconds]
cybiko123 has joined #neo900
cybiko123 has quit [Changing host]
cybiko123 has joined #neo900
lobito has quit [Quit: Leaving.]
rjeffries has quit [Remote host closed the connection]
louisdk has quit [Ping timeout: 244 seconds]
louisdk has joined #neo900
sparetire_ has quit [Quit: sparetire_]
DocScrutinizer51 has quit [*.net *.split]
sixwheeledbeast has quit [*.net *.split]
sixwheeledbeast has joined #neo900
DocScrutinizer51 has joined #neo900
freemangordon has joined #neo900
ravelo has joined #neo900
xes has joined #neo900
Pali has quit [Remote host closed the connection]
`John has joined #neo900
che1 has joined #neo900
modem has joined #neo900
jonsger has joined #neo900
paulk-aldrin has quit [Quit: Quitte]
xes has quit [Quit: bye]
che1 has quit [Ping timeout: 272 seconds]
ravelo has quit [Ping timeout: 246 seconds]
xes has joined #neo900
illwieckz has joined #neo900
cybiko123 has quit [Quit: Leaving.]
Oksana has joined #neo900
jonsger has quit [Quit: jonsger]
louisdk has quit [Ping timeout: 264 seconds]
illwieckz has quit [Ping timeout: 260 seconds]