archang has quit [Remote host closed the connection]
archang has joined #qi-hardware
rodgort has joined #qi-hardware
archang has quit [Ping timeout: 246 seconds]
archang has joined #qi-hardware
atommann has quit [Ping timeout: 256 seconds]
Textmode has joined #qi-hardware
atommann has joined #qi-hardware
jekhor__ has joined #qi-hardware
atommann has quit [Ping timeout: 252 seconds]
fengling has quit [Ping timeout: 246 seconds]
fengling has joined #qi-hardware
atommann has joined #qi-hardware
jekhor__ has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
fengling has quit [Ping timeout: 264 seconds]
atommann has quit [Ping timeout: 245 seconds]
Textmode has quit [Quit: "It was one dev, naked in a room with a carton of cigarettes, a thermos full of coffee and bourbon, and all his summoned angels."]
dandon_ has joined #qi-hardware
dandon has quit [Ping timeout: 244 seconds]
dandon_ is now known as dandon
Haswell has joined #qi-hardware
fengling has joined #qi-hardware
pcercuei has joined #qi-hardware
fengling has quit [Ping timeout: 252 seconds]
jekhor__ has joined #qi-hardware
<DocScrutinizer05>
wpwrak: ((battery is a bit tricky at the moment)) thought about asking? ;-)
<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.
fengling has joined #qi-hardware
<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 :)
fengling has quit [Ping timeout: 246 seconds]
kilae has joined #qi-hardware
fengling has joined #qi-hardware
archang has quit [Remote host closed the connection]
archang has joined #qi-hardware
xiangfu has joined #qi-hardware
<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/
<xiangfu>
this time is small files.
<xiangfu>
I double make sure. the wire connect is correct. there is no short.
<xiangfu>
I think there are something wrong with my nanonote. trying the ubbctl now..
<wpwrak>
(photos) whee, nice ! thanks !
<wpwrak>
(nanonote) oh, did you disable the mmc driver ? echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
<xiangfu>
no.
<xiangfu>
:(
<wpwrak>
and if your kernel has an atben driver, then also cd /sys/bus/spi/drivers/at86rf230; echo spi*.0 >unbind
<wpwrak>
okay, kernel and user space both trying to use the port at the same time may explain some issues :)
<wpwrak>
(pics) you have front and back reversed in the file names :)
<xiangfu>
Yes.
<xiangfu>
download the nanonote toolchain for compile ubbctl
<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
<wpwrak>
seems to be shorted to ground in some way
<xiangfu>
hmm... I am sure the DAT0 means SWD_CLK is not shorted at UBB or Anelok.
<wpwrak>
the DAT0=1!0 says that the ben is trying to output a 1 but it reads back a 0
<wpwrak>
but you can check this by setting the outputs manually (with ubbctl) and measuring
<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
<wpwrak>
(though shorts usually crash the ben. so one has instant feedback ;-)
<xiangfu>
one of the board : the SWD_CLK between GND have 60ohm
<wpwrak>
60 ohm is quite low. if you short the probes via the board, how many ohm do you get ?
<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
<xiangfu>
hmm... wait.
<xiangfu>
this device is not easy to understand. I borrow a Agilent U1252B.
<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
<wpwrak>
similar to joerg's critter :)
<xiangfu>
./ubbctl dat0=0: give me 0.0091v
<xiangfu>
./ubbctl dat0=1: give m1 0.5xxxv
jwhitmore has joined #qi-hardware
<xiangfu>
./ubbctl dat0=1: give m1 0.65xxv
<xiangfu>
s/m1/me
<qi-bot>
xiangfu meant: "./ubbctl dat0=1: give me 0.65xxv"
<xiangfu>
./ubbctl dat0=1: give m1 0.5xxx ~ 0x65xxv
<xiangfu>
this one ./ubbctl dat1=1: give me 3.3V. I like 3.3 :)
xiangfu has quit [*.net *.split]
kilae has quit [*.net *.split]
jow_laptop has quit [*.net *.split]
uwe_ has quit [*.net *.split]
jow_laptop has joined #qi-hardware
uwe_ has joined #qi-hardware
xiangfu has joined #qi-hardware
<xiangfu>
U1251B is expensive...
kilae has joined #qi-hardware
<xiangfu>
wpwrak: have you saw my last message:
<xiangfu>
~~~~
<infobot>
ARGH!!! STOP IT xiangfu!!!
<xiangfu>
./ubbctl dat0=1: give m1 0.5xxx ~ 0x65xxv
<xiangfu>
but ./ubbctl dat1=1: give me a very stable 3.3V.
<xiangfu>
~
<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
porchao has quit [Quit: Leaving...]
<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 ;)
<wpwrak>
#s/lab meter/bench meter/ that's the correct term
<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
<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
<xiangfu>
hmm... he sugest me this one: F179C .
<xiangfu>
FLUKE. expensive too. :)
<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
<xiangfu>
wpwrak: it is the my taobao UBB soldering problem.
<wpwrak>
(flashing) excellent ! it's normal that it takes a few tries
<wpwrak>
you could now connect USB and see if it enumerates
<wpwrak>
when the led goes on after you connect usb, it's probably happy
<wpwrak>
ah, and i would disconnect the ben first. just in case :)
<wpwrak>
and if it enumerates, you can then "make dfu" to flash the firmware
<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
<xiangfu>
connect usb: nothing happen on kernel msg
<wpwrak>
will be a bit tricky without a case but you should at least get some response
<wpwrak>
okay, not so easy then :)
<wpwrak>
with usb connected, please check that the voltages are right: especially that VBUS > GND :)
<wpwrak>
(there is a big VBUS pad right next to the usb connector)
<wpwrak>
vbus should be roughly 5 V. if it's very different, somethign is wrong.
atommann has joined #qi-hardware
<xiangfu>
VBUS: -0.15v
<wpwrak>
eeew
<wpwrak>
hmm. are you sure you got the right type of conenctor ? :)
<wpwrak>
yours don't look reversed
<wpwrak>
in a reversed connector, the two little slots should be at the bottom
<wpwrak>
not sure if there are reversed connector that have them on the other side
<wpwrak>
are your connectors AB or B ?
<xiangfu>
hmm... -4.5V
<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
<wpwrak>
that looks even more like the wrong connector
<wpwrak>
(reversed = what anelok needs)
<xiangfu>
Yes. wrong connecter...
<wpwrak>
let's hope you have a good electronic shop nearby :)
<wpwrak>
well, at midnight, it may not be open, though. or do you have all night electronics shopping in china ? :)
<xiangfu>
not in Beijing. maybe in Shengzhen.
<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.)
jwhitmore has quit [Ping timeout: 245 seconds]
<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
<xiangfu>
let me try the SWD.
<xiangfu>
what is the command for reflash teh application?
<wpwrak>
first you have to construct a combined binary
<wpwrak>
this should do the trick: dd bs=16k conv=sync if=boot-2014.bin of=combined.bin; cat anelok-2014.bin >>combined.bin
<wpwrak>
then flash with swd combined.bin
<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 :)
<wpwrak>
while ! ./swd combined.bin; do : ; done # then take a tea or a nap ;-)
porchao has joined #qi-hardware
rodgort has quit [Quit: Leaving]
<xiangfu>
a lot of access error
<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 :-(
<xiangfu>
finished one.
<wpwrak>
maybe a fresh pair of eyes will find it in minutes ... ;)
<xiangfu>
successed one of them
rodgort has joined #qi-hardware
<wpwrak>
excellent ! :) now .. swd -r to power and reset anelok
<wpwrak>
and then we'll see if it works :) (i've never tried this mode of operation myself)
rodgort has quit [Ping timeout: 245 seconds]
<wpwrak>
yup, should work. just booted one of mine with ./swd -r
<wpwrak>
ah, but now i have to leave. people trickling in.
<xiangfu>
yes. now I am doing 'while'... :)
<xiangfu>
have to sleep.
rodgort has joined #qi-hardware
jekhor has joined #qi-hardware
atommann has quit [Quit: Leaving]
pcercuei has quit [Ping timeout: 265 seconds]
pcercuei has joined #qi-hardware
jwhitmore has joined #qi-hardware
FDCX has quit [Remote host closed the connection]
FDCX has joined #qi-hardware
jwhitmore has quit [Ping timeout: 252 seconds]
viric has quit [Ping timeout: 264 seconds]
FDCX_ has joined #qi-hardware
viric has joined #qi-hardware
arossdotme has quit [Ping timeout: 264 seconds]
arossdotme has joined #qi-hardware
wolfspraul has joined #qi-hardware
viric has quit [Ping timeout: 245 seconds]
viric has joined #qi-hardware
ChanServ has quit [shutting down]
kilae has quit [Quit: ChatZilla 0.9.91.1 [Firefox 35.0.1/20150122214805]]