**** BEGIN LOGGING AT Thu May 04 03:00:03 2017
May 04 06:19:52 <JohnPIA> Hi all.
May 04 10:33:08 <Christ3> Hi guys, has anyone used the beaglebone black with the CS-BBB-EXP43 touch screen?
May 04 10:37:26 <professore> hi
May 04 10:39:25 <professore> please, is it possible to bootstrap the beagleboard from the wifi?
May 04 11:57:39 <JohnPIA> Hello... Ive a question: my service(.sh) stops a while(1) loop sometimes. Systemctl shows 0: Succes
May 04 11:58:02 <JohnPIA> But I don't exit the whileloop anywhere... c.q.: is shouldnt be able to stop with return 0
May 04 11:58:37 <JohnPIA> Can I somewhere see why it stops the while (main) loop?
May 04 12:42:51 <tuukka> Hello, I'm trying to get openSUSE working on Beagle Bone Black Wireless. Already upgraded to kernel 4.6.11 and should have correct firmwares and stuff.
May 04 12:43:39 <tuukka> If I just copy wl18xx-conf.bin to firmwares from Beagle Board it doesn't find Wlan with wl18xx and wlcore.
May 04 12:44:03 <tuukka> Does anyone have it working outside Beagle Bone Black own image?
May 04 13:51:55 <matthewburton> I've done some searching for this answer but haven't found anything concrete: is there a generally accepted MTBF for BB Black? I recognize this will vary by application, but perhaps some of the components of the board have published MTBFs...
May 04 14:17:22 <raffo> hello, for those of you using the TI AM572x EVM. Have you been able to boot it from an SSD drive? I've installed the os image on one of these drives, but the board fails to boot from it.
May 04 14:22:11 <raffo> all I get is:U-Boot SPL 2017.01-00302-gafb742e245-dirty (May 03 2017 - 14:09:51)
May 04 14:22:12 <raffo> DRA752-GP ES1.1
May 04 14:22:12 <raffo> SPL: Unsupported Boot Device!
May 04 14:22:12 <raffo> SPL: failed to boot from all boot devices
May 04 14:22:12 <raffo> ### ERROR ### Please RESET the board ###
May 04 15:37:05 <zmatt> your SPL clearly hasn't been built with sata support
May 04 15:40:59 <zmatt> matthewburton: the AM335x SoC is rated for 100K power-on hours (for all clock speeds, junction temperature up to 90 degrees celsius)
May 04 15:41:20 <zmatt> matthewburton: I've never seen any such info for other components
May 04 15:43:44 <zmatt> matthewburton: eMMC retention and wear-out is probably also something to watch out for
May 04 15:46:10 <matthewburton>  thanks
May 04 15:48:07 <winter-muted> hi, im having trouble using the PRU. can anyone help me with that?
May 04 15:48:19 <zmatt> if long-term reliability is important, an option to consider is reconfiguring the eMMC to be SLC instead of MLC.  this should significantly increase retention and wearout-resistance
May 04 15:49:46 <zmatt> winter-muted: my guess would be that noone can help you unless you actually say what the problem is :)
May 04 15:50:39 <winter-muted> ok! well ive looked at quite a few tutorials online, and they all seem to be from a few years ago.  at least on my bbb, which can with the 4.4 kernel, the device tree overlay step doesnt work
May 04 15:50:46 <winter-muted> came*
May 04 15:51:23 <zmatt> I have to admit I've lost track of what the defaults are nowadays
May 04 15:51:44 <raffo> zmatt: the u-boot I'm using was built following RCN's instructions. I'm not familiar enough w u-boot to enable sata support if such a thing exists.
May 04 15:52:06 <zmatt> winter-muted: for some time at least neither uio-pruss nor remoteproc-pru was enabled by default, but enabling uio-pruss was a simple matter of inserting the appropriate overlay
May 04 15:52:30 <winter-muted> i went to the bb.org-overlays githup and built the 4.9-ti kernel with realtime support...then i decompiled? the overlay and it told me the pru was "okay"
May 04 15:53:00 <zmatt> why an -rt kernel?
May 04 15:53:19 <winter-muted> my thought was that the -rt bit meant add the pru device?
May 04 15:53:22 <zmatt> no
May 04 15:53:25 <winter-muted> mhmm
May 04 15:53:31 <zmatt> it has absolutely nothing to do with pru
May 04 15:53:37 <winter-muted> ah, real time linux then
May 04 15:53:57 <zmatt> yeah, which is only useful if you have software that specifically makes use of that
May 04 15:54:13 <zmatt> (and otherwise is just less efficient and potentially buggier)
May 04 15:54:30 <winter-muted> got it. so do you think there is a default overlay from the curret IOT jessie build that i can load?
May 04 15:54:59 <zmatt> I see several overlays with pru in the name
May 04 15:55:07 <zmatt> are you trying to get uio-pruss to work or remoteproc-pru ?
May 04 15:55:31 <winter-muted> uhh, all i really wanna do is blink an external led with the pru over gpio, so i guess the uio_pruss bit?
May 04 15:56:01 <zmatt> that's a description of what you're trying to do, not how you're trying to do it :)
May 04 15:56:08 <zmatt> they're different mechanisms for loading pru programs
May 04 15:56:42 <winter-muted> mhmm. i havent heard of remoteproc-pru yet
May 04 15:59:07 <zmatt> lemme check how things are being configured in the main dt in current 4.9 kernels
May 04 15:59:44 <zmatt> (I use my own DT so I don't bother keeping track of defaults)
May 04 16:03:35 <zmatt> looks like both 4.9.26-bone4 and 4.9.25-ti-r32 enable remoteproc-pru by default
May 04 16:03:43 <winter-muted> hmm
May 04 16:03:54 <ver|laptop> zmatt: at least you know what you're looking at ;)
May 04 16:03:58 <zmatt> if you disable that however you could enable uio-pruss with this overlay https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/AM335X-PRU-UIO-00A0.dts
May 04 16:04:19 <winter-muted> so that means the firmware driver is loaded, right? and then i have to map it with an overlay?
May 04 16:04:53 <zmatt> both remoteproc-pru and uio-pruss are built as kernel modules, so the kernel will load the correct one depending on DT
May 04 16:06:28 <zmatt> you can either use an overlay or just patch up the main DT
May 04 16:06:43 <winter-muted> sorry, what does DT stand for?
May 04 16:06:45 <zmatt> since you need to patch up the main DT anyway to disable remoteproc-pru, you might as well enable uio-pruss at the same time
May 04 16:06:48 <zmatt> device tree
May 04 16:06:50 <winter-muted> ahh
May 04 16:07:32 <winter-muted> ok ill try that for a bit her
May 04 16:07:33 <winter-muted> here
May 04 16:07:46 <winter-muted> thanks!
May 04 16:08:49 <zmatt> maybe I should make an example of how to use pru with just uio_pdrv_genirq or /dev/mem ;)
May 04 16:09:03 <zmatt> saves on driver headache
May 04 16:09:15 <ver|laptop> zmatt: doo eet :D
May 04 16:09:21 <winter-muted> it seems most of the tutorials online are from 2014 or 13
May 04 16:09:40 <zmatt> i.e. ancient history
May 04 16:09:42 <ver|laptop> yes, the tutorials really don't keep pace with development :/
May 04 16:09:49 <winter-muted> ^^basically
May 04 16:09:56 <ver|laptop> there is a lack of beaglebone documentation project :/
May 04 16:10:21 <winter-muted> i just got my board, it seems like a really capable part
May 04 16:10:29 <ver|laptop> which is a crying shame imho, since the board is really capable
May 04 16:10:40 <zmatt> note that uio_pruss is unnecessarily crappy, but its advantage over plain uio_pdrv_genirq is that you can reserve a chunk of DDR3 memory for use by pru (or any other purpose)
May 04 16:10:42 <ver|laptop> much more so (graphics excepting) than the R-Pi
May 04 16:11:21 <ver|laptop> but then both are very different Applications Processors :)
May 04 16:11:29 <zmatt> indeed
May 04 16:12:10 <zmatt> well, later pies also have a cpu performance advantage I'd presum,e
May 04 16:12:17 <winter-muted> i heard of a guy writing a neural network library for the RPi's gpu. any such thing been done for the bb?
May 04 16:12:51 <zmatt> RPi's "gpu" is just a processor for which you can write arbitrary code
May 04 16:13:17 <zmatt> (it's actually the boot cpu, the ARM processor is brought up as auxiliary)
May 04 16:13:31 <winter-muted> oh yea, i remember reading that
May 04 16:14:16 <raffo> zmatt: after grepping and google searching I got it to compile with SPL "sata support", finds the device, but fails to initialize it and boot. Oh well.
May 04 16:14:17 <zmatt> the gpu on the am335x is a dedicated gpu, and there's currently no way to use it except through openGL ES / ES2
May 04 16:14:55 <zmatt> raffo: sounds like it might need some... fine tuning ;-)
May 04 16:15:04 <luneff> is there a way to deal with sound playback delay with ALSA/BBB/HDMI? It seems that actual audio comes after a bit of delay so not the whole file is played :-(
May 04 16:15:04 <winter-muted> my prof told me that in the old days, some guys implemented some RNN's in opengl.  what a bear...
May 04 16:15:20 <ver|laptop> we have opencl these days ... :D
May 04 16:15:28 <zmatt> not on am335x though
May 04 16:15:36 <zmatt> unless I missed something
May 04 16:15:45 <ver|laptop> no, only only on certain gpu arches irc
May 04 16:15:48 <ver|laptop> iirc8
May 04 16:16:01 <zmatt> not on any gpu used by TI afaik
May 04 16:16:30 <zmatt> they do support opencl to use the DSPs on vayu
May 04 16:16:35 <ver|laptop> I think the talk may have been with vivante on the imx's .. sure rcn was talking about mining on something lol
May 04 16:17:11 <zmatt> winter-muted: oh you can probably abuse it for some general-purpose computation
May 04 16:17:12 <ver|laptop> probably his arm cluster :D
May 04 16:17:26 <zmatt> winter-muted: I mean, a shader program is still a program
May 04 16:18:03 <winter-muted> yea. these small boards have some cool applications for machine vision
May 04 16:18:16 <winter-muted> but gpus are nice for that
May 04 16:18:54 <zmatt> the NEON engine on the cortex-a8 is also not too bad for code that's optimized for it
May 04 16:21:26 <zmatt> but the am335x is not really a number cruncher, it's much more at home in real-time / low-latency :)
May 04 16:21:50 <ver|laptop> ^ in the pru capacity anyway :)
May 04 16:22:06 <zmatt> yes
May 04 16:22:14 <winter-muted> heh. i suppose if you have network, you can farm out some things anyway
May 04 16:22:18 <ver|laptop> one of these days I *will* write a pru app .. or find something easy to download
May 04 16:22:31 <winter-muted> its challenging!
May 04 16:23:05 <ver|laptop> since my first forays into microcontroller assembly programming it really can't be hard .. :D
May 04 16:23:20 <zmatt> pru has a nice instruction set
May 04 16:23:28 <ver|laptop> zmatt: how many instructions roughly?
May 04 16:23:50 <ver|laptop> I like the ~30-60 range :D
May 04 16:24:10 <ver|laptop> I assume its RISC
May 04 16:24:20 <ver|laptop> or something comparable
May 04 16:24:27 <zmatt> heh, does it even reach 30 ? lemme check
May 04 16:24:41 * ver|laptop started out with PIC's
May 04 16:25:06 <ver|laptop> I never liked their architecture though... give me AVR over PIC any day
May 04 16:27:06 <zmatt> not sure where to draw the line between instructions... e.g. are branch if left-than and branch if greater-than different instructions or different forms of one instruction?
May 04 16:27:38 <ver|laptop> ah yes .. 10 different variants of branch :D
May 04 16:27:54 <ver|laptop> usually they become separate .. depends on the opcode though ..
May 04 16:28:54 <ver|laptop> s/left/less/ :)
May 04 16:29:51 <ver|laptop> bit-test-file-skip-if-zero and -one were PIC favourites :D
May 04 16:30:05 <zmatt> https://pastebin.com/raw/2L73r7E3
May 04 16:30:17 <ver|laptop> or btfss/-sc in mnemonics
May 04 16:30:41 <zmatt> mvi is crazy
May 04 16:30:54 <zmatt> it lets you perform a register-indexed move within the register file
May 04 16:32:03 <ver|laptop> neat
May 04 16:32:20 <zmatt> its coprocessor bus is also... interesting
May 04 16:32:25 <zmatt> also known as the broadside bus
May 04 16:32:35 <zmatt> since they wired out the whole register set
May 04 16:32:44 <ver|laptop> slightly risky though lol
May 04 16:33:07 <zmatt> you can save/restore/swap any contiguous byterange of the general-purpose registers to/from one of the three "scratchpads"
May 04 16:33:10 <zmatt> in 1 cycle
May 04 16:33:21 <ver|laptop> :
May 04 16:33:23 <ver|laptop> :D
May 04 16:33:54 <zmatt> those are shared between the two cores, hence usable for fast handoff of data from one core to the other
May 04 16:34:43 <ver|laptop> ideal!
May 04 16:34:50 <zmatt> it can also do a rendezvous between the two cores, where one will wait in the xin/xout until the other has reached it too so they can transfer directly from core to core
May 04 16:34:54 <ver|laptop> yea that instruction set is .. compact!
May 04 16:35:18 <zmatt> the alu is all of the form  reg, reg, reg|uimm8
May 04 16:35:43 <zmatt> where reg is a 32-bit register, or one of the three 16-bit subfields, or one of the four 8-bit subfields
May 04 16:36:14 <ver|laptop> three 16-bit subfields?
May 04 16:36:23 <zmatt> yeah, middle subfield too :)
May 04 16:36:30 <ver|laptop> mental...
May 04 16:37:53 <zmatt> load/store instructions are even more liberal, they treat the whole register file as one contiguous byte-array
May 04 16:38:44 <zmatt> all alu stuff is unsigned btw
May 04 16:38:53 <zmatt> there's no support for signed compare
May 04 16:39:15 <zmatt> for multiplication there's a coprocessor
May 04 16:40:58 <zmatt> limited mostly by data movement: you need to get the (32-bit) arguments into specific registers, and then XIN the 64-bit result into another set of specific registers
May 04 16:43:35 <zmatt> so yeah they're fun... I'm a bit surprised you've never taken a look :)
May 04 16:43:39 <ver|laptop> eh if you're doing a lot of multiply/divide and not shifts .. well ..
May 04 16:44:08 <ver|laptop> zmatt: too much other .. "crap" .. :/ but yeah one day .. I bought a 'spare' BBB to 'play' with ;)
May 04 16:44:27 <zmatt> and of course gpio wired into registers is also a nice perk
May 04 16:44:32 <ver|laptop> gotta finish the imx6 stuff first :/ and then someone convinced me (uh, self) to get a Pi0W .. heh.
May 04 16:44:49 <zmatt> a pi0w ? why?
May 04 16:45:22 <ver|laptop> why not :p
May 04 16:45:30 <zmatt> *shrug*
May 04 16:45:34 <ver|laptop> its cheap and tiny!
May 04 16:45:36 <ver|laptop> and wireless
May 04 16:45:44 <ver|laptop> bluetooth too
May 04 16:46:04 <zmatt> a piece of gum is also cheap, tiny, and wireless
May 04 16:46:15 <ver|laptop> ubt yeah .. find me a good IO rich project .. I'll be back on that BBB ..
May 04 16:46:19 <ver|laptop> but*
May 04 16:46:44 <zmatt> I tested the pru gpio latency by just filling instruction memory with a move instruction from gpi to gpo
May 04 16:46:46 <ver|laptop> the imx project may find itself on a Pi0W
May 04 16:46:55 <ver|laptop> lol cool
May 04 16:47:00 <zmatt> then a clock signal on the gpi and compare with the gpo on a scope
May 04 16:47:23 <zmatt> iirc around 25ns-30ns
May 04 16:47:46 <ver|laptop> thats what .. a few hundred khz?
May 04 16:48:46 <ver|laptop> adequate for bit-banging i2c LOL
May 04 16:51:22 <zmatt> eh, you're off a few orders of magnitude
May 04 16:51:51 <ver|laptop> bugger...
May 04 16:51:52 <ver|laptop> lol
May 04 16:52:40 <zmatt> also this is in->out latency, it can bitbang much faster (up to a 100 MHz in bursts)
May 04 16:53:08 <zmatt> although I guess if you need to read back for i2c then the values I measured might be relevant
May 04 16:54:22 <zmatt> add a few instructions for actual work... maybe it could do 20 MHz i2c or so, hard to say
May 04 16:55:22 <zmatt> there's also a 100 Msps logic analyzer made with pru
May 04 16:56:25 <zmatt> where probably the biggest problem was "how do we offload that much data?" :D
May 04 16:58:17 <ver|laptop> lol yes...
May 04 16:59:01 <zmatt> it occurred to me it would be neat to implement complex triggers by generating pru code
May 04 16:59:46 <ver|laptop> you could
May 04 17:08:46 <zmatt> one thing that annoys me though is that they use "word" and "dword" to mean 16-bit and 32-bit, even though PRU is a 32-bit processor with no 16-bit heritage
May 04 17:26:51 <ver|laptop> ah like 'how big is an int' lol
May 04 17:26:59 <ver|laptop> always worth double-checking
May 04 17:41:09 <zmatt> an int (in the pru C compiler) is 32-bit of course
May 04 17:46:55 <ver|laptop> :)
May 04 17:47:35 <zmatt> the pru C compiler is crap btw ;)  not really a huge surprise
May 04 17:50:30 <ver|laptop> I think I can handle 20-odd instructions XD
May 04 17:59:52 <Raki_> I just want to know which can give better sampling rate?
May 04 18:00:36 <Raki_> *which beagle board has better sampling rate for ADC?
May 04 18:03:16 <zmatt> which ones are you trying to compare?
May 04 18:04:43 <zmatt> I'm not sure any of the beagleboards even have an ADC.  The beaglebones do however
May 04 18:04:55 <Raki_> beaglebard-xM and beaglebone black
May 04 18:05:07 <zmatt> I'm not familiar with the capabilities of the xM
May 04 18:06:52 <zmatt> apparently the xM only has an ADC integrated in the PMIC, with one general-purpose analog input available on the expansion header
May 04 18:06:54 <Raki_> which board do you suggest me? if i would do an experiment to take input from a pressure sensor onto board
May 04 18:08:20 <zmatt> the beaglebone is cheap and available, I'm not sure the xM is even being produced anymore
May 04 18:09:24 <Raki_> there are blue black beaglebone is that just a difference of color or any better features ?
May 04 18:09:35 <zmatt> they are quite different
May 04 18:11:22 <zmatt> I mean, all beaglebones are based on the AM3358 SoC from TI, but they differ in I/O and connectivity
May 04 18:52:33 <ds2> zmatt: hehe... that caused a complete rewrite of my first firmware :(
May 04 18:52:45 <zmatt> ds2: hmm?
May 04 18:52:56 <zmatt> what did?
May 04 19:04:47 <ds2> the whole definition of a word on the PRU
May 04 19:08:36 <zmatt> how did that end up requiring a rewrite?  it's just an annoying bit of terminology
May 04 19:24:30 <beginner> Hello, I'm beginner on BBB. But I've bought my board 3 years ago. And It's A5C version.
May 04 19:25:04 <beginner> now I'm trying to boot from microSD with one of latest images
May 04 19:25:14 <beginner> but I can't reach to my BBB over 192.168.7.2
May 04 19:27:40 <beginner> I'm using bone-debian-8.7-lxqt-2gb-armhf-2017-04-30-2gb.img.xz image
May 04 19:48:53 <MathOnNapkins> beginner: Assuming you're using Windows, did you install the drivers? (it should at least show up as a drive, and the additional drivers to make it show up as a network device are on that drive, aka mass storage device)
May 04 19:49:59 <beginner> MathOnNapkins: no, i'm using both windows and zorinOS
May 04 19:50:12 <beginner> and I've already installed drivers for windows
May 04 19:56:42 <zmatt> don't send private messages
May 04 19:57:06 <zmatt> MathOnNapkins: drivers should actually not be required anymore on latest images
May 04 19:57:24 <zmatt> beginner: does it seem to boot normally? does it appear as network interface?
May 04 19:59:09 <beginner> zmatt: yes boot seems to completed normally
May 04 20:00:25 <beginner> actually I'm not sure
May 04 20:03:15 <zmatt> try 192.168.6.2 and beaglebone.local in addition to 192.168.7.2
May 04 20:04:22 <zmatt> normally a new network interface should show up conspicuously though, in any OS afaik
May 04 20:05:13 <beginner> to boot from microSD, should i press boot button during power on?
May 04 20:07:48 <zmatt> normally not required, but if you have doubts it can be useful to force boot from microSD
May 04 20:08:00 <zmatt> e.g. if the bootloader on eMMC is ancient
May 04 20:08:57 <beginner> I don't want to flash from SD to eMMC at the moment.
May 04 20:09:18 <beginner> I want to boot from microSD and see to run.
May 04 20:09:45 <zmatt> normally the ROM bootloader prefers to load u-boot from eMMC, only falling back to uSD if eMMC is completely unbootable.  However u-boot prefers to load linux from uSD (if it detects a bootable system on it) over eMMC
May 04 20:10:21 <zmatt> holding down the S2 button during power-on removes eMMC from the boot order, so ROM will load u-boot from uSD
May 04 20:10:59 <beginner> ok also when I unmount my microSD on linux system
May 04 20:11:00 <zmatt> so that's mainly useful if the u-boot on eMMC is broken, or too ancient to successfully load a recent linux system
May 04 20:11:18 <beginner> I only see rootfs
May 04 20:11:36 <zmatt> there's normally only 1 partition
May 04 20:11:50 <beginner> and when I open with disks there are two partition
May 04 20:11:56 <beginner> 4.2mb Free Space
May 04 20:12:07 <beginner> at /dev/sdc
May 04 20:12:25 <beginner> and 1.8GB rootfs at /dev/sdc1
May 04 20:12:30 <beginner> and it's bootable
May 04 20:12:38 <beginner> is it a right configuration?
May 04 20:13:05 <zmatt> uh, what you've pasted says there's one partition, not two
May 04 20:13:26 <zmatt> (which is correct)
May 04 20:13:32 <beginner> yes the freespace can't be unmounted
May 04 20:13:42 <beginner> because it's empty and not formatted
May 04 20:14:06 <zmatt> that "free" space actually isn't free, it's where u-boot resides
May 04 20:14:40 <beginner> I don't think so, it's empty :S
May 04 20:14:50 <beginner> I can't unmount it
May 04 20:14:50 <zmatt> trust me, it's where u-boot resides
May 04 20:15:00 <beginner> ok :)
May 04 20:15:01 <zmatt> you mean "mount", unmount is the opposite thereof
May 04 20:15:07 <zmatt> you can only mount a filesystem
May 04 20:15:10 <zmatt> there isn't one there
May 04 20:15:26 <beginner> hmm..
May 04 20:15:49 <beginner> ok, you convince me
May 04 20:16:07 <beginner> now I'm trying with holding down the s2 button
May 04 20:16:52 <beginner> I released button when all LEDs are light up
May 04 20:16:59 <beginner> now some LEDs are flashing
May 04 20:17:04 <zmatt> you can release it when any led lights up
May 04 20:17:33 <beginner> LED 0 and 1 are flashing
May 04 20:17:35 <zmatt> or, well, you need to hold it a few ms after the power led turns on
May 04 20:17:41 <zmatt> that sounds like booting
May 04 20:17:58 <beginner> when the booting process will be completed
May 04 20:18:06 <beginner> or how will I understand it
May 04 20:18:24 <zmatt> when it looks reasonably calm apart from led 0 flashing in a "heartbeat" pattern
May 04 20:18:38 <beginner> yes
May 04 20:18:42 <beginner> now it looks like that
May 04 20:18:55 <beginner> led 0 is flashing in a hearbeat pattern
May 04 20:19:07 <zmatt> yeah it'll do that pretty much from the start
May 04 20:19:35 <zmatt> led 0 is heartbeat, led 1 is uSD access, led 2 is cpu activity, led 3 is eMMC access
May 04 20:19:51 <zmatt> (by default)
May 04 20:20:07 <beginner> it's a very usefull info :) thanks again
May 04 20:20:16 <beginner> now can I try to reach to my board?
May 04 20:21:07 <zmatt> the easiest criterion is still: did it show up as network interface? (assuming it's connected to your computer via usb)
May 04 20:22:01 <beginner> hm.. it's a good question.
May 04 20:22:17 <beginner> and it's connected to my computer via usb, you're right
May 04 20:22:33 <zmatt> normally there's somewhere where you can see your network interfaces and also query the ip address being used
May 04 20:23:11 <beginner> can i check it via nmap
May 04 20:23:12 <beginner> ?
May 04 20:23:54 <zmatt> if you're on linux just use "ip -4 addr"
May 04 20:24:50 <zmatt> on windows it should show up among these -> https://restingsysadmin.files.wordpress.com/2013/03/networkconnections1.png
May 04 20:25:20 <beginner> yes I'm on linux at the moment
May 04 20:25:26 <beginner> and I run this command
May 04 20:26:49 <beginner> it showed me two interface
May 04 20:27:03 <beginner> they are lo and wlan0
May 04 20:27:41 <zmatt> then it's not showing up
May 04 20:28:01 <beginner> yes
May 04 20:28:18 <beginner> how can i configure it?
May 04 20:28:40 <zmatt> there's nothing to configure if it's not showing up
May 04 20:28:54 <zmatt> hard to diagnose though without something like a debug serial cable
May 04 20:29:15 <zmatt> you could try checking the kernel log to see if it showed up as any sort of usb device at all
May 04 20:29:28 <zmatt> or try flashing a different image to sd
May 04 20:29:30 <zmatt> dunno
May 04 20:30:14 <beginner> can I use 4GB images with my bbb version
May 04 20:30:24 <beginner> I won't write to eMMC
May 04 20:30:31 <beginner> I'll use it over uSD
May 04 20:30:55 <beginner> also I've a serial cable
May 04 20:30:58 <zmatt> if it fits on your uSD card then sure
May 04 20:31:10 <zmatt> just be sure to download a "standalone" image and not a "flasher" image
May 04 20:31:26 <beginner> if you can assit me for debug with serial cable
May 04 20:31:33 <beginner> it can be intersting for me
May 04 20:31:41 <beginner> and I can learn a lot of thing
May 04 20:31:50 <zmatt> not now really, I kinda have to go
May 04 20:32:04 <beginner> it's a very bad new for me
May 04 20:32:09 <beginner> thanks for your support
May 04 20:32:12 <beginner> and everything
May 04 20:32:15 <beginner> till now
May 04 23:22:49 <ds2> zmatt: I was manipulating specific number of bits and using instructions that refer to it
**** ENDING LOGGING AT Fri May 05 03:00:01 2017