| 00:12.18 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 00:35.54 | *** join/#qi-hardware infobot_ (ibot@rikers.org) |
| 00:35.54 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 00:35.54 | *** mode/#qi-hardware [+v infobot_] by ChanServ |
| 01:10.57 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 01:21.38 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 02:15.45 | *** join/#qi-hardware fengling (~fengling@60.10.97.16) |
| 02:58.52 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 02:58.52 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 02:58.59 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 03:34.52 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 03:40.56 | *** join/#qi-hardware rodgort (~rodgort@105.ip-167-114-152.net) |
| 03:50.38 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 04:28.51 | *** join/#qi-hardware rodgort (~rodgort@2607:5300:100:200::160d) |
| 05:05.10 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 05:40.33 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |
| 06:04.33 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 06:12.04 | *** join/#qi-hardware jekhor__ (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 07:40.05 | *** join/#qi-hardware fengling (~fengling@114.111.166.208) |
| 08:17.37 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 09:18.18 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 09:38.57 | *** join/#qi-hardware dandon_ (~dandon@88.151.75.119) |
| 09:47.34 | *** join/#qi-hardware Haswell (~Haswell@unaffiliated/haswell) |
| 10:21.04 | *** join/#qi-hardware fengling (~fengling@114.111.166.208) |
| 10:29.21 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 11:33.11 | *** join/#qi-hardware jekhor__ (~jek@port-232-adslby-pool41.infonet.by) |
| 11:48.50 | DocScrutinizer05 | wpwrak: ((battery is a bit tricky at the moment)) thought about asking? ;-) |
| 12:23.41 | *** join/#qi-hardware jow_laptop (~jow@srv.mein.io) |
| 12:24.56 | wpwrak | hmm ? all i do is available for review and i document my progress in quite some detail :) for example, here's the current battery issue: http://lists.en.qi-hardware.com/pipermail/discussion/2015-February/010811.html |
| 12:26.27 | wpwrak | basically OLED's Vih(min) being quite high, higher than i tought, and i somehow missed that until now. so i need to rearrange the voltage domains. |
| 12:27.57 | *** join/#qi-hardware fengling (~fengling@60.10.97.16) |
| 12:32.49 | wpwrak | but first i'm checking whether my batteries are really still okay. wouldn't do to spend a lot of effort to solve problems that are just caused by dead batteries :) |
| 12:46.55 | *** join/#qi-hardware kilae (~chatzilla@catv-162-034.tbwil.ch) |
| 12:57.39 | *** join/#qi-hardware fengling (~fengling@60.10.97.16) |
| 13:24.51 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 13:26.29 | *** join/#qi-hardware xiangfu (~xiangfu@124.202.191.226) |
| 13:34.11 | xiangfu | wpwrak: Hi. I just uploaded some pics [brd-back-close.jpg brd-back.jpg brd-front-1.jpg brd-front.jpg brd-two.jpg brd-with-UBB-back.jpg brd-with-UBB-front.jpg] to here: http://downloads.qi-hardware.com/people/xiangfu/anelok/tmp/ |
| 13:34.32 | xiangfu | this time is small files. |
| 13:35.33 | xiangfu | I double make sure. the wire connect is correct. there is no short. |
| 13:35.56 | xiangfu | I think there are something wrong with my nanonote. trying the ubbctl now.. |
| 13:36.49 | wpwrak | (photos) whee, nice ! thanks ! |
| 13:37.18 | wpwrak | (nanonote) oh, did you disable the mmc driver ? echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind |
| 13:37.40 | xiangfu | no. |
| 13:37.41 | xiangfu | :( |
| 13:37.43 | wpwrak | and if your kernel has an atben driver, then also cd /sys/bus/spi/drivers/at86rf230; echo spi*.0 >unbind |
| 13:38.10 | wpwrak | okay, kernel and user space both trying to use the port at the same time may explain some issues :) |
| 13:39.21 | wpwrak | (pics) you have front and back reversed in the file names :) |
| 13:43.18 | xiangfu | Yes. |
| 13:45.12 | xiangfu | download the nanonote toolchain for compile ubbctl |
| 13:45.32 | wpwrak | hmm, and you may have placed too many of the resistors around the boost converter. e.g., if you're using the AAT1217-3.3, R4-R6 should be DNP. it looks as if they're populated |
| 13:48.20 | wpwrak | or is this just an optical illusion ? |
| 13:54.14 | xiangfu | nothing on F4-R6 |
| 14:18.28 | xiangfu | wpwrak: http://dpaste.com/0VN8S25 |
| 14:18.36 | xiangfu | ubbctl + swd. |
| 14:25.26 | wpwrak | DAT0 looks unhappy |
| 14:25.39 | wpwrak | seems to be shorted to ground in some way |
| 14:28.49 | xiangfu | hmm... I am sure the DAT0 means SWD_CLK is not shorted at UBB or Anelok. |
| 14:29.49 | wpwrak | the DAT0=1!0 says that the ben is trying to output a 1 but it reads back a 0 |
| 14:31.24 | wpwrak | but you can check this by setting the outputs manually (with ubbctl) and measuring |
| 14:32.26 | wpwrak | and you may also want to check the supply voltage. if there's a problem somewhere, it may be too low, but still not low enough to just crash the ben as well |
| 14:32.43 | wpwrak | (though shorts usually crash the ben. so one has instant feedback ;-) |
| 14:32.50 | xiangfu | one of the board : the SWD_CLK between GND have 60ohm |
| 14:35.04 | xiangfu | Here is another board output: http://dpaste.com/0VMV98X |
| 14:35.23 | wpwrak | 60 ohm is quite low. if you short the probes via the board, how many ohm do you get ? |
| 14:38.50 | wpwrak | in any case, 60 ohm is too low. i measured for both SWD_CLK and SWD_DIO abour 7.8 MOhm if + is on SWD_* and 0 on GND, and about 27 kOhm if - is on SWD_* and + on GND |
| 14:39.38 | xiangfu | hmm... wait. |
| 14:39.59 | xiangfu | this device is not easy to understand. I borrow a Agilent U1252B. |
| 14:40.21 | wpwrak | results may be different with different meters (that was with a picotest m3500a, alas not the most exact device but my fluke is busy watching the batter discharge), but anything lower than at least a few kOhm is suspicious |
| 14:40.55 | wpwrak | similar to joerg's critter :) |
| 14:42.38 | xiangfu | ./ubbctl dat0=0: give me 0.0091v |
| 14:42.45 | xiangfu | ./ubbctl dat0=1: give m1 0.5xxxv |
| 14:42.55 | *** join/#qi-hardware jwhitmore (~jwhitmore@host213-122-244-203.range213-122.btcentralplus.com) |
| 14:43.02 | xiangfu | ./ubbctl dat0=1: give m1 0.65xxv |
| 14:43.16 | xiangfu | s/m1/me |
| 14:43.16 | qi-bot | xiangfu meant: "./ubbctl dat0=1: give me 0.65xxv" |
| 14:43.52 | xiangfu | ./ubbctl dat0=1: give m1 0.5xxx ~ 0x65xxv |
| 14:44.32 | xiangfu | this one ./ubbctl dat1=1: give me 3.3V. I like 3.3 :) |
| 14:45.35 | *** join/#qi-hardware jow_laptop (~jow@srv.mein.io) |
| 14:45.40 | *** join/#qi-hardware uwe_ (~uwe_@dslb-088-067-009-230.088.067.pools.vodafone-ip.de) |
| 14:45.44 | *** join/#qi-hardware xiangfu (~xiangfu@124.202.191.226) |
| 14:45.47 | xiangfu | U1251B is expensive... |
| 14:46.05 | *** join/#qi-hardware kilae (~chatzilla@catv-162-034.tbwil.ch) |
| 14:46.58 | xiangfu | wpwrak: have you saw my last message: |
| 14:46.59 | xiangfu | ~~~~ |
| 14:46.59 | infobot | ARGH!!! STOP IT xiangfu!!! |
| 14:47.05 | xiangfu | ./ubbctl dat0=1: give m1 0.5xxx ~ 0x65xxv |
| 14:47.17 | xiangfu | but ./ubbctl dat1=1: give me a very stable 3.3V. |
| 14:47.32 | xiangfu | ~ |
| 15:01.19 | wpwrak | yes, 3.3 V is good. 0.65 V suggests that there's a short. apparently not directly with ground but with some other pin |
| 15:02.42 | wpwrak | (u1252b) yeah, these agilent/keysight meters are a bit overpriced in my opinion. i'd get a good lab meter. not portable, but much nicer to use in the lab. and you don't have to worry about batteries ;) |
| 15:03.12 | wpwrak | #s/lab meter/bench meter/ that's the correct term |
| 15:04.08 | wpwrak | the good ones are even more expensive, but if you're going to spend many hundreds of dollars on a meter, you may as well go the extra mile and get a really good one |
| 15:04.52 | xiangfu | YEAH: http://dpaste.com/24MHQ07 |
| 15:05.01 | wpwrak | the 0.65 V may be a short between DAT0 and some pin that outputs a "0". maybt try CLK=1 and see what happens |
| 15:05.40 | xiangfu | hmm... he sugest me this one: F179C . |
| 15:05.47 | xiangfu | FLUKE. expensive too. :) |
| 15:05.57 | wpwrak | if it's not that, things will get a bit more complicated. you could then test all the other pins of the KL26 and see if there's another one that has 0.65 V |
| 15:06.08 | xiangfu | wpwrak: it is the my taobao UBB soldering problem. |
| 15:06.50 | xiangfu | first try: http://dpaste.com/2TQCYQE |
| 15:06.54 | xiangfu | again |
| 15:07.15 | xiangfu | second try: http://dpaste.com/2F2K93R |
| 15:07.30 | wpwrak | (fluke) maybe this ? http://www.testequipmentdepot.com/fluke/dmm/8808a.htm |
| 15:07.54 | xiangfu | flashed: http://dpaste.com/0JKC8ZH |
| 15:08.03 | xiangfu | what should I do next? |
| 15:08.14 | wpwrak | (fluke) i have this one (the 8808a didn't exist back then): http://www.testequipmentdepot.com/fluke/dmm/8845a.htm |
| 15:08.23 | wpwrak | lemme check ... |
| 15:08.59 | wpwrak | (flashing) excellent ! it's normal that it takes a few tries |
| 15:09.21 | wpwrak | you could now connect USB and see if it enumerates |
| 15:09.39 | wpwrak | when the led goes on after you connect usb, it's probably happy |
| 15:09.56 | wpwrak | ah, and i would disconnect the ben first. just in case :) |
| 15:11.05 | wpwrak | and if it enumerates, you can then "make dfu" to flash the firmware |
| 15:12.03 | wpwrak | after flashing the firmware, the led will go off. you'll then have to wait for about 30 seconds and then you should be able to operate the slider |
| 15:12.19 | xiangfu | connect usb: nothing happen on kernel msg |
| 15:12.23 | wpwrak | will be a bit tricky without a case but you should at least get some response |
| 15:12.47 | wpwrak | okay, not so easy then :) |
| 15:13.13 | wpwrak | with usb connected, please check that the voltages are right: especially that VBUS > GND :) |
| 15:13.58 | wpwrak | (there is a big VBUS pad right next to the usb connector) |
| 15:14.59 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 15:15.00 | wpwrak | vbus should be roughly 5 V. if it's very different, somethign is wrong. |
| 15:17.04 | xiangfu | VBUS: -0.15v |
| 15:18.46 | wpwrak | eeew |
| 15:19.32 | wpwrak | hmm. are you sure you got the right type of conenctor ? :) |
| 15:19.46 | wpwrak | yours don't look reversed |
| 15:20.22 | wpwrak | in a reversed connector, the two little slots should be at the bottom |
| 15:20.36 | wpwrak | not sure if there are reversed connector that have them on the other side |
| 15:21.33 | wpwrak | are your connectors AB or B ? |
| 15:23.41 | xiangfu | hmm... -4.5V |
| 15:23.48 | wpwrak | how to identify a reversed connector: the little plastic inside the connector should be close to the PCB, with the contacts facing away from the PCB |
| 15:24.18 | wpwrak | that looks even more like the wrong connector |
| 15:25.02 | wpwrak | (reversed = what anelok needs) |
| 15:25.17 | xiangfu | Yes. wrong connecter... |
| 15:26.00 | wpwrak | let's hope you have a good electronic shop nearby :) |
| 15:26.30 | wpwrak | well, at midnight, it may not be open, though. or do you have all night electronics shopping in china ? :) |
| 15:28.17 | xiangfu | not in Beijing. maybe in Shengzhen. |
| 15:28.19 | wpwrak | (regarding the usb connector, i hope to eventually replace this with a regular - non-reversed - connector. but so far i haven't been able to find a nice way to do this. layout gets very tricky.) |
| 15:31.51 | wpwrak | okay, what we can do now is ... a) wait until you can get right kind of connector, b) you can try to make a reversed cable, c) you could try to flash the application via SWD. but that's a bit messy because SWD is so unreliable and the application is larger than the boot loader |
| 15:32.48 | xiangfu | let me try the SWD. |
| 15:33.14 | xiangfu | what is the command for reflash teh application? |
| 15:33.33 | wpwrak | first you have to construct a combined binary |
| 15:35.57 | wpwrak | this should do the trick: dd bs=16k conv=sync if=boot-2014.bin of=combined.bin; cat anelok-2014.bin >>combined.bin |
| 15:36.34 | wpwrak | then flash with swd combined.bin |
| 15:39.42 | wpwrak | hmm. my statistical estimates suggest that it may take something like 80 attempts before swd will work for somethign this large, given that it took you three attempts with boot-2014.bin. well, you can use a while loop :) |
| 15:40.40 | wpwrak | while ! ./swd combined.bin; do : ; done # then take a tea or a nap ;-) |
| 15:41.02 | *** join/#qi-hardware porchao (~quassel@218.231.148.105.eo.eaccess.ne.jp) |
| 15:43.07 | xiangfu | a lot of access error |
| 15:43.49 | wpwrak | yes, there's something wrong but i don't know what. i already spent a lot of time trying to figure out what may be the problem :-( |
| 15:44.01 | xiangfu | finished one. |
| 15:44.14 | wpwrak | maybe a fresh pair of eyes will find it in minutes ... ;) |
| 15:44.32 | xiangfu | successed one of them |
| 15:45.46 | *** join/#qi-hardware rodgort (~rodgort@105.ip-167-114-152.net) |
| 15:48.03 | wpwrak | excellent ! :) now .. swd -r to power and reset anelok |
| 15:48.49 | wpwrak | and then we'll see if it works :) (i've never tried this mode of operation myself) |
| 15:51.01 | wpwrak | yup, should work. just booted one of mine with ./swd -r |
| 15:52.01 | wpwrak | ah, but now i have to leave. people trickling in. |
| 15:52.21 | xiangfu | yes. now I am doing 'while'... :) |
| 15:54.23 | xiangfu | have to sleep. |
| 16:05.39 | *** join/#qi-hardware rodgort (~rodgort@105.ip-167-114-152.net) |
| 16:07.34 | *** join/#qi-hardware jekhor (~jek@46.216.12.20) |
| 16:42.43 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::2) |
| 16:43.41 | *** join/#qi-hardware jwhitmore (~jwhitmore@host213-122-244-203.range213-122.btcentralplus.com) |
| 16:58.19 | *** join/#qi-hardware FDCX (~fdcx@2a02:2f0a:a03f:ffff::bc19:9094) |
| 19:26.31 | *** join/#qi-hardware FDCX_ (~fdcx@188.25.144.148) |
| 19:28.28 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 20:23.38 | *** join/#qi-hardware arossdotme (~butler@79-69-195-92.dynamic.dsl.as9105.com) |
| 20:36.08 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-4d0cc6ab.pool.mediaWays.net) |
| 21:12.06 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 22:05.00 | *** join/#qi-hardware ChanServ (ChanServ@services.) |
| 22:05.00 | *** mode/#qi-hardware [+o ChanServ] by rajaniemi.freenode.net |
| 22:37.10 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |
| 22:40.29 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 22:49.27 | *** join/#qi-hardware porchaso0 (~quassel@218.231.148.105.eo.eaccess.ne.jp) |
| 22:53.15 | *** join/#qi-hardware viric_ (~viric@unaffiliated/viric) |
| 23:02.18 | *** join/#qi-hardware woakas (~woakas@static.13.240.46.78.clients.your-server.de) |
| 23:17.05 | *** join/#qi-hardware arossdotme (~butler@79-69-195-92.dynamic.dsl.as9105.com) |
| 23:57.28 | *** join/#qi-hardware arossdotme (~butler@79-69-195-92.dynamic.dsl.as9105.com) |