2012-01-28 00:03 and yeah, schedule does not seem to be called ever 2012-01-28 00:07 I wish openocd supported single stepping... 2012-01-28 00:10 * DocScrutinizer would toss a Lauterbach over to lindi, if it wasn't such an incredibly expensive and closed and dongled tool that lindi-_ wouldn't like it anyway 2012-01-28 00:14 it's really convenient to click the "load" button which implicitly resets the attached DUT, and a few moments later you see the first opcode of ROM-BL highlighted in the listing window, and a "stopped" in the status line 2012-01-28 00:16 even more convenient is to set a breakpoint to the interesting line of your patched code, and when it stops again, click on the two parameters to strcmp() to find you passed a pointer to "LLDEBUG" while the compared item in the list is "LLDebug" 2012-01-28 00:17 probably saved me like 2h of code analysis today 2012-01-28 00:18 now you could say "duh, use printf() - just does the same for you" - ust LLDebug was the name of the UART where printf() prints to ;-D 2012-01-28 00:19 so you could say I patched printf(), and it'S not a nice idea to use printf(9 inside printf() to debug it 2012-01-28 00:22 btw Lauterbach trace32 software can do this on ARM core SoC via JTAG 2012-01-28 00:24 so if it wasn't for the dongle, you probably wouldn't even need the Lauterbach hardware 2012-01-28 00:24 seems it is never exiting the interrupt handler 2012-01-28 00:25 only thing that doesn't work when you use JTAG only is the 512MB backtrace buffer in Lauterbach hw, that allows you to run the code "backwards" 2012-01-28 00:26 at least that's not possible in realtime via JTAG ;-D 2012-01-28 00:28 yeah nice non-free tools indeed :/ 2012-01-28 00:28 I thought you'd appreciate to hear what's possible via JTAG if only the free tools were smart enough 2012-01-28 00:28 now I'd like to know how the cpu gets to execute instruction at 0xc02975a4 2012-01-28 00:29 it's not executing the instruction before that so something is branching there 2012-01-28 00:29 hehe 2012-01-28 00:29 but according to source there isn't any kind of loop :/ 2012-01-28 00:30 a clear case for backtrace buffer 2012-01-28 00:30 or auto-singlestepped mode 2012-01-28 00:31 though *terribly* slow, it should be able to create a backtrace as well 2012-01-28 00:33 hmm, single stepping seems to work after some openocd magic :/ 2012-01-28 00:36 DocScrutinizer: gdb has some support for reversible debugging, doesn't it? 2012-01-28 00:36 should 2012-01-28 00:36 I admit I'm not a gdb wizard 2012-01-28 00:37 I'll just try it for my arm now 2012-01-28 00:37 ... only to find out that I do not have it atm. 2012-01-28 00:39 DocScrutinizer: actually, if your arch has a proper gdbserver, then you have half of those features for certain, and maybe have reversible debugging, if it's actually working. so things are not that bad 2012-01-28 00:40 I never said things were bad 2012-01-28 00:40 ok, then I misunderstood you 2012-01-28 00:41 just debugging kernel on arm seems wasn't possible a year ago, since no free (or no at all) version of kdbg available for that 2012-01-28 00:42 lindi-_ is debugging suspend/resume issues on GTA02, not exactly gdb's primary domain 2012-01-28 00:47 wej [wej!~j@m2.mullvad.net] has joined #qi-hardware 2012-01-28 00:48 and I think I should get a beer now at my pub, so I'll see sth else than LCD screens all day and all night 2012-01-28 00:48 :-D 2012-01-28 00:49 you could try to find a CRT for home use :) 2012-01-28 00:52 maybe I could invent some goggles/glasses that are made of some special material energized by washing with liquid air from Himalaya, to remove that nasty mind corrupting vibrations from that light that goes thru the liquid crystal. Might be a commercial success story on next esoteric convention 2012-01-28 00:53 sounds like a plan 2012-01-28 01:15 re 2012-01-28 01:25 MEH 2012-01-28 01:25 that was a quick beer 2012-01-28 01:26 no, that was the slowest waitress I've ever seen, paired with amnesia and a bunch of drunken assholes 2012-01-28 01:26 I probably would die from thirst in there 2012-01-28 01:26 ;-) 2012-01-28 01:27 the reward for trying to do weird things which are not related to looking at LCD 2012-01-28 01:29 poetic justice, swiftly served by the agent on duty, disguised as a waitress 2012-01-28 01:30 indeed 2012-01-28 01:33 don't forget her troops! a really nice bunch of weird drunken people, one sitting left to me and arguing with the one right to me, face to face. Probably the waitress didn'T even dare to bring a beer for me, no way to place it anywhere 2012-01-28 01:34 * DocScrutinizer gors washing his face 2012-01-28 01:36 you could have asked one of them to swap places with you :) 2012-01-28 03:45 heberth [heberth!~heberth@190.97.216.164] has joined #qi-hardware 2012-01-28 04:38 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware 2012-01-28 05:02 qwebirc93098 [qwebirc93098!4766dbba@gateway/web/freenode/ip.71.102.219.186] has joined #qi-hardware 2012-01-28 05:05 whitequark Jean Claude Whippler of JeeLabs does a lot of home automation stuff, all very open. AVRs are ok/fine for the individual sensor nodes, need something beefier for central coordinator. He alswo recently worked through a design to steal a small amount of energy form 230V mains. is not selling due to liability. 2012-01-28 05:07 He uses the HopeRF RFM12B radio. cheap, and it works. I think that's also the device ?? mirko ?? uses for his project 2012-01-28 07:27 jekhor [jekhor!~jek@leased-line-46-53-195-130.telecom.by] has joined #qi-hardware 2012-01-28 08:57 DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware 2012-01-28 09:32 B_Lizzard [B_Lizzard!~havoc@athedsl-428276.home.otenet.gr] has joined #qi-hardware 2012-01-28 09:58 Ayla [Ayla!~paul@254.135.123.78.rev.sfr.net] has joined #qi-hardware 2012-01-28 10:00 antoniodariush [antoniodariush!~antonio@host-92-2-65-80.as43234.net] has joined #qi-hardware 2012-01-28 10:32 B_Lizzard [B_Lizzard!~havoc@athedsl-428276.home.otenet.gr] has joined #qi-hardware 2012-01-28 10:38 antoniodariush [antoniodariush!~antonio@host-92-2-65-80.as43234.net] has joined #qi-hardware 2012-01-28 11:05 blackrose1231 [blackrose1231!~blackrose@2401:8000:0:1::2ef] has joined #qi-hardware 2012-01-28 11:26 kudkudyak [kudkudyak!~sun@94.72.140.37] has joined #qi-hardware 2012-01-28 11:38 [commit] Maarten ter Huurne: MIPS: A320: Fine-tune PWM backlight settings. (jz-3.2) http://qi-hw.com/p/qi-kernel/0bc374e 2012-01-28 11:45 [commit] Paul Cercueil: MIPS: JZ4740: enable the OpenDingux logo only when targetting the Dingoo. (jz-3.2) http://qi-hw.com/p/qi-kernel/2688101 2012-01-28 11:45 [commit] Paul Cercueil: MIPS: A320: Updated defconfig to match Kconfig changes. (jz-3.2) http://qi-hw.com/p/qi-kernel/9c420ed 2012-01-28 11:45 [commit] Paul Cercueil: MIPS: A320: defconfig: Tweak scheduling options to get better performance. (jz-3.2) http://qi-hw.com/p/qi-kernel/d9e5b2b 2012-01-28 11:59 blackrose1231 [blackrose1231!~blackrose@27.225.223.72] has joined #qi-hardware 2012-01-28 12:07 [commit] Paul Cercueil: OpenDingux: initrd: added 'splashkill' program. (jz-3.2) http://qi-hw.com/p/qi-kernel/c9b9fe0 2012-01-28 12:14 kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #qi-hardware 2012-01-28 12:52 wolfspra1l: hmm, this could be an interesting product for qi-hw. should have a nice margin when produced in china. (page in german) http://www.bpes.de/de/boxentransformer.html 2012-01-28 13:13 jluis [jluis!~jluis@2001:5c0:1400:a::515] has joined #qi-hardware 2012-01-28 13:49 wolfspraul [wolfspraul!~wolfsprau@p5B0AA963.dip.t-dialin.net] has joined #qi-hardware 2012-01-28 13:50 lol 2012-01-28 13:59 wpwrak: thanks for the link! the text sounds a little esoteric at first read, but I'll read again 2012-01-28 13:59 I am in no way worried about finding product opportunities 2012-01-28 14:00 (esoteric) i think it's highly concentrated snake oil :) 2012-01-28 14:00 and I also don't think there will be anything specific about any country in the manufacturing process 2012-01-28 14:00 no second read needed? 2012-01-28 14:00 but you can't beat the margin on a few pieces of what looks like plastic sold for EUR 2100 :) 2012-01-28 14:01 2nd read only for entertainment value 2012-01-28 14:01 oh that doesn't surprise me. I can't put a percentage figure but A LOT of businesses only survive because at some underlying point, they have these kinds of margins 2012-01-28 14:01 my gut feeling says 50% of businesses at least :-) 2012-01-28 14:02 you can also look at their product catalog. they also have some energy varnish for violins and such :) 2012-01-28 14:02 ok then no 2nd read, I thought it's something serious 2012-01-28 14:02 there's a lot of innovation in speakers indeed, that's why I even read it in the first place 2012-01-28 14:02 because I have come across a lot of initially exotic sounding speaker stuff lately 2012-01-28 14:02 ah ! sorry :) speakers sounded like just credible enough at first to make it more funny 2012-01-28 14:03 jluis [jluis!~jluis@2001:5c0:1400:a::515] has joined #qi-hardware 2012-01-28 14:03 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware 2012-01-28 14:03 maybe I become to open-minded towards 'creative' people nowadays 2012-01-28 14:04 about margins, I went through a number of computer/electronics retailers in Germany in recent weeks, and wow, they are changing a lot 2012-01-28 14:04 yeah, though these show more the kind of creativity that gets you executed in china ;-) 2012-01-28 14:04 all I see are piles of very high-margin accessories 2012-01-28 14:04 interesting 2012-01-28 14:04 it's like people are stuck with their computers, and try to keep them alive 2012-01-28 14:04 all the rest is mail order ? 2012-01-28 14:05 so they sell all these crufty little things, extensions, expansions, cables, etc. 2012-01-28 14:05 the computers are also there, but they are clearly loss leaders 2012-01-28 14:06 the store makes money with accessories, when people come back because something doesn't work :-) 2012-01-28 14:07 yeah, cables have traditionally had interesting pricing 2012-01-28 14:10 did you have any luck pimping M1 to shops ? (if you got to doing that ... you were once talking about it) 2012-01-28 14:10 mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware 2012-01-28 14:10 they shuold like it better now that is has midi. more accessories to sell ;-)) 2012-01-28 14:11 (accessories) maybe we could offer a special usb-midi cable :) 2012-01-28 14:12 (i.e., USB A for the M1, USB mini B for the MIDI device. perhaps USD 50. after all, it is something a little exclusive that's hard to find elsewhere) 2012-01-28 14:15 ... wait what 2012-01-28 14:16 * whitequark had to read it three times before he finally understood 2012-01-28 14:16 important properties could include: 1) low transmission delay (< 10 ns); 2) ultra-low delay variation; 3) electromagnetic shielding 2012-01-28 14:17 4) asbestos-free 2012-01-28 14:17 (http://xkcd.com/641/) 2012-01-28 14:17 oh right, GREEN !! :) 2012-01-28 14:18 you need to add nanotechnologies somewhere 2012-01-28 14:18 maybe it could come in a sealed bag, sterilized 2012-01-28 14:18 no pitching yet, for that I have to travel around to visit music/dj shops 2012-01-28 14:18 everything is better (from the "get money from govt" point of view) with some nanotechnologies 2012-01-28 14:19 wolfspraul: train network down ? :) 2012-01-28 14:22 EEEW 2012-01-28 14:22 * DocScrutinizer puts on his frozen-air activated rock-crystal goggles before continuing to read http://www.bpes.de/de/boxentransformer.html on his evil LCD screen 2012-01-28 14:23 for the archive records: that link is a hoax 2012-01-28 14:36 i still kinda like the usb-midi cable idea, though. you could probably make good money with this. and you wouldn't even have to lie :) 2012-01-28 14:37 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 14:37 as in "tell a lie". lies of omission are a different topic 2012-01-28 14:39 what cable? size-A to mini-B is the most common type 2012-01-28 14:40 faderfox comes with a cable, I forgot whether one was included in the icreativ 2012-01-28 14:41 I will focus on the product, accessories are a distraction now. 2012-01-28 14:41 iCreativ comes with A to mini-B. so does the nanoKONTROL2 (and probably a ton of midi for iGadget devices) 2012-01-28 14:41 first step is to finish the remote kbd idea, that's really nice 2012-01-28 14:42 and why would that not work with the M1? 2012-01-28 14:42 the connector on M1 is the same as the most common connector on notebooks 2012-01-28 14:43 mini-b into icreativ, the other size into m1 2012-01-28 14:44 no no ... i'm not saying that any random usb cable wouldn't work. that would be a lie. but one could still offer a usb-midi cable, no ? 2012-01-28 14:44 like you can get some fancy ethernet cables for audio 2012-01-28 14:45 of course, that would be preying on the technically weak, who may be led to think (once you tell them that such a product exists) that you actually NEED a special usb-midi cable for usb-midi. 2012-01-28 14:46 or maybe they're just not sure and prefer to err on the safe side. 2012-01-28 14:53 it won't sell 2012-01-28 14:53 I think you underestimate the amount of work needed to actually sell such cables 2012-01-28 14:54 let's make a strong core product first, then accessories 2012-01-28 14:54 and btw, the #1 best accessory for the Ben NanoNote already exists - jane's pouches 2012-01-28 14:55 wpwrak: do you know of a cable which has usb-midi on one end (host) and midi on the other? 2012-01-28 14:55 to use usb-midi devices with stuff that likes real midi 2012-01-28 14:55 we've only found the other way round 2012-01-28 14:56 hehe... i know the other way round exists ;) 2012-01-28 14:56 to connect old-style MIDI devices to a notebook, that exists for 5 USD or so 2012-01-28 14:56 we have not found what you mean 2012-01-28 14:56 i was just thinking if i could trigger wpwrak into hacking mode to brew something up *ducks* 2012-01-28 14:56 you can use a pc ;-) 2012-01-28 14:57 wouldnt that be a job for your 8051? 2012-01-28 14:57 with a pc, it works great. plug in all the usb-midi you want, add a usb-to-midi dongle, connect them all together with qjackctl 2012-01-28 14:59 (my 8051) it doesn't do usb host :) 2012-01-28 14:59 about the led mails... it was so much that I was overwhelmed in replying 2012-01-28 14:59 ;-)) 2012-01-28 14:59 I think all is good now - design verified 2012-01-28 14:59 when Adam is back we can proceed to actual schematic entry? 2012-01-28 14:59 the only question was the size of grid? 2012-01-28 15:00 I have no overview over free pins and routing 2012-01-28 15:00 otherwise you can just pick what you like 2012-01-28 15:00 if we do well, I can imagine other uses for the led array later 2012-01-28 15:00 yeah. the only things missing are 1) see if there is led vs. ir interference. but i'm sufficiently unworried about that that i think i'll postpone such testing until a day i feel really totally and utterly bored :) 2012-01-28 15:00 yes 2012-01-28 15:00 not needed 2012-01-28 15:01 worst case that led has to stay off, so what 2012-01-28 15:01 2) pick a location of the leds in the matrix. i'd leave that to adam / the layout guys. 2012-01-28 15:01 :-) 2012-01-28 15:01 yes 2012-01-28 15:02 3) size of matrix, yes. that can simply be use 3+3 pins, reserve one more 2012-01-28 15:02 let's have one asking size 2012-01-28 15:02 otherwise we just spread uncertainty to more people 2012-01-28 15:03 4) picking pins would also be adam / layout guys. we can adapt to anything they pick within ~30 minutes, 25 of which are the xilinx tools doing their thing 2012-01-28 15:03 that asking size can come with a note *) can be smaller if needed 2012-01-28 15:03 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 15:04 for the size, i'd go with 3 x 4. it's not an excessive number of pins and it allows for up to 24 leds. depending on how you populate the matrix, only a 2x4 or 3x3 area of it would be used, i.e., one pin could be unconnected 2012-01-28 15:05 (there would be no physical matrix anyway. just an equivalent topology) 2012-01-28 15:06 5) decide on the exact layout rules for the leds. such as leaving an area for translucency, distance from connector edge, distance from board edge, any exceptions to the rules, etc. 2012-01-28 15:08 (ir led) yes, that worst case gives me great comfort :) 2012-01-28 15:12 don't make 5) too complicated 2012-01-28 15:12 but yes, sure. I saw your drawing :-) 2012-01-28 15:15 it's one more thing for adam to decide :) 2012-01-28 15:17 ok, so 3*4 is the preferred one 2012-01-28 15:21 great, seems led is exhaustively covered 2012-01-28 15:21 if we are fiddling with layout, a wish I want to add is to move the memcard or jtag-serial so that the memcard can be fully opened 2012-01-28 15:21 just move it a bit, no big change 2012-01-28 15:22 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 15:22 also the jtag-serial has one corner cut out slightly, I am wondering whether that is still needed (there was a 2nd batch of jtag-serial board with minor improvements) 2012-01-28 15:22 3*4 also happens to be the maximum size we can support with 6 mA per LED :) anything larger would get a bit more demanding (well, a little. we could go to vast quantities of LEDs without working up a sweat, if we really must :) 2012-01-28 15:22 if it's still there, that's another thing we can fix 2012-01-28 15:22 yeah, saw the corner. very cute ;-) 2012-01-28 15:23 why is this an issue ? 2012-01-28 15:23 finally the jtag-serial coult be 1mm or so further away from the acrylic, that would make inserting the cable a tad easier 2012-01-28 15:23 not an issue, just a small annoyance 2012-01-28 15:23 i would make a hole in the acrylic and make both the cable and its insertion even easier ;-)) 2012-01-28 15:23 that's another idea 2012-01-28 15:24 "live hinge" anyone ? :) 2012-01-28 15:24 so I just want to move jtag-serial and memcard a little (1-2mm) to solve those 3 issues 2012-01-28 15:24 memcard open, 1mm more clearance to wall, no need for cut corner 2012-01-28 15:24 sure we can make bigger changes, but that's a separate idea then 2012-01-28 15:24 I like having the jtag-serial separate now, it's good 2012-01-28 15:25 again, why is the cut corner an issue ? once you know you need it, it should be trivial to have 2012-01-28 15:25 even though for the foreseeable future all boards will have it inside by default 2012-01-28 15:25 it's a detail that needs to be remembered, and really just a leftover from lack of mechanical overview early on 2012-01-28 15:25 if you want new jtag boards you make backward-compatible, you need to keep the corner anyway 2012-01-28 15:26 it may actually already be fixed in the 2nd-gen jtag-serial, I don't know 2012-01-28 15:26 no need because all m1 have one already and I have plenty in stock 2012-01-28 15:26 I just want to cleanup the board a little, that's al 2012-01-28 15:26 I'm talking about 1-2mm moves 2012-01-28 15:26 my M1r4 has an "RC2" jtab board. that has (and needs) the corner 2012-01-28 15:26 if it's easy, layout should just do it 2012-01-28 15:27 we already have two versions of jtag boards 2012-01-28 15:27 and plenty in stock 2012-01-28 15:27 the point is to cleanup the files going forward 2012-01-28 15:27 has to start at some point... 2012-01-28 15:27 same for memcard blockage 2012-01-28 15:28 this looks alike a case of fighting yesterday's battles :) 2012-01-28 15:28 if those little things won't get done, no big deal either 2012-01-28 15:28 the memcard i get 2012-01-28 15:28 the jtag has already sailed 2012-01-28 15:28 if you move it and anyone makes cards that don't have the corner cut out, they won't work in rc2/rc3 boards 2012-01-28 15:28 I would move the headers on m1 a little so that the board doesn't need the cut corner 2012-01-28 15:29 doesn't matter, since all rc2/rc3 boards have jtag-serial already 2012-01-28 15:29 if you keep on cutting out the corner forever anyway, why bother moving ? :) 2012-01-28 15:29 that's what I want to cleanup, the cut corner need 2012-01-28 15:29 gee, small detail :-) 2012-01-28 15:29 the jtag board could need replacing due to loss, defect (real or imagined) 2012-01-28 15:29 it should take layout less time to move this by 1mm than our discussion here :-) 2012-01-28 15:29 I have plenty in stock 2012-01-28 15:30 and I don't even plan another run without cutting the corner 2012-01-28 15:30 you're trying to solve a problem you've already solved :) 2012-01-28 15:30 but I want to move the headers by 1mm :-) 2012-01-28 15:30 so you don't make the same argument when we are at R5 2012-01-28 15:30 if routing says it's easy, i will ask them to move 2012-01-28 15:30 also memcard opening 2012-01-28 15:30 and also 1mm extra clearance towards wall 2012-01-28 15:31 a bigger thing would be whether to move the memcard to the side 2012-01-28 15:31 I was worried you bring that up :-) 2012-01-28 15:31 but I think we should not do that now 2012-01-28 15:31 well, probably no harm in it. just totally pointless :) 2012-01-28 15:31 not in R4 2012-01-28 15:31 kinda like the endless renames in kicad ;-)) 2012-01-28 15:32 you agree about the memcard? 2012-01-28 15:32 that's highest value of those 3 2012-01-28 15:32 second is 1mm extra clearance to wall 2012-01-28 15:32 the memcard is a disaster. i don't think you can make it worse ;-) 2012-01-28 15:32 third is remove need to cut corner 2012-01-28 15:32 I think we agree actually, on everything. *if* they are moving the jtag-serial headers already, they can also consider that corner thing. 2012-01-28 15:32 so any change to the memcard is good :) 2012-01-28 15:32 because you bet that was not intentional... 2012-01-28 15:33 it has very small practical value now, only cleanup 2012-01-28 15:33 but that most minor thing is what we discuss about 2012-01-28 15:33 if routing says it's difficult in that area, or the power stuff is too close, or whatever, then I wouldn't touch any of this 2012-01-28 15:33 I think the entire current situation is not bad, including memcard 2012-01-28 15:33 I see the memcard as some sort of internal storage 2012-01-28 15:34 and I ship all products with 2gb formatted and installed there 2012-01-28 15:34 while changes to jtag don't seem to do more than change for the sake of changing. kinda like when you go to the supermarket and find your favourite butter with a slightly different logo and somewhere in the corner they printed "NEW LOGO !" 2012-01-28 15:34 (i'm not kidding. i actually saw something like this. though it wasn't butter) 2012-01-28 15:34 the corner cut was not intentional 2012-01-28 15:35 just believe me 2012-01-28 15:35 anyway this is indeed the most minor of those 3 small mechanical annoyances 2012-01-28 15:35 oh, i get that :) just, now that it's there and done, it has no further cost 2012-01-28 15:36 the pcb-cutting cnc machine won't mind that little turn :) 2012-01-28 15:36 and you have no problem discussing whitespace in sources... 2012-01-28 15:36 :-) 2012-01-28 15:36 wpwrak: how do you think, how long will it take to make M1 Rlast? and how long will it be until it will be obsolete? 2012-01-28 15:36 Rlast ? 2012-01-28 15:36 ah, final :) 2012-01-28 15:36 don't understand your question 2012-01-28 15:36 R1, R2, ..., R5, Release. 2012-01-28 15:36 yeah, final revision 2012-01-28 15:37 the more it sells, the more revisions 2012-01-28 15:37 ah, so that M1 revision isn't like release candidate. my bad. 2012-01-28 15:37 even after a Milkymist Two or some other product that replaces M1 comes out, there may still be new M1 revisions 2012-01-28 15:37 it's like cars. you make a new model every year. you stop the line only when it stops selling. 2012-01-28 15:37 whitequark: yes, but you noticed an important detail :-) 2012-01-28 15:37 the 'candidate' was indeed confusing 2012-01-28 15:38 we realized that recently 2012-01-28 15:38 so we stopped saying RC1, RC2, RC3 2012-01-28 15:38 and instead now it's just revision, or R4 2012-01-28 15:38 have we actually announced the name change on the list ? i'd still consider that our "official" channel 2012-01-28 15:38 I'd personally suggest V4, or V1.4 2012-01-28 15:38 like router vendors do 2012-01-28 15:38 that's way less confusing 2012-01-28 15:39 well, we've just settled on R4 2012-01-28 15:39 but maybe V5 in honor of whitequark ? :-) 2012-01-28 15:39 then W6 in honor of Werner 2012-01-28 15:39 how about that? 2012-01-28 15:39 it was M1rc3 (confusing). wolfgang suggested M1r4, which is better. i think i kinda like the idea of a M1.4. been thinking about that for a while, too. 2012-01-28 15:39 each time i type "M1r4", it feels a little wrong 2012-01-28 15:40 oh god, version number discussion 2012-01-28 15:40 I am relaxed about this 2012-01-28 15:40 if it makes werner happy, I am also ok with M1.4 2012-01-28 15:40 the main thing on the sales side is product literature, manual etc. 2012-01-28 15:40 yeah, M1.4 is fine too 2012-01-28 15:40 and they all talk about 'milkymist one' only anyway 2012-01-28 15:40 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 15:40 the rest is 'internal' (open for Qi of course), so we can communicate about improvements 2012-01-28 15:41 so as long as the numbers make sense, including the old ones, I don't care which words or characters there are 2012-01-28 15:41 meaning that... M1R4 can also be M1.4 2012-01-28 15:41 we have another thing, just "Milkymist". that would be the whole category. e.g., i could imagine an M2 with a >= 7" panel 2012-01-28 15:42 that's another discussion 2012-01-28 15:42 the Milkymist brand is confusing, overloaded a bit 2012-01-28 15:42 :) 2012-01-28 15:42 but I wouldn't change that right now, the brand needs more visibility first 2012-01-28 15:42 so I tend to say Milkymist SoC or Milkymist One 2012-01-28 15:42 or sometimes I just say Milkymist when talking to new people, since I mainly want to catch their attention 2012-01-28 15:43 wpwrak: btw, about the 1.4 thing 2012-01-28 15:43 the current silkscreen says Milkymist One RC3 2012-01-28 15:43 datecodes are great to have 2012-01-28 15:43 oh definitely 2012-01-28 15:43 so you suggest Milkymist One M1.4 ? 2012-01-28 15:43 you want to repeat the "M1"? 2012-01-28 15:44 hmm, dunno 2012-01-28 15:44 "Milkymist One V1.4 " ? 2012-01-28 15:44 with R4 the flow is better Milkymist One R4 2012-01-28 15:44 or V4 2012-01-28 15:44 since we are deep in opinion land, I think V is geeky and cheap 2012-01-28 15:45 yes, for the long form, R4 looks nicer 2012-01-28 15:45 I believe if it's R, the product will take off! :-) 2012-01-28 15:45 heh 2012-01-28 15:45 there's a story why the founder of Roland chose that name 2012-01-28 15:46 one reason supposedly was that there were very few/no other companies starting with 'R', and that would give Roland a very visible spot in alphabetical listings at tradeshows and exhibitions 2012-01-28 15:46 that's the legend... 2012-01-28 15:46 :-) 2012-01-28 15:46 (roland) before, they called themselves "Eyjafjallaj 2012-01-28 15:47 heh :) 2012-01-28 15:47 I continue with "R4" unless some other active contributor insists on something else 2012-01-28 15:47 I never type M1R4 anyway 2012-01-28 15:47 there's also the eternal battle for having the most "A" at the beginning of the name 2012-01-28 15:47 because the context is clear 2012-01-28 15:47 yeah but that's cheap 2012-01-28 15:47 very :) 2012-01-28 15:47 but I can see the point of being the only one under 'R' 2012-01-28 15:47 if the story is true 2012-01-28 15:47 so about R4 - leds are settled 2012-01-28 15:48 exhaustively 2012-01-28 15:48 ;-) 2012-01-28 15:48 wpwrak: infinite thanks, really! 2012-01-28 15:48 I hope this turns into a multi-billion dollar LED spinoff, one day 2012-01-28 15:48 er, what? 2012-01-28 15:48 (M1R4) you should type M1r4 anyway ;-) 2012-01-28 15:48 can I see the history of led thing? 2012-01-28 15:48 it's mostly in #milkymist and the milkymist devel list 2012-01-28 15:48 whitequark: are you on the #milkymist list ? 2012-01-28 15:48 wpwrak: nope 2012-01-28 15:48 bah 2012-01-28 15:48 just have a bit here today so the Qi crowd doesn't feel excluded 2012-01-28 15:48 milkymist list, without # 2012-01-28 15:49 most likely there would have been more feedback on the Qi list... 2012-01-28 15:49 so leds are settled 2012-01-28 15:49 mostly 2012-01-28 15:49 I will add my wish item of moving the jtag-serial header slightly to address the issues above - if easy 2012-01-28 15:50 whitequark: for some visual impressions and random stuff: http://downloads.qi-hardware.com/people/werner/m1/leds/ 2012-01-28 15:50 then we have the expansion system 2012-01-28 15:50 whitequark: to make sense of it, you'll have to read the list, though :) 2012-01-28 15:51 (qi crowd excluded) boosting the traffic for the monthly statistics ? :) 2012-01-28 15:51 nah 2012-01-28 15:51 yup. still needs more specs. but ... the part adam needs should be pretty much covered 2012-01-28 15:51 quality stuff will find its way 2012-01-28 15:51 you mean the leds? 2012-01-28 15:51 the expansion header 2012-01-28 15:52 or header(s) 2012-01-28 15:52 oh, we settled on the pins for the second header? 2012-01-28 15:52 i'm fine with the pins adam uses 2012-01-28 15:52 there are two clock pins too (i think), so in case we need any of these, we'll have them 2012-01-28 15:53 nobody mentioned any other special pin features to take into account, so maybe there are none we should care about 2012-01-28 15:54 the ones we do take into account are: voltage (all 3.3 V), differential pairs, and having > 1 clock pins 2012-01-28 15:54 (up from 0 clock pins in M1rc3 :) 2012-01-28 15:55 what i'm not so happy about is that J21 is upside down. but that's too late to fix. 2012-01-28 15:55 and we should probably keep J22 like this too, for consistency 2012-01-28 15:55 better consistently bad than inconsistent :) 2012-01-28 15:56 upside down? 2012-01-28 15:56 >1 you mean >=2 ? 2012-01-28 15:57 people don't mention special pins because almost nobody is using the header now 2012-01-28 15:57 chicken & egg problem, like so many on m1 2012-01-28 15:57 but I agree, the above looks right 2012-01-28 15:57 we do factor in what we've learnt from kpaul and others - clock & differential pairs 2012-01-28 15:58 and if more people learn more things, we will factor them in in the future... 2012-01-28 15:58 ha ha, I like how you reply to the html mail in this ugly way 2012-01-28 15:58 span span span span 2012-01-28 15:59 div div div 2012-01-28 15:59 yes 2012-01-28 15:59 span span 2012-01-28 15:59 div div div 2012-01-28 15:59 :-) 2012-01-28 15:59 (the "yes" was my actual message) 2012-01-28 15:59 knowing you I'm pretty sure you did this on purpose :-) 2012-01-28 16:01 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 16:01 (special pins) well, also people who know that there special pins can mention them. they don't have to actually use them. but since nobody said anything, i suppose it's fine. else, we'll eventually find out ;-) 2012-01-28 16:01 yes, fully agree 2012-01-28 16:01 speed 2012-01-28 16:01 R4 looks like a huge step up from R3 2012-01-28 16:02 (html mail) obviously ;-) 2012-01-28 16:04 (j21 upside down) in the schematics, it's shown with ground at the bottom, which is a common configuration (of the connector i mean, not just of the presentation) 2012-01-28 16:05 in the board, you notice that the ground pins are towards the center of the main pcb. if you work on such a board, you'll probably consider the edge of the M1 as your "bottom". thus, the connector will appear reversed. 2012-01-28 16:05 hmm 2012-01-28 16:05 ok 2012-01-28 16:05 why not rotate the header? 2012-01-28 16:06 we can ease the pain by rotating it in the schematics or in the supporting documentation 2012-01-28 16:06 or on the board 2012-01-28 16:06 if you rotate now, it'll be incompatible with rc2/rc3 2012-01-28 16:06 show the layout folks some respect 2012-01-28 16:06 wouldn't it just be upside down? 2012-01-28 16:07 and plus, we are going from male to female anyway 2012-01-28 16:07 without having found an easy-to-point-to adapter cable or piece yet 2012-01-28 16:08 well, ledm would still fit, even if rotated. not as elegantly, but yes. so 100% of my existing boards would be compatible ;-) 2012-01-28 16:08 (adapter) just take a header 2012-01-28 16:09 jluis_ [jluis_!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 16:10 the typical header has ~5 mm mating pin on the top and ~2.5 mm pin for soldering at the bottom. those 2.5 mm are just enough to mate with a female socket. it won't be great mechanically, but you get a contact 2012-01-28 16:10 of course, this gives you a bit of a stack 2012-01-28 16:11 but if you rotate your board, it would fit even on rc2/3, no? 2012-01-28 16:11 I think we can go for reversal of the physical header, no problem 2012-01-28 16:12 ledm can be rotated, yes. it'll sit on the dvi connector, but that's okay. there's nothing on the bottom 2012-01-28 16:12 ok, so let's rotate the header? 2012-01-28 16:12 of course, future boards may be more difficult 2012-01-28 16:13 if we do it, it's now or never :) 2012-01-28 16:13 not really because we already know that most and I have no problem at all offering ugprade options to the few that are not, if this should ever become an issue 2012-01-28 16:14 Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware 2012-01-28 16:14 I think any argument for not rotating the header is quite hypothetical 2012-01-28 16:14 with so many changes we are making already 2012-01-28 16:14 (future boards) i was thinking of making some experimental board and being able to try it out on an rc3. as the rc3 ages, it also becomes attractive for more risky experiments ;-) 2012-01-28 16:14 sure but that is still possible, even with rotation, no? 2012-01-28 16:15 if that makes you feel uneasy or slow down, then let's not rotate 2012-01-28 16:15 let's float the idea on #milkymist or the list ? 2012-01-28 16:15 you can but there will be 0 responses 2012-01-28 16:15 (possible) yes, but you may have to design specifically for rc3 2012-01-28 16:15 we can also leave the header unrotated 2012-01-28 16:15 I can see arguments either way 2012-01-28 16:16 but as you said, no more changes after R4 2012-01-28 16:16 otherwise we really completely screw up any expansion idea 2012-01-28 16:17 yeah :) 2012-01-28 16:17 so maybe no rotate? 2012-01-28 16:17 your pick 2012-01-28 16:18 you are *by far* the one who gave the expansion system the most thought and practical usage 2012-01-28 16:18 and yes, if we leave J21 the way it is now, then j22 should be the same and we update schematics and documentation 2012-01-28 16:19 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 16:21 no rotating on the pcb is the safer choice. sometimes, cowardice is the better part of valor ;-) but we can still float it on the list 2012-01-28 16:21 it's also more democratic ;-) 2012-01-28 16:22 sure, fine by me. do I understand this right: if list is silent we leave as-is, and update documentation? 2012-01-28 16:25 ok :) 2012-01-28 16:25 valhalla [valhalla!~valhalla@81-174-22-194.dynamic.ngi.it] has joined #qi-hardware 2012-01-28 16:28 emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware 2012-01-28 16:36 cool, so that was all for R4? 2012-01-28 16:37 how about connecting 5V on J21 via a header ? 2012-01-28 16:37 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 16:37 with jumper 2012-01-28 16:38 i.e., a cheap "switch" 2012-01-28 16:38 don't understand. you mean a switch between 3.3V and 5V? 2012-01-28 16:39 no, 3V3 would always be there. but we'd get the ability to disable 5V. 2012-01-28 16:40 some pins are 5V? wait, checking 2012-01-28 16:41 ah yes, 1 and 2 2012-01-28 16:41 I have no idea. You hear people saying they want 5V, others are saying they want lower voltages, even below 3.3V 2012-01-28 16:42 the default is to leave the jumper open? 2012-01-28 16:42 so 5V only after closing the jumper? 2012-01-28 16:43 yes 2012-01-28 16:43 moo wolfspraul wpwrak 2012-01-28 16:43 i'm writing a mail with the rationale ... 2012-01-28 16:43 hi there :-) 2012-01-28 16:43 gotta boost the list traffic stats ;-) 2012-01-28 16:43 hmm, what's the sound bats make ? chirp ? :) 2012-01-28 16:43 what you're messing up right here? ;-D 2012-01-28 16:44 wpwrak: depends on converter, here they ROAR 2012-01-28 16:45 (messing) keeping 5V away from the FPGA's 3.3V domain :) 2012-01-28 16:45 sounds like a good idea :-D 2012-01-28 16:45 (roar) naw, our bats are small 2012-01-28 16:45 you mean if someone shorts 1 and 3, the fpga and board are toast? 2012-01-28 16:46 that could happen, too 2012-01-28 16:46 or bring 5V to one of the I/O pins 2012-01-28 16:46 how about bringing out lower voltages like 1.8, 1.2 ? 2012-01-28 16:47 not sure what happens if you short the 5V and 3V3 rails. maybe that's actually survivable because everything is then at a higher level 2012-01-28 16:47 :-) 2012-01-28 16:47 I somehow doubt that, but ok 2012-01-28 16:47 not for long 2012-01-28 16:47 i wouldn't bother with that 2012-01-28 16:47 well I have nothing against a jumper (default off) to disable 5V 2012-01-28 16:47 of course it's more work 2012-01-28 16:47 perhaps we can have some use for the rc2 wolfgang is replacing with newer boards ;-) 2012-01-28 16:47 if you're concerned, you usually use crowbar circuits 2012-01-28 16:48 and fuses 2012-01-28 16:48 DocScrutinizer: are you on the milkymist mailing list ? 2012-01-28 16:48 what's the proposed pin structure for J22 ? 2012-01-28 16:48 another 2 gnd, 2 3V3, 2 5V ? 2012-01-28 16:48 nope, and I'm happy with it 2012-01-28 16:48 (j22) 2 x GND, 2 x 3V3, the rest i/o 2012-01-28 16:48 I got just a few lists with several 1000 unread mails already 2012-01-28 16:48 ;) 2012-01-28 16:49 Qi is far bigger than Milkymist and has a more diverse set of people on the list 2012-01-28 16:49 well, you know the schematics. the issue in question is the to of the expansion header J21 (page 3) 2012-01-28 16:49 linkie to schem pdf pls 2012-01-28 16:49 there we have the 5 V rail, right next to it the 3.3 V rail, and then a lot of 3.3 V FPGA I/Os 2012-01-28 16:49 bookmark this :) http://milkymist.org/mmone/rc3_schematics.pdf 2012-01-28 16:50 meh maybe I got it somewhare under my 587 bookmarks already ;-) 2012-01-28 16:50 * DocScrutinizer missing a search in bookmarks, heard FF got sth like that 2012-01-28 16:53 yeah, bookmarks are not all that useful :) 2012-01-28 16:53 J21 has no 5V? 2012-01-28 16:53 i have a little HTML page i keep on editing. would actually be easy to turn this into a smarter bookmark page. 2012-01-28 16:53 pins 1 and 2 2012-01-28 16:53 ooh it has 2012-01-28 16:54 prety please consider changing VDD symbols from upside-down GND symbol to a circle symbol! 2012-01-28 16:55 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 16:56 * DocScrutinizer notices the "GND" symbols are actually PE symbols there 2012-01-28 16:56 wrong tree ;-) 2012-01-28 16:56 the plan is to migrate the schematics to kicad anyway. soon. like next week. 2012-01-28 16:57 on that occasion, a number of perversions can die :) 2012-01-28 16:57 I'd happily help killing them :-D 2012-01-28 16:57 next week? 2012-01-28 16:58 excellent. we have our first volunteer ! :) 2012-01-28 16:58 too soon ? basically once adam has processed the backlog 2012-01-28 16:58 I just siign the execution orders though :-) 2012-01-28 16:58 oh sure 2012-01-28 16:58 you;ll make a fine military governor ;-) 2012-01-28 16:59 :-P 2012-01-28 16:59 but yes, perhaps next week is to ambitious. there is a bit of a pile awaiting him already :) 2012-01-28 17:00 I already got upset about illegible GTA04 schematics, and about goldelico not even offering a way I might edit this mess 2012-01-28 17:00 they got no GND symbols at all, rather wire up GND like any other trace 2012-01-28 17:01 excellent ! ;-) 2012-01-28 17:01 confuses the living hell out of me 2012-01-28 17:01 learn from the rookiest of rookies ;-) 2012-01-28 17:01 DocScrutinizer: you want to help with the kicad schematics? 2012-01-28 17:02 I'll pray 5 times a day towards any direction of the sky you are telling me to :-) 2012-01-28 17:03 wolfspraul: I'd maybe take some fun in doing so, alas I am afraid kicad is no fun to work with, esp on a laptop with ~300MB free space (actually less than the 5% reserved for root-only) 2012-01-28 17:05 my installed size is 102 MB 2012-01-28 17:05 new laptop is on my ToBuy list for next week 2012-01-28 17:05 kicad isn't commercial bloatware ;-) 2012-01-28 17:05 (J21) so what's wrong with it? 2012-01-28 17:06 for sure my choice to place the GND, 5V, 3V3 would have been slightly different 2012-01-28 17:06 the risk of accidently bringing those 5V somewhere they shouldn't go 2012-01-28 17:07 e.g., short to the neighbouring 3V3. or to any of the 3.3 V I/Os 2012-01-28 17:07 valhalla [valhalla!~valhalla@81-174-22-229.dynamic.ngi.it] has joined #qi-hardware 2012-01-28 17:07 just described it here: http://lists.milkymist.org/pipermail/devel-milkymist.org/2012-January/002655.html 2012-01-28 17:08 the latter seems unlikely to happen, the first I'd tackle by placing GND *between* 5V and 3V3 2012-01-28 17:08 it's not just shorts by metal objects, but could be traces on the board 2012-01-28 17:09 this is for experimental boards. so they can have errors. or they could also simply be mis-inserted. 2012-01-28 17:09 shorts on traces caused by faulty PCB can never be handled in any sane way by design 2012-01-28 17:09 correct. that's why i'm suggesting to keep 5 V away if we don't need it 2012-01-28 17:10 for mis-inserting plugs, you usually cut one pin and plug one "hole" 2012-01-28 17:10 i'm not worried about shorting anything there to GND or to 3V3. that's survivable, often indefinitely. 2012-01-28 17:10 that assumes you use proper connectors :) 2012-01-28 17:11 also a common best practice is to place GND pins so the plug's short between all the GND contacts would short VDD to GND when plug inserted wrong way round (180° rotated) 2012-01-28 17:12 for DIY/prototypes, improvisation is quite likely, so i wouldn't count on people to have the "right" connectors 2012-01-28 17:12 for that you can't count on anything, so as well just forget about the whole issue 2012-01-28 17:13 apart from separating 5V from 3V3 by one positions so shorting the pins by metal opbjects gets unlikely 2012-01-28 17:13 yes, short-on-rotation is good. seems to be a bit tricky here, though. or not ? 2012-01-28 17:14 5V, GND, 3V3, IO [...] 2012-01-28 17:14 (tricky) not that much if you'd use 4 GND and only one for 5V and for 3V3if 2012-01-28 17:15 er, where from is that trailing "if"? 2012-01-28 17:15 o.O 2012-01-28 17:16 DocScrutinizer: sorry what? why is it a best practice to short VDD to GND? 2012-01-28 17:16 read context 2012-01-28 17:16 we'd rather not reassign pins. since that would break compatibility with rc2 and rc3 boards already in the field 2012-01-28 17:16 :nod: 2012-01-28 17:16 whitequark: if you short the rails, the short-circuit protection of the regulator will kick in and you just power down 2012-01-28 17:16 get a crowbar on 3V3 2012-01-28 17:17 how to do this without reassigning pins ? :) 2012-01-28 17:17 wpwrak: ah ok, that's how it should work theoretically then 2012-01-28 17:17 whitequark: got some cases where it didn't ? ;-) 2012-01-28 17:17 so same short-circuit shutdown would kick in when shorting 5V to 3V3 2012-01-28 17:17 olimex did it with their jtag. plug the connector wrong way and their LDO explodes 2012-01-28 17:17 almost literally 2012-01-28 17:18 wpwrak: electronic crowbar circuit on 3V3 rail 2012-01-28 17:18 OVP 2012-01-28 17:18 designed according to military standards, including the self-destruct :) 2012-01-28 17:19 (crowbar) but that still wouldn't help with 5V reaching the I/Os 2012-01-28 17:20 don't you like the simplicity of being able to just disable 5V with a jumper ? 2012-01-28 17:20 wpwrak: it might, when IO got proper clamp diodes to 3V3 2012-01-28 17:20 it's the clamp diodes i'm worried about :) 2012-01-28 17:20 tiny little clamp diodes 2012-01-28 17:20 yeah sure 2012-01-28 17:21 they should survive a surge to charge up 3V3 buffer C to the point where crowbar kicks in and ters down both 3V3 *and* 5V *directly* 2012-01-28 17:22 tears* 2012-01-28 17:22 sounds like a major redesign of the power supply circuit 2012-01-28 17:22 nope 2012-01-28 17:23 just add a synced crowbar circuit on both 5V and 3V3 rail 2012-01-28 17:23 crowbar .... "No records match your search criteria" says digi-key :-( 2012-01-28 17:23 meh 2012-01-28 17:24 no crowbar chips out there 2012-01-28 17:24 thyristor, Zener, R 2012-01-28 17:25 http://www.elektronik-kompendium.de/public/schaerer/crowbar.htm 2012-01-28 17:25 actually 2012-01-28 17:25 thyristor, Zener, 2 R, C 2012-01-28 17:26 urandom__ [urandom__!~user@p548A5A42.dip.t-dialin.net] has joined #qi-hardware 2012-01-28 17:27 hmm, the 2nd circuit looks scary. the 1st isn't so bad. but i notice that it works with 12 V. that may explain some of the simplicity. 2012-01-28 17:27 you'd need some sync as well to trigger 5V crowbar when 3V3 engages 2012-01-28 17:27 phew. does sound major. 2012-01-28 17:28 c'mon 2012-01-28 17:28 good EE isn't for free on BOM 2012-01-28 17:28 i'm more worried about EE-time :) 2012-01-28 17:28 and design risk 2012-01-28 17:28 better get some positions in BOM for *that* rather than for useless inductors etc 2012-01-28 17:29 but for an imperfect solution, a jumper on 5 V doesn't sound so bad, does it ? 2012-01-28 17:29 design risk? 2012-01-28 17:29 yeah, these inductors where evil ;-) 2012-01-28 17:29 risk of a fuckup. wouldn't be the first :) 2012-01-28 17:29 you can remove the whole circuit without any impact on normal operation, so what's the "risk"? 2012-01-28 17:30 rework :) 2012-01-28 17:30 just make whole block "NC" and risk killed ;-P 2012-01-28 17:30 wpwrak: what's with those inductors? 2012-01-28 17:31 naw, while i think the whole power supply circuit needs some overhaul, r4 may not be a good moment for it 2012-01-28 17:31 we don't want to delay that thing forever. and opinions on the importance of the expansion header are already divided 2012-01-28 17:32 so making this the source for another week of discussion and experiment wouldn't be popular 2012-01-28 17:32 a "meh" for me. You asked me, I give a proposal. Up to you to deal with orga crap 2012-01-28 17:32 hence my proposal for a jumper :) 2012-01-28 17:32 jumper for sure can't hurt 2012-01-28 17:33 OVP crowbar idea duly noted :) that's a good item to have on the requirements for the future proper power supply circuit. ideally already as part of the chip. but we'll see. 2012-01-28 17:34 whitequark: some ground planes are connected with inductors. e.g., the audio section with the main part of the circuit. 2012-01-28 17:34 or, rather, were :) 2012-01-28 17:35 now these inductors have yielded to a significant amount of tin 2012-01-28 17:35 kewl, already two votes for the jumper ;) 2012-01-28 17:36 wpwrak: hm. I heard some guidelines recommend that. What was wrong with them? 2012-01-28 17:36 DocScrutinizer: and you agree that 5 V reaching the 3.3 V rail or the I/O pins in the 3.3 V domain is generally bad news. i.e., it's not just some theoretical risk i'm imagining 2012-01-28 17:38 whitequark: i'm glad you asked :-) connect audio equipment. a little voltage surge goes through ground (they're at different "floating" potentials). the inductor won't let the surge through. so it goes through the audio codec in one way or another. 2012-01-28 17:39 sounds like fubar 2012-01-28 17:39 whitequark: audio codec hates that and crashes. luckily, it takes no permanent damage. system clock happens to be provided by audio codec. thus whole systems hangs. VJ is not happy ;-) 2012-01-28 17:40 >no permanent damage 2012-01-28 17:40 I guess it depends on the surge energy... 2012-01-28 17:40 yeah, i was lucky :) 2012-01-28 17:41 i would have kinda hated to burn my brand new M1 already on the first day 2012-01-28 17:41 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 17:41 wpwrak: yes, I agree on 5V is a bad thing on 3V3 domain, and should never happen 2012-01-28 17:42 kewl, thanks ! 2012-01-28 17:42 and risk to get shorts on expansion cables would cause exactly that to happen when 5V are on a connector that has lots of 3V3 stuff is not negligible 2012-01-28 17:43 aye 2012-01-28 17:44 ideally your 3V3 IO is protected against such incidents, but yes... I know 2012-01-28 17:48 DocScrutinizer: I heard of a cheap way to do overvoltage protection. Basically, to protect a 3.3V max input you place a 3.3V (or slightly bigger to account for imprecision) zener on it. Zeners always fail short, and when it fails short, your power supply protection kicks in. Afterwards, you replace failed zeners. 2012-01-28 17:48 Does that work? 2012-01-28 17:59 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 18:05 usually yes 2012-01-28 18:06 so the end result is we do the jumper, and we leave it open by default (but jumper seated there) 2012-01-28 18:06 but Zener are no ideal perfect components, so you might see overvoltage nevertheless 2012-01-28 18:07 DocScrutinizer: thanks 2012-01-28 18:07 wolfspraul: perfect 2012-01-28 18:11 yeah well, work work work. but what wouldn't we do for THE FUTURE 2012-01-28 18:11 it's probably the easiest of all the changes in r4 ;-)) 2012-01-28 18:13 let's see 2012-01-28 18:13 :-) 2012-01-28 18:16 the reluctance to do changes on new hw rev basically defeats the whole purpose of getting a new hw rev at all 2012-01-28 18:18 this old OM notion of "well, this maybe is a bug, but until now it didn't cause major issues so let's keep it this way it's now, rather than introducing new untested stuff into next hw rev" somehow always bewildered me 2012-01-28 18:19 not at all. it's a question of what gets improvements to people as efficiently as possible 2012-01-28 18:19 nobody benefits if we have the perfect design but it takes us ten years to finish it 2012-01-28 18:20 it's a question of self esteem and professional experience whether you think you could fix a bug, or are incompetent to a degree where your fix would rather make things worse than better 2012-01-28 18:20 oh, i'm confident we can do anything :) 2012-01-28 18:21 given enough time and money :) 2012-01-28 18:21 workload for *implementing* an existing improvement mustn't be a major concern, otherwise you again picked the wrong profession 2012-01-28 18:21 see, there is only a finite number of M1rc3. and they're selling. when wolfgang runs out of them, would it be better to sell M1r4 with some improvements or make more M1rc3 without any of them ? 2012-01-28 18:23 depends on the workload vs benefit from a new revision, Often it's better to produce some more of the old rev, and get a real improved version later on 2012-01-28 18:23 a major fail in procedures at OM 2012-01-28 18:23 well, rc3 had a number of nightmarish issues :) 2012-01-28 18:24 here, i prefer the "release often" approach over the "it's done when it's done" approach. making hardware is slow enough as it is. 2012-01-28 18:25 haha, it only gets much slower by this release often approach 2012-01-28 18:25 correct. but you're making progress. 2012-01-28 18:25 it's not like software where you simply hit a button to release 2012-01-28 18:26 this misconception was another reason why OM hw release policy and procedures been so therribly fsckdup 2012-01-28 18:26 also, in case you really mess up, you have a previous version to fall back to that's reasonably close, not something already completely prehistoric 2012-01-28 18:27 OM also suffered from the "this is our last chance to do it" syndrome 2012-01-28 18:27 which is somehow identical 2012-01-28 18:27 if you just accept that there will be, say, two hw revisions per year, you can be a lot more relaxed 2012-01-28 18:28 if it doesn't make it this time, you'll only have to wait a few moremonths 2012-01-28 18:28 at OM Sean more thought of two *products* per year 2012-01-28 18:28 not like several years. or until your next life :) 2012-01-28 18:29 let's just say that he had a great many ideas ;-) 2012-01-28 18:36 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 19:06 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 19:48 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 20:07 jekhor [jekhor!~jek@leased-line-46-53-195-130.telecom.by] has joined #qi-hardware 2012-01-28 20:12 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 20:25 wow your voting works better than I thought 2012-01-28 20:26 mehr Demokratie wagen :-) 2012-01-28 20:27 ? 2012-01-28 20:28 there's been any votes lately? 2012-01-28 20:41 and unanimously ! ;-) 2012-01-28 20:50 that was about whether we should rotate J21 or not 2012-01-28 20:51 a minor issue and I suggested Werner just decides what he likes better, but Werner wanted to ask the list (where I thought nobody would care) 2012-01-28 20:51 and I was wrong, already 3 answers by now, all favoring to keep the layout as-is and fix the schematics/docs 2012-01-28 20:54 in general, the simpler the issue, the more people will offer their opinion :) 2012-01-28 20:54 * mstevens attempts to reflash a long neglected nanonote 2012-01-28 20:55 * lindi-_ still struggles with suspend bug :/ 2012-01-28 20:56 currently it seems that an irq occurs even though it has been masked and __irq_svc does not cope with the unexpected situation and instead loop forever and never returns from the interrupt handler 2012-01-28 20:59 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 21:30 ooh you guys improved things so much since last time I flashed 2012-01-28 21:56 mstevens: thanks! :-) 2012-01-28 21:56 and I think we got 10% of what the Ben could do out of it 2012-01-28 21:56 that bugs me, but well, just steady improvement is fine 2012-01-28 21:57 the Ben could be a really great notebook companion, on a day when lugging around the big thing is a bad idea 2012-01-28 21:57 wolfspraul: there are like actual applications now 2012-01-28 21:59 :-) 2012-01-28 22:06 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 22:22 dvdk [dvdk!~dvdkhlng@g225041073.adsl.alicedsl.de] has joined #qi-hardware 2012-01-28 22:25 paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware 2012-01-28 22:58 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 23:24 Ayla [Ayla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware 2012-01-28 23:26 GNUtoo [GNUtoo!~gnutoo@host29-81-dynamic.48-82-r.retail.telecomitalia.it] has joined #qi-hardware 2012-01-28 23:26 hi kristianpaul 2012-01-28 23:27 did you already heard of MEIF? 2012-01-28 23:27 GNUtoo: hey there 2012-01-28 23:27 nope 2012-01-28 23:27 basically it's a GPS protocol present on some phones 2012-01-28 23:27 the CPU has to compute the fix 2012-01-28 23:28 some people are interested about reversing it 2012-01-28 23:28 like the new main replicant developer 2012-01-28 23:28 is not another network to improve gps accuracy? 2012-01-28 23:28 + another person in #openmoko-cdevel(morphis) 2012-01-28 23:28 oh interesting (reverse) 2012-01-28 23:29 what hardware does it need to work? 2012-01-28 23:29 so we might share work and/or knowledge 2012-01-28 23:29 i mean receiver part 2012-01-28 23:29 but dont you want to implement a gps sofyware receiver from scratch? dont they? 2012-01-28 23:29 I don't know, MEIF is present at least on some phones like some samsung ones or the nexus S(our target) 2012-01-28 23:29 hmm 2012-01-28 23:30 if you have more information about hw part, IF, etc.. 2012-01-28 23:30 but the interesting part is that it get the raw data, and compute the fix on the phone's CPU 2012-01-28 23:30 yes this sounds very famiiar to RRLP 2012-01-28 23:30 we don't have something working yet but as soon as we have the init sequence we should share infos/code 2012-01-28 23:31 what about hw? 2012-01-28 23:31 what chip does it use? 2012-01-28 23:31 ah I remember now 2012-01-28 23:31 broadcom something 2012-01-28 23:31 hmm, still hard to guess ;) 2012-01-28 23:31 lets see 2012-01-28 23:32 bcm4751 it seem 2012-01-28 23:32 wich phone have it? 2012-01-28 23:32 there is a datasheet floating on the net 2012-01-28 23:32 some samsung phones 2012-01-28 23:32 like the nexus S 2012-01-28 23:32 or other phones 2012-01-28 23:32 look for MEIF on xda 2012-01-28 23:32 Monolithic.. 2012-01-28 23:33 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 23:35 argh, cant find anythoing 2012-01-28 23:35 first time look at that xda 2012-01-28 23:35 do you know xda? 2012-01-28 23:36 let me look 2012-01-28 23:37 "The GPS software also provides native support for Broadcom's Long Term Orbit (LTO) extended ephemeris service" what on hell is that?? 2012-01-28 23:38 why they need extend ehepmeris.. 2012-01-28 23:38 no idea 2012-01-28 23:39 oh oh, you're going to replace firmware inside bcm4751 ? 2012-01-28 23:39 it's da_G 2012-01-28 23:39 no 2012-01-28 23:40 we only want to talk to ir right now 2012-01-28 23:40 da_G is the author of the posts if I remember well 2012-01-28 23:40 ah.. 2012-01-28 23:41 i was looking a datasheet, seems baseband is just another blackbox 2012-01-28 23:41 yes 2012-01-28 23:41 however it's way better than qualcomm phones (for now) 2012-01-28 23:41 so nah, nothing i could get interesting it, as the idea is to get a libre baseband SoC and firmware 2012-01-28 23:41 sure sure 2012-01-28 23:42 basically we should share the : 2012-01-28 23:42 "how to compute GPS fix on a CPU" 2012-01-28 23:42 that dont sound right to me, 2012-01-28 23:43 ah? why? 2012-01-28 23:43 mom 2012-01-28 23:43 ? 2012-01-28 23:43 not free enough? 2012-01-28 23:43 I lack context in your don't sound right to me 2012-01-28 23:43 wait 2012-01-28 23:44 i'm reading this http://wenku.baidu.com/view/0128a23467ec102de2bd8973.html 2012-01-28 23:44 indeed is RRLP related 2012-01-28 23:45 ok 2012-01-28 23:45 I've downloaded the datasheet if you want 2012-01-28 23:45 wikisend it! thanks 2012-01-28 23:45 emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware 2012-01-28 23:46 so far your project look liks this to me http://gps.psas.pdx.edu/ 2012-01-28 23:47 ok 2012-01-28 23:47 i never tought found a "GPS SoC" this days nice ! 2012-01-28 23:47 GPS receiver 2012-01-28 23:48 ? 2012-01-28 23:48 you plan get to the arm cortex later correct? 2012-01-28 23:48 no 2012-01-28 23:48 I'll explain 2012-01-28 23:49 replicant is the project which replaces non-free software and libraries on android phones 2012-01-28 23:49 but you meant, calculate fix on tye cpu 2012-01-28 23:49 so.. 2012-01-28 23:49 we started with the htcdream and qualcomm devices 2012-01-28 23:50 and we found out that they were very bad for freedom since the modem controlled: 2012-01-28 23:50 *the GPS 2012-01-28 23:50 *the sound card 2012-01-28 23:50 *could read/write in the ram of the main CPU 2012-01-28 23:50 but then we found the nexus S 2012-01-28 23:50 another dev which is now the main dev reversed the modem protocol of it 2012-01-28 23:51 we still need to reverse the GPS protocol 2012-01-28 23:51 which is MEIF 2012-01-28 23:51 MEIF is like NMEA ? 2012-01-28 23:51 not at all 2012-01-28 23:52 MEIF is like raw mesurement of the GPS sent to the main CPU(the arm CPU running android) 2012-01-28 23:52 which is why I talked to you about it 2012-01-28 23:52 the fix and everything must be calculated from the main CPU(running android) 2012-01-28 23:52 sounds good 2012-01-28 23:52 so if you have hints on how to calculate fixes with free software we are very interested 2012-01-28 23:53 yes i DO ! 2012-01-28 23:53 well, lindi-_ had some experiences on field too 2012-01-28 23:53 from ublox chips 2012-01-28 23:53 ok 2012-01-28 23:53 that provides navigation data 2012-01-28 23:53 I'd love to have free software GPS running on my freerunner btw 2012-01-28 23:53 but i dont see any hope if you cant hack the arm cortex soc from the broadcon chip 2012-01-28 23:54 wich is that gpl-gps link above is about 2012-01-28 23:54 ok 2012-01-28 23:55 jluis [jluis!~jluis@2001:5c0:1400:a::313] has joined #qi-hardware 2012-01-28 23:55 GNUtoo: if you have more datasheets perhaps i coould help or point something more accurate to do 2012-01-28 23:55 GNUtoo: currently I think it's a major milestone if we can extract raw data from non-free firmware and then recalculate the results from that 2012-01-28 23:56 but resumiing if you can get navigation data from the soc, well is a early first step 2012-01-28 23:56 GNUtoo: replacing the non-free firmware on the chip sounds currently too hard 2012-01-28 23:56 indeed 2012-01-28 23:56 GNUtoo: got a spec for this MEIF? 2012-01-28 23:56 no 2012-01-28 23:56 that's the problem 2012-01-28 23:56 otherwise, trying to reverse eng closed source protocols like that MEIF is a waste of time i think 2012-01-28 23:56 nokia offered it under NDA but they do not anymore 2012-01-28 23:57 kristianpaul: it can't be that complex 2012-01-28 23:57 hack the arm cortex inside the bcm chip !! 2012-01-28 23:57 learn how internals correlator works 2012-01-28 23:58 GPS protocol as you called it not secret, specificaions are public 2012-01-28 23:58 you mean we hack it and reimplement something like NMEA instead? 2012-01-28 23:58 nmea is not very nice format 2012-01-28 23:58 I know 2012-01-28 23:58 i said you cant ingnore this bcm chip run a firmware 2012-01-28 23:58 like AT 2012-01-28 23:58 hack that 2012-01-28 23:58 ubx is actually quite nice 2012-01-28 23:58 ok 2012-01-28 23:58 no learn how talk the chip, no just that 2012-01-28 23:58 compact, simple 2012-01-28 23:59 GNUtoo: or help us port osgps to milkymist soc ! 2012-01-28 23:59 we are working on a free gps baseband and receiver here 2012-01-28 23:59 lindi-_, what's the chip in the openmoko?