Wednesday, 2014-09-03

*** prpplague <prpplague!~prpplague@107-206-64-184.lightspeed.rcsntx.sbcglobal.net> has joined #minnowboard00:04
*** crised <crised!~crised@186.67.181.203> has quit IRC00:21
*** nashi <nashi!~Jaqie@208.53.180.58> has quit IRC00:58
*** Jefro1 <Jefro1!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC01:55
*** nashi <nashi!~Jaqie@208.53.180.66> has joined #minnowboard02:37
*** russell-1 is now known as russell--03:15
*** GPSFan <GPSFan!~kenm@64.92.145.112> has quit IRC03:26
*** aholler_ <aholler_!~aholler@p57B22FB4.dip0.t-ipconnect.de> has joined #minnowboard03:27
*** aholler <aholler!~aholler@p57B22F50.dip0.t-ipconnect.de> has quit IRC03:31
*** inflex <inflex!~PLD@122-148-142-6.static.dsl.dodo.com.au> has quit IRC03:36
*** inflex <inflex!~PLD@122-148-142-6.static.dsl.dodo.com.au> has joined #minnowboard03:39
*** dvhart <dvhart!dvhart@nat/intel/x-ovgtmjjnyawxoknw> has joined #minnowboard04:22
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #minnowboard04:27
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:32
*** sethstorm <sethstorm!zerebah@cpe-184-58-75-33.woh.res.rr.com> has quit IRC04:46
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC05:04
*** jkridner <jkridner!~jkridner@c-98-250-189-79.hsd1.mi.comcast.net> has joined #minnowboard05:05
*** jkridner <jkridner!~jkridner@c-98-250-189-79.hsd1.mi.comcast.net> has quit IRC05:05
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #minnowboard05:05
*** dvhart <dvhart!dvhart@nat/intel/x-ovgtmjjnyawxoknw> has quit IRC05:43
*** dvhart <dvhart!~dvhart@134.134.137.73> has joined #minnowboard05:43
holtmanndvhart: Do you know that the Minnowboard Max firmware has issues with an Apple USB keyboard. It crashes badly.05:47
dvhartholtmann, that's news to me, I've never tried using an Apple keyboard.05:48
holtmannYep. That keyboard does not work. So something is wrong with the HID code in the firmware.05:49
dvhartI'd suggest opening a bug, with specifics on the error observed and the model of the keyboard.05:49
holtmannFunny. That is it.05:49
holtmannI mean nothing else shows up. The screen stays black.05:49
holtmannBooting it without they keyboard lets it boot to the UEFI prompt.05:50
dvhartassuming a non-apple keyboard also works?05:51
holtmannNo idea. I have to go out and buy one.05:52
dvhartHah05:52
holtmannI don't have these lying around anymore.05:52
dvhartwhat if you boot over serial and then add the keyboard, does Linux detect it properly?05:52
dvhartI'm trying to make sure it isn't a problem with your USB port05:52
dvhart(on the max)05:52
holtmannSerial cable is on order since nobody included that in the package.05:53
dvhartright05:53
dvhart:-/05:53
holtmannSame as I have to get some feet for that board. It gets a bit too hot.05:53
dvhartThat is something I miss about minnow 1 - loved the mini USB onboard for the console05:53
holtmannThat part is just silly in my eyes. Some nice serial console and USB gadget is essential.05:54
holtmannThe two things that Android got right are adb and fastboot.05:55
holtmannBoth are just plain nice to have.05:55
thaytanexternal USB hub is worth a try too05:57
dvhartthaytan, good point05:57
holtmannAnd you assume I have these lying around.05:59
thaytanholtmann, lying around? no - I assume you have them in a neatly catalogued box in a pristine lab ;)06:02
dvhartI may have access to a usb mac keyboard in the office06:05
dvhartI'll check in the morning06:05
dvhartall mine are bluetooth06:05
* dvhart crashes - night all06:09
thaytano/06:10
*** dvhart <dvhart!~dvhart@134.134.137.73> has quit IRC06:13
*** aholler_ is now known as aholler07:52
ahollerserials are legazy stuff, just add bluetooth as hw and bluez into the firmware ;)07:52
ahollerI already use a small bt-dongle connected to the serial with most of my "embedded" toys. that works even without bt in toy-firmware ;)07:55
*** macmeck <macmeck!~macmeck@212.172.46.34> has joined #minnowboard07:59
ahollerhttp://ahsoftware.de/bbb_ftdi_bt_rn-42.jpg07:59
ahollerunfortunately the ftdi-connector doesn't have power from the board but for the board :(08:04
*** bluelightning <bluelightning!~paul@83.217.123.106> has joined #minnowboard08:08
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard08:08
ahollernot that I want to name the mbm a toy, I just call most of my embedded stuff such08:18
ahollerbecause, besides making linux-arm-maintainers angry, I have no use for most of them ;)08:19
ahollersorry for the picture with a competitor but I don't have a mb(m) ;)08:29
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard08:30
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC08:30
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:16
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard09:28
*** bluelightning_ is now known as bluelightning09:30
ahollerwhich reminds me that someone should define a SPP for GATT (btle-only SPP). Should be easy to do.09:52
ahollertwo standardized attributes (serial in and serial out) should do the trick09:54
ahollerbesides baudrate and whatever is necessary on the side which connects to some hw-serial09:54
ahollerpatent pending (c) me ;)09:56
ahollermaybe someone could bribe some chipmaker to offer a low-cost serial-btle-chip. I think it would be the really a new star for embedded people.10:04
aholler(and boards)10:04
tbrso what are all the CC2540/2541 modules you can buy doing then? AFAICT they do exactly that.10:04
ahollerno, these are full-featured and not really low-cost10:05
ahollerand you need to fiddle with their firmware10:05
ahollerI just want a btle-chip with 4 wires (tx, rx, gnd, vcc), nothing else necessary to replace the serial with bt on most boards10:06
aholler(at least for low-speed applications like debugging)10:07
tbr< US$ 1.8 in quantity. I'd say this qualifies as low cost.10:08
tbrthere are also other chips by nordic etc which might be even cheaper10:08
ahollerseems to be too much for most board-producers10:08
ahollerand, as said, they would have to fiddle with the firmware. Don't let EE's do that ;)10:10
av500who cares for a few hundred people that are "debugging"10:10
av500to afford making a low cost chip for them10:11
ahollerfor me it would be a buying decision10:11
av500well, talk to TSMC10:11
av500if they can run a wafer for you10:11
aholleri'm not in that business.10:12
av500why do you even care if your debug dongle costs $5 or $15?10:12
ahollerI care for the time I have to spend to connect to the serial with ever changing cables and voltages10:13
ahollerbesides that my usb-ports for usb-2-serial-connectors are limited10:13
ahollernot to speak about the missing serial on todays hw10:14
av500yes, its serial2usb :)10:14
av500not serial2serial10:14
aholleryes, all halfduplex ;)10:14
av500so?10:14
*** macmeck_ <macmeck_!~macmeck@212.172.46.34> has joined #minnowboard10:17
av500http://www.aliexpress.com/item/Free-Shipping-1pc-HM-10-transparent-serial-port-Bluetooth-4-0-module-with-logic-level-translator/1675440638.html10:18
av500there10:18
aholleryou haven't understood10:19
*** macmeck <macmeck!~macmeck@212.172.46.34> has quit IRC10:21
*** macmeck_ is now known as macmeck10:21
ahollertoo complicated. the idea is to have a low-cost, low-power, easy-to-use serial-api for all those iot-people. Most "devs" are able to handle a serial-api, but try to tell them how to use GATT or some other radio-protocol.10:21
av500sure, but still its the same HW10:24
av500BT/LE on one side, uart on the other10:24
av500the rest is SW/firmware10:24
ahollerand that sw is the problem. there should be just a low-cost btle-chip with a serial-connection, like those existing serial-modules they now sell for $10 and more10:26
av500so why not use the above with the right SW?10:27
av500firmware10:28
ahollerno full blown-bt necessary. Assuming btle (and btle-chips) are much more simple to produce than bt10:28
av500yes, there are BLE only chips10:28
av500still they have a little ARM inside that runs the firmware10:28
ahollerbut no gatt-serial-profile10:28
av500thats SW10:28
av500it can be part of the firmware10:28
aholleryou need a standard10:29
av500agree10:29
av500sure10:29
av500that does not mean it has to be mask programmed10:29
ahollerI could have build it myself, if I wouldn't have to register at ti to get their btle-dev-kit. ;)10:29
av500it can still be the above HW or similar10:29
av500register with nordic then :)10:30
ahollersure but no one will add such chip on boards10:30
aholler(instead of a serial)10:30
av500of course not :)10:31
av500imagine having 20 boards running10:31
av500find a BLE stack that handles 20 peripherals10:31
av500good luck10:31
ahollerno problem, just use 3 bt-dongles10:31
av500right, it gets simple and simpler :)10:32
av500+r10:32
ahollerdon't know out of memory how many connections btle does allow10:32
av500and hope that your wifi does not kill the BLE10:33
ahollerI use bt instead of wifi ;)10:33
av500because the debug BLE most likely wont have a coexistence line with the wifi chip10:33
av500the board you want to debug might have wifi10:33
av500or does your standard disallow that?10:34
ahollercan't follow10:34
av500you have a board with wifi10:34
av500you debug over BLE10:34
ahollerdo you want to say wifi and bt(le) can't cooperate?10:34
av500with your $1 chip10:34
av500they cant10:34
av500thats why there are so called coexistance protocolls10:34
av500in a combined wifi/bt chip, its SW10:35
ahollererm10:35
av500for 2 chips, its a signal line that tells the other to shut up10:35
av500of course it works without10:35
av500but you can kill the throughput10:35
ahollerthe whole idea of the fast-switching bt is coexistence10:36
av500yes10:36
av500and there is reality10:36
ahollersure in reality nothing works as promised10:36
ahollerbut at least I don't have problems to use BT, and there is a lot of wifi around here10:37
av500and there is us yelling at IC makers to even get coexistance in their own chip working10:37
av500and now imagine a room full of boards, that you debug10:38
ahollerthat's most likely because the stuff uses the same antenna10:38
av500no10:38
ahollerI have a room full with boards and they all talk bt in an environment full of wifi10:40
av500focus.ti.com/pdfs/vf/bband/coexistence.pdf10:40
av500fig 4-9, 4-1010:40
av500yes, they talk10:40
av500but look at the rates10:40
ahollerI'm talking about low-speed serials, something were 1000c/s are a lot ;)10:41
av500so you want to limit your solution to low speeds?10:41
av500300baud?10:42
av500ok, 120010:42
ahollersure, it's enough for most serials and sensors10:42
av500640k was enough for everybody :)10:43
ahollerI don't think btle is usable with higher speeds10:43
av500it is10:44
ahollerbut I haven't played that much which GATT, just read a sensor-tag ;)10:44
ahollers/-//10:45
ahollerthose pictures do talk about throughoutput in mbps ;)10:47
ahollernot what I have in mind ;)10:48
ahollerbesides that, just move wifi out of the 2ghz-band ;)10:51
ahollerwhat speeds are possible with btle/gatt? I assume with high speeds there isn't much le left10:58
*** RzR is now known as rZr11:00
ahollere.g. my sensortag "just" worked around a month on a coin-cell when reading values every 4 minutes11:01
ahollerbut that's likely because I haven't tuned the bt-params of the host11:02
aholleror at the host. they weren't tunable (I think there are now patches for that available)11:02
*** ka6sox <ka6sox!ka6sox@nasadmin/ka6sox> has quit IRC11:03
*** ka6sox <ka6sox!ka6sox@nasadmin/ka6sox> has joined #minnowboard11:11
ahollerok, to limit the speed while still offering higher baudrates you need 2 cables/pin more (rts/cts).11:19
ahollerassuming no one wants to go back to using xmodem or similiar ;)11:20
*** av500 <av500!~av500@b2b-46-252-131-98.unitymedia.biz> has quit IRC11:27
*** av500 <av500!~av500@b2b-46-252-131-98.unitymedia.biz> has joined #minnowboard11:30
*** ka6sox is now known as zz_ka6sox11:42
*** zz_ka6sox is now known as ka6sox13:23
*** prpplague <prpplague!~prpplague@107-206-64-184.lightspeed.rcsntx.sbcglobal.net> has quit IRC13:25
*** inflex <inflex!~PLD@122-148-142-6.static.dsl.dodo.com.au> has quit IRC13:46
*** dvhart <dvhart!~dvhart@134.134.139.76> has joined #minnowboard14:57
*** prpplague <prpplague!~prpplague@rrcs-97-77-26-26.sw.biz.rr.com> has joined #minnowboard14:59
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard14:59
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:01
macmeckwarthog9: ping15:02
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #minnowboard15:03
*** dvhart <dvhart!~dvhart@134.134.139.76> has quit IRC15:03
prpplaguemacmeck: he might be out on holiday15:07
prpplaguemacmeck: did you have a question?15:07
macmeckprpplague: just wanted to know if there is any update on the max cpu frequency thing we discussed last week15:08
prpplaguemacmeck: i don't think it's been looked into heavily as of yet15:08
macmeckprpplague: i'll get back to him once he's back15:08
prpplaguemacmeck: i've not been able to replicate the issue15:08
macmeckprpplague: okay15:08
prpplaguemacmeck: dvhart is the one you want to ping15:08
macmeckprpplague: okay15:09
macmeckprpplague: thanks15:09
prpplaguemacmeck: dvhart will have more time/expertise to look into it for you15:09
prpplaguemacmeck: have you posted the issue on the mailing list yet?15:09
macmeckprpplague: nope. someone else brought it up, i just realized that i had the same on my board15:10
macmeckprpplague: i'll check the mailing list later15:10
prpplaguemacmeck: if someone can post it on the list, it will be a good way to track the issue15:11
*** bluelightning1 <bluelightning1!~paul@83.217.123.106> has joined #minnowboard15:27
*** bluelightning1 is now known as bluelightning15:27
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard15:27
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:28
*** dvhart <dvhart!~dvhart@134.134.139.76> has joined #minnowboard15:30
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC15:37
*** macmeck <macmeck!~macmeck@212.172.46.34> has quit IRC15:53
*** warthog19 <warthog19!~warthog9@149.20.54.19> has joined #minnowboard16:08
*** ChanServ sets mode: +o warthog1916:08
*** warthog9 <warthog9!~warthog9@149.20.54.19> has quit IRC16:08
*** smurray <smurray!~Scott@69-165-247-13.cable.teksavvy.com> has quit IRC16:08
*** gabrbedd <gabrbedd!~gabrbedd@li680-65.members.linode.com> has quit IRC16:08
*** gabrbedd <gabrbedd!~gabrbedd@li680-65.members.linode.com> has joined #minnowboard16:08
*** warthog19 is now known as warthog916:09
*** smurray <smurray!~Scott@69-165-247-13.cable.teksavvy.com> has joined #minnowboard16:09
*** zenlinux <zenlinux!zenlinux@2600:3c00::f03c:91ff:fedb:c91> has joined #minnowboard16:20
*** Jazzdude <Jazzdude!6dc03c5d@gateway/web/freenode/ip.109.192.60.93> has joined #minnowboard17:11
*** GPSFan <GPSFan!~kenm@64.92.145.112> has joined #minnowboard17:11
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #minnowboard18:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:09
*** dvhart <dvhart!~dvhart@134.134.139.76> has quit IRC18:23
*** dvhart <dvhart!~dvhart@134.134.139.74> has joined #minnowboard19:42
*** yokel <yokel!~yokel@unaffiliated/contempt> has quit IRC19:44
*** yokel <yokel!~yokel@unaffiliated/contempt> has joined #minnowboard19:49
*** sjolley <sjolley!~sjolley@134.134.139.70> has joined #minnowboard19:52
*** aholler <aholler!~aholler@p57B22FB4.dip0.t-ipconnect.de> has quit IRC19:56
*** jaqiefox <jaqiefox!~Jaqie@75-170-92-228.eugn.qwest.net> has joined #minnowboard20:24
*** nashi <nashi!~Jaqie@208.53.180.66> has quit IRC20:27
*** jaqie_fox <jaqie_fox!~Jaqie@75-170-92-37.eugn.qwest.net> has joined #minnowboard20:27
*** jaqiefox <jaqiefox!~Jaqie@75-170-92-228.eugn.qwest.net> has quit IRC20:30
*** nashi <nashi!~Jaqie@75-170-93-147.eugn.qwest.net> has joined #minnowboard20:31
*** jaqie_fox <jaqie_fox!~Jaqie@75-170-92-37.eugn.qwest.net> has quit IRC20:34
*** aholler <aholler!~aholler@p57B22FB4.dip0.t-ipconnect.de> has joined #minnowboard21:24
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC21:27
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #minnowboard21:28
*** dvhart <dvhart!~dvhart@134.134.139.74> has quit IRC21:33
*** inflex <inflex!~PLD@122-148-142-6.static.dsl.dodo.com.au> has joined #minnowboard22:28
*** Jazzdude <Jazzdude!6dc03c5d@gateway/web/freenode/ip.109.192.60.93> has quit IRC22:31
*** dvhart <dvhart!dvhart@nat/intel/x-fzducuvdgysbzeju> has joined #minnowboard23:01
*** prpplague <prpplague!~prpplague@rrcs-97-77-26-26.sw.biz.rr.com> has quit IRC23:06
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #minnowboard23:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard23:21
*** mmetzger <mmetzger!~mmetzger@99-71-214-107.lightspeed.mdldtx.sbcglobal.net> has quit IRC23:21

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!