| 01:06.01 | *** join/#qi-hardware GitHub164 (~GitHub164@192.30.252.40) |
| 01:06.02 | GitHub164 | [13j1soc] 15kristianpaul pushed 1 new commit to 06master: 02https://github.com/kristianpaul/j1soc/commit/7633b712734d149c6719c227edd0d709a23e3f15 |
| 01:06.02 | GitHub164 | 13j1soc/06master 147633b71 15Cristian Paul Penaranda Rojas: Update to 14.6 ISE |
| 01:06.02 | *** part/#qi-hardware GitHub164 (~GitHub164@192.30.252.40) |
| 01:08.43 | kristianpaul | eww |
| 01:08.50 | kristianpaul | that stills works :p |
| 01:21.05 | *** join/#qi-hardware sb0 (~sb0@123202036015.ctinets.com) |
| 01:43.10 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d36:0:40af:482f:c0af:951) |
| 02:00.05 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 02:27.03 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 02:29.35 | wpwrak | kristianpaul: great, eh ? :) |
| 02:32.27 | wpwrak | xiangfu: heya ! how's life ? in the last days, i made a bit of progress with anelok. after the boost converter rework, it can run on battery power. at least the basic system (MCU and OLED). so i'd recommend applying the rework to the devices you have as well. |
| 02:33.51 | xiangfu | wpwrak: great. I am slow on anelok. I will try that. |
| 02:34.09 | wpwrak | xiangfu: we may see problems with the memory card, though. the worst-case power demand of these cards can go up to 300 mW, while the CR2032 can at best deliver a bit more than 100 mW. |
| 02:35.05 | wpwrak | what i don't know yet is how bad they are in real life. presumably a lot nicer than that, but only measurements will tell. |
| 02:35.51 | wpwrak | if they need more power than the battery can supply, then the current design won't work and we'll have to switch to AAA or such :-( |
| 02:37.06 | wpwrak | (current design) that is, mainly the mechanical design. the electrical side would almost be identical. to if one doesn't mind an ugly case, the same PCB could be used. at least in theory :) |
| 02:41.48 | wpwrak | for experimenting with the memory card, i'd like to integrate some things from your code. i think it may be easiest if i just cherry-pick, so you don't have to generate pull requests. does that sound okay for you ? |
| 02:45.23 | xiangfu | sure. |
| 02:45.40 | xiangfu | Yes. free feel to cherry-pick |
| 02:50.35 | wpwrak | great. i'll do this during the long easter weekend. |
| 03:13.44 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d36:0:345d:207a:da25:1cfe) |
| 04:21.25 | *** join/#qi-hardware archang (~archang@111.198.29.54) |
| 04:55.45 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 05:01.47 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 05:11.15 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 06:06.56 | *** join/#qi-hardware wolfspraul (~wolfsprau@x5f72ecac.dyn.telefonica.de) |
| 06:07.43 | *** join/#qi-hardware wolfspraul (~wolfsprau@x5f72ecac.dyn.telefonica.de) |
| 06:22.24 | *** join/#qi-hardware jekhor__ (~jek@nat-minsk-pool-46-53-200-107.telecom.by) |
| 06:57.44 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 07:06.33 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 07:56.33 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 08:12.55 | DocScrutinizer05 | wpwrak: ((presumably a lot nicer than that)) uSD? don't bet on that, constant writes on uSD heat them up to temperatures where you start to worry |
| 08:13.27 | DocScrutinizer05 | then otoh *reads* are prolly way nicer, due to operation principles |
| 08:15.40 | DocScrutinizer05 | how about CR2045? |
| 08:16.10 | DocScrutinizer05 | wouldn't change THAT jmuch on your design, only 1 1.3mm higher case, right? |
| 08:16.34 | DocScrutinizer05 | s/ 1 / a / |
| 08:16.35 | qi-bot | DocScrutinizer05 meant: "wouldn't change THAT jmuch on your design, only a 1.3mm higher case, right?" |
| 08:30.11 | *** join/#qi-hardware jwhitmore_ (~jwhitmore@109.79.176.204) |
| 09:44.37 | *** join/#qi-hardware jekhor (~jek@port-206-adslby-pool37.infonet.by) |
| 09:53.29 | *** join/#qi-hardware wolfspraul (~wolfsprau@x5f72ecac.dyn.telefonica.de) |
| 10:24.18 | *** join/#qi-hardware wolfspraul (~wolfsprau@x5f72ecac.dyn.telefonica.de) |
| 10:43.12 | *** join/#qi-hardware jwhitmore_ (~jwhitmore@109.79.176.204) |
| 11:18.09 | wpwrak | (much nicer) well, the idea is to use the memory card only very infrequently, especially writes. and we can go slowly - do a sector, take a break for a few dozen milliseconds, etc. |
| 11:19.22 | wpwrak | cr2045 seems a bit on the exotic side, isn't it ? digi-key don't even have that type |
| 11:25.35 | wpwrak | 2450 seems to be somewhat common. internal resistance is still pretty high, though |
| 11:26.57 | wpwrak | about 12-15 ohm for cr2450 vs. 20 ohm for cr2032 |
| 11:33.09 | wpwrak | if we assume an ideal cell voltage of 2.8 V, then max power of 2032 is ~100 mW and of 2450 ~160 mW |
| 11:34.08 | wpwrak | but yes, it could be a possibility luckily, anelok's battery holder is on a separate board, so it's very easy to accommodate other cells :) |
| 11:34.37 | wpwrak | i hadn't even thought of other coins. thanks ! |
| 11:36.08 | DocScrutinizer05 | yw |
| 11:36.27 | DocScrutinizer05 | ((much nicer)) the suspected problem case is page erase |
| 11:36.40 | DocScrutinizer05 | you hardly can mitigate that |
| 11:37.48 | DocScrutinizer05 | only way: provide buffer energy ("Hasso! Schlafende!") sufficient for one page erase |
| 11:41.29 | wpwrak | for the first round of devices, i could just buffer writes in internal flash, then commit them to the memory card when there's plenty of power. not ideal, but one would hardly notice |
| 11:42.17 | wpwrak | and i did the calculations for buffering worst-case power. it should actually be possible, but you need a fat supercap for it. |
| 11:44.11 | DocScrutinizer05 | http://www.zubrod-net.de/Orion/Episode-2.pdf p.7 |
| 11:45.25 | wpwrak | not the usual coin type or other small ones (internal resistance way too high) but there are some larger blocks that have a low resistance. not cheap, though, some USD 5+ apiece @ 1000 at digi-key |
| 11:45.40 | wpwrak | e.g., this critter: http://www.digikey.com/product-detail/en/BZ055B153ZSB/478-3645-ND/1045919 |
| 11:46.27 | DocScrutinizer05 | or you siply go for two cr2015 in series |
| 11:47.01 | DocScrutinizer05 | wouldn't even need major rework in battery holder, I guess |
| 11:48.01 | DocScrutinizer05 | double voltage, half the current |
| 11:48.21 | DocScrutinizer05 | needs buck converter then |
| 11:48.34 | DocScrutinizer05 | well, they're 'cheap' |
| 11:49.23 | wpwrak | 2016 ? would need to change the converter, yes. the current one is only step-up |
| 11:50.22 | DocScrutinizer05 | go for buck/boost type, should be "compatible" |
| 11:51.06 | wpwrak | resistance is the same as 2032, so one could indeed draw more juice |
| 11:51.36 | DocScrutinizer05 | evidently, since you only need half the current at twice the voltage for same energy |
| 11:54.00 | DocScrutinizer05 | of course, if the cr2016 had tiwce the ESR than CR2032, it would be a zero-sum equation |
| 11:55.53 | wpwrak | yup |
| 11:56.58 | *** join/#qi-hardware kyak (~kyak@128-72-187-236.broadband.corbina.ru) |
| 11:56.58 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 11:56.59 | wpwrak | but if i make major changes, i'd probably go to AAA then. ESR drops by some two orders of magnitude |
| 11:59.07 | wpwrak | i actually tried to feed my current boost critter with a low voltage, but it didn't like that for some reason. may be a lab effect, though - they specifically warn about the inductance of long feed lines from the lab power supply |
| 12:02.44 | wpwrak | the chop should be good down to 0.85 V to start, 0.5 V when running. idle current is too high, though, 0.5 mA, but there's a close cousin from TI that's much better |
| 12:04.51 | wpwrak | (lab effect) also, they're weasling in their reference circuit: the caps they specify are 4.7 uF, so they look all nice and efficient, but then they mention that this is effective capacitance, so you really need a bigger cap because real-life caps usually don't have their nominal capacitance when you actually make them do something |
| 12:06.17 | wpwrak | that's another pending rework item. and the we'll see if the critter can handle an alcaline from the next supermarket. i mean, even logitech can do it in their mice, so how hard can it be ? ;-) |
| 12:11.27 | DocScrutinizer05 | should work |
| 12:32.28 | *** join/#qi-hardware paul_boddie (~paul_bodd@cm-84.215.167.166.getinternet.no) |
| 12:41.50 | DocScrutinizer05 | well, even AAAA are too weak it seems: http://data.energizer.com/PDFs/E96.pdf |
| 12:42.25 | DocScrutinizer05 | AAA prolly should work |
| 12:43.47 | DocScrutinizer05 | yeah, easily http://data.energizer.com/PDFs/XR91.pdf |
| 12:48.01 | DocScrutinizer05 | http://data.energizer.com/ is quite convenient site |
| 12:48.21 | *** join/#qi-hardware kyak (~kyak@128-72-170-218.broadband.corbina.ru) |
| 12:48.37 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 12:54.20 | wpwrak | AAAA ... heh, another exotic type :) |
| 12:55.51 | wpwrak | i want to stay mainstream. the sort of batteries you can find in a village you visit for the first time and where you don't speak the local language :) |
| 12:58.30 | wpwrak | i.e., AA >> AA > CR2032. but then AA would be rather big. |
| 12:59.42 | DocScrutinizer05 | go for AAA then |
| 12:59.56 | DocScrutinizer05 | even CR2032 are sort of tricky |
| 13:00.12 | DocScrutinizer05 | and friggin expensive |
| 13:01.30 | wpwrak | around here they're about 50 us-cents apiece if you buy a bunch. else, about 80 us-cents. so they must be single-digit cents in the rest of the world :) |
| 13:20.41 | paul_boddie | Argentina provides the "distressed economy" test, I guess. ;-) |
| 13:25.44 | wpwrak | guess that's happens when beavis and butthead grow up and become ministers |
| 13:28.22 | paul_boddie | Wonder how much they are here... 29 NOK! |
| 13:29.22 | paul_boddie | I was reading about Argentine political history not that long ago. Enlightening and rather sad. |
| 13:29.45 | wpwrak | elections are in october. there will be a reckoning. |
| 13:30.55 | wpwrak | NOK 29 = USD 3.6. that's for how many CR2032 ? |
| 13:31.57 | paul_boddie | Just one at expensive retailer: http://www.clasohlson.com/no/Varta-litium-batterier/32-2236 |
| 13:33.30 | paul_boddie | Their UK shop is as expensive. Will look closer when next in the supermarket. |
| 13:33.31 | wpwrak | wow, nice margin ;-) |
| 13:34.14 | wpwrak | first hit on ebay: http://www.ebay.com/itm/5-Energizer-2032-Battery-CR2032-Lithium-3v-Batteries-/280639218596 |
| 13:35.53 | wpwrak | for really good prices, you may want to get 100 or so. like this: http://articulo.mercadolibre.com.ar/MLA-545118517-100-pilas-cr2032-sony-litio-boton-20blister-x5und-en-caja-_JM |
| 13:36.22 | wpwrak | that's ARS 500, so about 50-60 US-cents |
| 13:36.46 | wpwrak | apiece |
| 13:37.40 | paul_boddie | The amusing thing about Clas Ohlson's "own brand" cells is that there's a review by some Swedish person... |
| 13:38.06 | paul_boddie | ...complaining that they used one in their banking code generator and it immediately complained about a low battery. Caveat emptor! |
| 13:38.32 | wpwrak | well, if someone is gullible enough to pay at that price, ... |
| 13:39.12 | wpwrak | hmm. s/pay/buy/ || s/ at// |
| 13:40.00 | paul_boddie | The cheap ones seem to work in kitchen scales and such things OK, in my experience. |
| 13:40.57 | wpwrak | if you want cheap and don't mind if it's alkalines and not button cells, how about this lovely deal ? http://www.ebay.com/itm/100-AAA-ALKALINE-LOOSE-BATTERIES-/121560854139?pt=LH_DefaultDomain_3&hash=item1c4d976e7b |
| 13:41.18 | wpwrak | somebody must have been robbing the trash bins |
| 13:42.17 | larsc | 'these have been in our warehouse for a few years and the boxes got water damaged' |
| 13:43.23 | paul_boddie | Of course, corroding coin cells are a real peril with old computers. |
| 13:47.14 | wpwrak | never saw a coin cell corrode. alkaline, though, armies of them ... |
| 13:56.13 | paul_boddie | larsc: Looking at the jz4740 PWM driver, it appears usable for the jz4730 at a glance, but I think the pin assignments differ. |
| 13:57.57 | larsc | yea, that's kind of expected |
| 13:58.17 | larsc | let me have a quick look at the datasheet |
| 13:59.05 | paul_boddie | wpwrak: http://www.retro-kit.co.uk/page.cfm/content/Acorn-BBC-A3000-Battery-Maintenance/ |
| 13:59.12 | pcercuei | that's not a problem |
| 13:59.17 | paul_boddie | wpwrak: Although that's technically not a coin cell. |
| 13:59.33 | pcercuei | the PWM driver doesn't know anything about the pin assignment |
| 14:00.06 | paul_boddie | jz4740_pwm_gpio_list mentions JZ_GPIO_PWM0 through JZ_GPIO_PWM7 |
| 14:00.55 | paul_boddie | JZ_GPIO_PORTD(23) through JZ_GPIO_PORTD(31), apparently. |
| 14:01.04 | pcercuei | because that's old code |
| 14:01.17 | pcercuei | we have an updated one: https://github.com/gcwnow/linux/blob/jz-3.19/drivers/pwm/pwm-jz4740.c |
| 14:01.49 | paul_boddie | Is that going to be merged upstream at some point? |
| 14:02.10 | pcercuei | that's the plan |
| 14:02.21 | pcercuei | but I need larsc to finish the pinctrl driver first :) |
| 14:02.50 | pcercuei | (since this updated driver requires that you have a pinctrl driver) |
| 14:03.09 | paul_boddie | Linux dependency hell! ;-) |
| 14:17.22 | *** join/#qi-hardware valhalla (~valhalla@149-71-148-166.v4.ngi.it) |
| 14:22.00 | *** join/#qi-hardware dandon_ (~dandon@88.151.72.40) |
| 14:33.03 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 14:58.13 | *** join/#qi-hardware jwhitmore_ (~jwhitmore@109.79.176.204) |
| 15:09.13 | *** join/#qi-hardware jekhor (~jek@port-206-adslby-pool37.infonet.by) |
| 15:10.06 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 15:29.11 | paul_boddie | Is it worth following device tree work for jz47xx? If so, where should I be following? |
| 15:29.48 | larsc | yes |
| 15:30.00 | larsc | non-devicetree is not going to be supported in the future |
| 15:34.38 | paul_boddie | I see that there's some jz4770 DT stuff, and maybe the MIPS people did some jz4780 DT stuff as well. |
| 15:36.01 | whitequark | wpwrak: that's because coin cells use methanol for electrolyte |
| 15:36.08 | whitequark | they're not really "battery" cells |
| 15:36.16 | whitequark | they're more like fuel cells with a semipermeable membrane |
| 15:36.25 | whitequark | and metallic li |
| 15:47.49 | pcercuei | there's some jz4740 stuff as well |
| 15:54.22 | paul_boddie | I found a 3.18 branch in gcwnow for DT, but is that the "most upstream" place? |
| 15:55.32 | pcercuei | qi-hardware is the "most upstream" for jz4740, gcwnow is the "most upstream" for jz4770, MIPS/CI20_Linux is the "most upstream" for jz4780 :) |
| 15:56.46 | paul_boddie | I meant for DT. I didn't think the qi-kernel repo was being updated any more. |
| 15:57.02 | pcercuei | ah, then it's the jz4780 tree from the MIPS guys |
| 15:57.41 | pcercuei | we started moving our jz4770 tree to DT some months ago, but some parts (e.g. clocks driver) aren't easy |
| 15:58.20 | paul_boddie | OK. I'll have a look at what the MIPS people have for DT. |
| 15:58.56 | paul_boddie | Short of that, I'm tempted to do some dirty hacks to see if the "old" jz4740 PWM driver can be tweaked to work with jz4730 pin assignments. |
| 15:59.31 | paul_boddie | I think the timer/counter registers are the same between the jz4730 and jz4740. |
| 15:59.45 | pcercuei | if you want to do it cleanly, bump larsc - IIRC he has a pinctrl driver ready for jz4740 |
| 16:00.08 | pcercuei | the pin assignments are done in DT so it would probably work on jz4730 as well |
| 16:00.31 | pcercuei | (e.g. we use the exact same pinctrl driver for jz4770 and jz4780 now) |
| 16:00.49 | pcercuei | if the subsystem didn't change too much it may even be used for older versions |
| 16:04.22 | paul_boddie | I think the confusing thing when looking at the old (2.6) code is, apart from kernel coding changes, the way some things like PWM are done. |
| 16:05.24 | paul_boddie | It's hard to tell from vendor code, though, as they dump their internal knowledge to C. |
| 16:06.36 | paul_boddie | But since the timer/counter unit looks the same, we can probably ignore weird vendor stuff and go the tried and tested route. |
| 16:16.47 | *** join/#qi-hardware Haswell (~broaderba@unaffiliated/haswell) |
| 17:14.17 | eintopf | https://www.amazon.com/oc/dash-button |
| 17:15.13 | eintopf | wpwrak: that's like the shaver which buys blades when they are empty |
| 17:20.47 | *** join/#qi-hardware sb0 (~sb0@123202036015.ctinets.com) |
| 17:35.48 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 17:49.45 | paul_boddie | eintopf: Hope it has built-in "surge protection" for when someone's child presses the button for chocolate a hundred times. :-) |
| 17:55.20 | *** join/#qi-hardware FDCX (357@86.127.72.28) |
| 18:08.39 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 18:11.02 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 18:30.46 | arossdotme | what is the resistor value to put across a usb socket to that connects to a usb charger to get max current? |
| 18:31.34 | arossdotme | i'm making up a micro usb socket pwr input adaptor for my zipit. |
| 18:31.59 | arossdotme | so i can use a standard microusb socket to charge/pwr my device |
| 18:32.37 | arossdotme | where would i find this info, in the usb doc? isn't such info hard to find in the doc? |
| 18:40.15 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 18:53.56 | *** join/#qi-hardware jekhor (~jek@port-206-adslby-pool37.infonet.by) |
| 18:55.55 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 18:56.08 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::9) |
| 19:02.57 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 19:04.56 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 19:27.58 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 20:01.27 | *** join/#qi-hardware FDCX (357@5-12-185-186.residential.rdsnet.ro) |
| 20:20.58 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-107.telecom.by) |
| 20:57.05 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 21:51.10 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 23:21.17 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |