2014-07-27 00:23 pcercuei has quit [Quit: leaving]
2014-07-27 00:30 rz2k has joined #qi-hardware
2014-07-27 00:38 Textmode has joined #qi-hardware
2014-07-27 01:59 zcrc has quit [Quit: dodo]
2014-07-27 04:25 rz2k has quit [Read error: Connection reset by peer]
2014-07-27 04:29 pabs3 has quit [Ping timeout: 240 seconds]
2014-07-27 04:43 pabs3 has joined #qi-hardware
2014-07-27 05:05 jekhor has joined #qi-hardware
2014-07-27 06:24 qi-bot has quit [Ping timeout: 240 seconds]
2014-07-27 06:25 qi-bot has joined #qi-hardware
2014-07-27 06:40 qi-bot has quit [Ping timeout: 256 seconds]
2014-07-27 06:43 qi-bot has joined #qi-hardware
2014-07-27 06:46 wolfspraul has joined #qi-hardware
2014-07-27 07:00 qi-bot has quit [Ping timeout: 260 seconds]
2014-07-27 07:26 rz2k has joined #qi-hardware
2014-07-27 08:00 Textmode has quit [Quit: "It was one dev, naked in a room with a carton of cigarettes, a thermos full of coffee and bourbon, and all his summoned angels."]
2014-07-27 08:26 jekhor has quit [Ping timeout: 245 seconds]
2014-07-27 09:49 jekhor has joined #qi-hardware
2014-07-27 10:25 pcercueiS2 has joined #qi-hardware
2014-07-27 10:28 pcercueiS2 has joined #qi-hardware
2014-07-27 10:41 jekhor has quit [Ping timeout: 250 seconds]
2014-07-27 12:36 pcercueiS2 has quit [Remote host closed the connection]
2014-07-27 13:17 zcrcS2 has joined #qi-hardware
2014-07-27 14:02 rz2k has quit [Read error: Connection reset by peer]
2014-07-27 14:16 zcrcS2 has quit [Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org]
2014-07-27 14:51 jekhor has joined #qi-hardware
2014-07-27 16:07 jekhor has quit [Read error: Connection reset by peer]
2014-07-27 16:07 jekhor has joined #qi-hardware
2014-07-27 16:21 jekhor has quit [Ping timeout: 272 seconds]
2014-07-27 18:36 pcercuei has joined #qi-hardware
2014-07-27 18:44 jekhor has joined #qi-hardware
2014-07-27 19:14 qi-bot has joined #qi-hardware
2014-07-27 19:27 qi-bot has quit [Ping timeout: 255 seconds]
2014-07-27 19:31 wolfspraul has quit [Ping timeout: 250 seconds]
2014-07-27 19:33 wolfspraul has joined #qi-hardware
2014-07-27 19:36 qi-bot has joined #qi-hardware
2014-07-27 19:48 wolfspraul has quit [Quit: leaving]
2014-07-27 19:50 qi-bot has quit [Ping timeout: 264 seconds]
2014-07-27 19:58 qi-bot has joined #qi-hardware
2014-07-27 19:58 woakas1 has joined #qi-hardware
2014-07-27 19:58 mth_ has joined #qi-hardware
2014-07-27 19:59 pabspabspabs has joined #qi-hardware
2014-07-27 20:01 whitequa1k has joined #qi-hardware
2014-07-27 20:03 kanzure_ has joined #qi-hardware
2014-07-27 20:11 pabs3 has quit [*.net *.split]
2014-07-27 20:11 whitequark has quit [*.net *.split]
2014-07-27 20:11 kanzure has quit [*.net *.split]
2014-07-27 20:11 mth has quit [*.net *.split]
2014-07-27 20:11 woakas has quit [*.net *.split]
2014-07-27 20:11 qi-bot has quit [Ping timeout: 260 seconds]
2014-07-27 20:12 qi-bot has joined #qi-hardware
2014-07-27 20:25 qi-bot has quit [Read error: No route to host]
2014-07-27 20:35 qi-bot has joined #qi-hardware
2014-07-27 20:48 qi-bot7 has joined #qi-hardware
2014-07-27 20:48 qi-bot has quit [Read error: Connection reset by peer]
2014-07-27 20:49 qi-bot has joined #qi-hardware
2014-07-27 20:49 qi-bot7 has quit [Read error: Connection reset by peer]
2014-07-27 20:59 whitequa1k is now known as whitequark
2014-07-27 21:02 qi-bot has quit [Read error: Connection reset by peer]
2014-07-27 21:02 qi-bot has joined #qi-hardware
2014-07-27 21:20 qi-bot has quit [Ping timeout: 240 seconds]
2014-07-27 22:06 jekhor has quit [Ping timeout: 240 seconds]
2014-07-27 22:23 mth_ is now known as mth
2014-07-27 22:40 kanzure_ is now known as kanzure
2014-07-27 23:24 <nicksydney> DocScrutinizer05: http://faif.us/cast/2014/jul/18/0x49/
2014-07-27 23:24 <nicksydney> [Get cast in Ogg/Vorbis format] [Get cast in MP3 format] 0x49: Why Free Software Phone Doesn't Exist
2014-07-27 23:29 <DocScrutinizer05> so?
2014-07-27 23:30 <DocScrutinizer05> I doubt I will learn anything new (which I also would be willing to believe) from such a talk
2014-07-27 23:31 <DocScrutinizer05> I've been *inside* business of development modem firmware, I think I know why there never will be a Free Software Phone
2014-07-27 23:32 <DocScrutinizer05> nobody can pay for, nor assure integrity of the mandatory certifications
2014-07-27 23:33 <wpwrak> time for the roguephone ;-)
2014-07-27 23:33 <whitequark> time to kill cellular as a technology
2014-07-27 23:34 <DocScrutinizer05> when a company like ST-E employs 1200 engineers for 24 months to develop a LTE firmware, why would they want to put it into public domain?
2014-07-27 23:34 <whitequark> every time you tell that story, the amount of engineers and months grows :D
2014-07-27 23:35 <wpwrak> maye we should talk to the fine folks at ISIS, or make friends in north korea. they may be less reluctant to ignore western restrictions :)
2014-07-27 23:35 <DocScrutinizer05> depends what you count in
2014-07-27 23:36 <DocScrutinizer05> wpwrak: sure, and they have an abundance of highly qualified software engineers
2014-07-27 23:37 <wpwrak> consider it a job opportunity ;-)
2014-07-27 23:39 <wpwrak> man ! that kinetis oscillator sucks !
2014-07-27 23:40 <DocScrutinizer05> where will they build the 60nm chip fab?
2014-07-27 23:40 <wpwrak> they will _occupy_ it ;-)
2014-07-27 23:41 <DocScrutinizer05> yeah, and then cut into little pieces and ship from Dresden to North Iraq, eh?
2014-07-27 23:42 <wpwrak> how to crash a KL26, method #651: OSC0_CR |= whatever; // change some harmless-looking field in that oscillator control register. this will read a "1" from some "unused" fields. that same "unused" fields really hates it when a "1" is written to it ...
2014-07-27 23:42 <DocScrutinizer05> ooooold
2014-07-27 23:43 <whitequark> uhhh, never touch "unused" fields
2014-07-27 23:43 <wpwrak> or at least i suppose there's a "1" somewhere in there. 'cause the whole critter goes south if i use |=. it's happy enough to accept everything i send it if i use =
2014-07-27 23:43 <whitequark> microcontrollers 101
2014-07-27 23:43 <DocScrutinizer05> man i2ctools
2014-07-27 23:43 <wpwrak> whitequark: tjey'
2014-07-27 23:43 <wpwrak> lert's try this again
2014-07-27 23:44 <wpwrak> they're supposed to read back a "0" ...
2014-07-27 23:44 <DocScrutinizer05> never do bit operation directly on control registers
2014-07-27 23:45 <whitequark> you can do that on some architectures
2014-07-27 23:45 <whitequark> e.g. STM32 specifically supports it, and most cortex SoCs do
2014-07-27 23:45 <DocScrutinizer05> depends on your ALU and how it works
2014-07-27 23:45 <whitequark> it's more due to the way register responds to writes
2014-07-27 23:46 <whitequark> especially flags that get reset on writes
2014-07-27 23:46 <DocScrutinizer05> well, kinda, but also how CPU does a read-modify-write
2014-07-27 23:47 <whitequark> yeah, there's some wankery with byte- and word-sized reads and writes
2014-07-27 23:47 <whitequark> and peripherals that react to reads/writes directly
2014-07-27 23:47 <whitequark> and the way your bus divides/groups requests
2014-07-27 23:47 <DocScrutinizer05> yep
2014-07-27 23:47 <wpwrak> i do it with perfect impunity on any other register so far ...
2014-07-27 23:47 <whitequark> anyway, cortex-m socs are explicitly designed to be completely compatible with C
2014-07-27 23:47 <whitequark> you can even do interrupt handlers without a line of assembly
2014-07-27 23:48 <wpwrak> yup, and this is an M0+
2014-07-27 23:48 <whitequark> because its interrupt controller knows C ABI
2014-07-27 23:48 <whitequark> (it's also faster because of that, as it can switch to an interrupt of higher priority without repushing registers)
2014-07-27 23:48 <whitequark> (if it arrives while pushing them)
2014-07-27 23:48 <wpwrak> well, in a bit, i'll make my code return that register value. then i'll know for sure what's cooking there.
2014-07-27 23:48 <wpwrak> for now, all i gave is a lone LED :)
2014-07-27 23:49 <wpwrak> s/gave/have/
2014-07-27 23:49 <whitequark> hook a scope there
2014-07-27 23:49 <whitequark> then shift it out
2014-07-27 23:52 <wpwrak> also found that my rfkill switch kills a bit more than just RF - i flipped VRF and VSYS and didn't notice. so it either connects VRF to VSYS (rf enabled, all is well), or VSYS to GND (system not happy)
2014-07-27 23:53 <wpwrak> ah well, that's why we have sharp knives and those yellow wires ...
2014-07-27 23:54 <wpwrak> mean while, i'm learning the dark secrets of the FLL. seems that it runs a tad too fast ...
2014-07-27 23:54 <whitequark> fll?
2014-07-27 23:54 <whitequark> frequency-locked loop?
2014-07-27 23:55 <wpwrak> yup
2014-07-27 23:55 <wpwrak> the chip has PLL and FLL .. and some tricky rules when to use which
2014-07-27 23:58 <wpwrak> the whole clocking system is actually a mess. it consists of no less than five subsystems with documentation on a module basis. so the word "external" can have a great many meanings.
2014-07-27 23:58 <wpwrak> and you have a while army of clock gates and clock mode bits
2014-07-27 23:58 <wpwrak> and of course no overview diagram that would give you the whole picture. just one that at least tells you where some of the muxers are lurking.
2014-07-27 23:59 <wpwrak> just enough information that you can eventually figure things out within a small number of days of trial and error ...