**** BEGIN LOGGING AT Mon Jul 04 02:59:58 2016
Jul 04 06:54:02 <Adit> I bought a BBB
Jul 04 06:54:11 <Adit> and its not recognizable via USB
Jul 04 06:54:24 <Adit> It shows Network cable unplugged
Jul 04 06:54:40 <Adit> Although it boots up and USR lights blew up
Jul 04 06:57:00 <Adit_> [08:54] <Adit> I bought a BBB [08:54] <Adit> and its not recognizable via USB [08:54] <Adit> It shows Network cable unplugged [08:54] <Adit> Although it boots up and USR lights blew up
Jul 04 06:58:18 <Adit> Can somebody help me
Jul 04 07:05:46 <tbr> Adit: which operating system are you using on yourPC?
Jul 04 08:05:36 <Adit_> I am using Win7
Jul 04 08:11:23 <dirkk> Hi
Jul 04 08:11:34 <dirkk> did you install drivers ?
Jul 04 08:15:11 <tbr> duh
Jul 04 08:16:09 <dirkk> ?
Jul 04 08:20:09 <dirkk> Why I don't have BB-BONE-PRU-01 in /lib/firmware/ ?  (bbb 4.7.0-rc2-bone0)
Jul 04 08:24:09 <Adit> My BBB dosent detect USB over Ethernet connection
Jul 04 08:24:43 <Adit> LAN says Network cable Unplugged
Jul 04 08:24:50 <Adit> I tried with other USB cable too
Jul 04 08:24:54 <Adit> Still the same error
Jul 04 08:25:10 <Adit> Although BBB boots up properly
Jul 04 08:25:17 <Adit> USR  lights blow up
Jul 04 08:26:42 <Adit> I am using Windows 7 Pro
Jul 04 08:26:44 <Adit> OS
Jul 04 08:36:27 <dirkk> tbr: still here ?
Jul 04 08:37:08 <tbr> dirkk: huh?
Jul 04 08:38:01 <dirkk> tbr: did you use/activate the pru of the bbb ?
Jul 04 08:38:07 <tbr> no
Jul 04 08:38:16 <dirkk> ok
Jul 04 08:38:55 <tbr> but there is a difference between the pru mechanisms on 3.8 and >4
Jul 04 08:39:03 <tbr> so you'll have to figure that out
Jul 04 08:39:48 <zmatt> 4.x-bone have uio_pruss just like 3.8
Jul 04 08:39:54 <zmatt> it's 4.x-ti that has remoteproc
Jul 04 08:40:17 <tbr> ah
Jul 04 08:40:21 <Texas> Can anyone telll why USB over Ethernet connection dosent work
Jul 04 08:40:29 <Texas> even though USB is cxonnected
Jul 04 08:40:38 <dirkk> Texas = Adit ;)
Jul 04 08:40:39 <tbr> do the leds on the BBB blink?
Jul 04 08:40:45 <Texas> haha
Jul 04 08:40:47 <Texas> yes
Jul 04 08:41:02 <Texas> It blinks
Jul 04 08:41:52 <tbr> and you installed the drivers?
Jul 04 08:41:55 <Texas> yes
Jul 04 08:41:58 <Texas> ofcourse
Jul 04 08:42:13 <tbr> does device manager show the added network interface/card?
Jul 04 08:43:15 <dirkk> zmatt: Hi, I changed for bone kernel. I see uio_pruss by lsmod. I use dtsi for enable pru and pins -> error.
Jul 04 08:43:40 <Texas> yes
Jul 04 08:43:46 <Texas> it shows it works properlz
Jul 04 08:43:50 <Texas> properly
Jul 04 08:43:53 <dirkk> zmatt: Then, I try to use a dtbo in /lib/firmware but see noting like BB-BONE-PRU-*
Jul 04 08:45:01 <zmatt> do you have cape-universal loaded?  since that's often the default on new images but it sucks and conflicts with just about every other overlay
Jul 04 08:45:20 <zmatt> I have no idea what normally populates those dtbos in /lib/firmware, I've never used them
Jul 04 08:45:35 <dirkk> zmatt: cat .../slots -> nothing
Jul 04 08:45:47 <tbr> Texas: go to network settings, is the interface active?
Jul 04 08:51:40 <dirkk> zmatt: http://pastebin.com/JirZ9qDQ  /boot/uEnv.txt there are 2 lines for HDMI should I uncomment the second one ?
Jul 04 08:52:37 <zmatt> no the one you uncommented is the correct one
Jul 04 08:52:46 <zmatt> the others ones also disable eMMC
Jul 04 08:53:21 <dirkk> zmatt: what about l. 46 47
Jul 04 08:53:33 <zmatt> the ones labeled (v3.8.x) you mean
Jul 04 08:53:36 <zmatt> :P
Jul 04 08:53:38 <dirkk> yep
Jul 04 08:53:44 <zmatt> guess what kernel version those are for
Jul 04 08:54:24 <zmatt> :)
Jul 04 08:55:02 <dirkk> ok ok, I'm checking everything because I'm clueless
Jul 04 08:55:05 <dirkk> ;)
Jul 04 08:55:06 <zmatt> they're not used for 4.x, it uses dtb selection for enabling/disabling hdmi
Jul 04 08:56:20 <zmatt> I'll see if I can gather some motivation to check how to write a dtsi for uio_pruss
Jul 04 08:56:58 <zmatt> I've done a few experiments with pru already but I just used uio_pdrv_genirq and some custom userspace code
Jul 04 08:58:04 <dirkk> ok but I tried with this http://pastebin.com/T1fuDhEq
Jul 04 08:58:14 <dirkk> it's not correct ?
Jul 04 08:58:46 <zmatt> looks okay at first sight, but I don't know what requirements uio_pruss has
Jul 04 08:58:53 <zmatt> what error did you get?
Jul 04 08:59:48 <dirkk> still the same: when I do : ./myprog ./asmoutput.bin
Jul 04 09:00:02 <dirkk> prussdrv open () failed
Jul 04 09:00:48 <zmatt> did you check kernel log?
Jul 04 09:02:58 <dirkk> try /var/log/kern.log don't know where to look ?
Jul 04 09:03:10 <zmatt> dmesg
Jul 04 09:03:17 <zmatt> or journalctl -k
Jul 04 09:03:49 <zmatt> or indeed /var/log/kern.log if you have rsyslog installed (it is by default, I always remove it)
Jul 04 09:05:08 <dirkk> http://pastebin.com/D2ZiZwnB  rproc handle ?
Jul 04 09:05:42 <zmatt> "pruss_uio 4a300000.pruss: No children"
Jul 04 09:05:45 <zmatt> what a helpful error message
Jul 04 09:06:25 <zmatt> so I'm guessing it's expecting some child node(s)
Jul 04 09:07:08 <dirkk> maybe this is why I don't see the dtbo in firmware ?
Jul 04 09:09:26 <zmatt> that remark makes absolutely no sense
Jul 04 09:10:37 <zmatt> ok, the driver indeed expect child nodes
Jul 04 09:10:53 <zmatt> not really clear to me why
Jul 04 09:11:53 <zmatt> apparently whoever wrote that driver seems to think you can't make use of pruss without also using some gpios, or something
Jul 04 09:11:56 <dirkk> ko, for me  part_number 'BB-BONE-PRU-01', version 'N/A' is missing
Jul 04 09:13:00 <dirkk> L 187 remoteproc ?
Jul 04 09:13:03 <zmatt> lovely, the uio pruss driver also has no devicetree binding documentation -.-
Jul 04 09:13:23 <zmatt> are you now just typing random things?
Jul 04 09:13:46 <zmatt> ah that's what you mean
Jul 04 09:13:52 <zmatt> that's remoteproc for the wakeup_m3
Jul 04 09:13:57 <zmatt> not related to pru
Jul 04 09:14:52 <dirkk> I was suprised by the red lines 187 with remoteproc because I change version to not use it
Jul 04 09:15:13 <zmatt> this has nothing to do with pru
Jul 04 09:15:17 <dirkk> ok
Jul 04 09:15:28 <zmatt> the wakeup-m3 is used for power management
Jul 04 09:16:07 <zmatt> anyhow, uio_pruss expects more than what's currently in your dtsi
Jul 04 09:18:30 <zmatt> it's not really clear to me what since I've never used uio_pruss
Jul 04 09:20:37 <dirkk> ok I will try with a standard dts file
Jul 04 09:20:42 <zmatt> hmm
Jul 04 09:20:47 <dirkk> to see if it could work
Jul 04 09:21:11 <zmatt> apparently if you enable pruss without any pinmux it should work, although with a warning; people seem to do that and then separately setup pinmux
Jul 04 09:21:14 <zmatt> which is hideous
Jul 04 09:22:28 <zmatt> hah, hold on
Jul 04 09:23:06 <dirkk> yeah
Jul 04 09:24:17 <zmatt> try this http://pastebin.com/4KRkuYgs
Jul 04 09:25:05 <zmatt> this should keep the silly driver happy
Jul 04 09:25:52 <dirkk> haha
Jul 04 09:29:59 <dirkk>  sudo bin/add-overlay pru-test.dtbo /sys/kernel/config/device-tree/overlays/pru-test/status: unapplied rmdir: removing directory, '/sys/kernel/config/device-tree/overlays/pru-test'
Jul 04 09:30:58 <zmatt> did you first remove old overlays?
Jul 04 09:31:34 <zmatt> check kernel log
Jul 04 09:31:37 <dirkk> hum.. my bad
Jul 04 09:34:34 <zmatt> hmm, this might not work, not entirely sure
Jul 04 09:35:52 <dirkk> kernel log http://pastebin.com/qEXTqEGk
Jul 04 09:36:07 <zmatt> yeah was afraid of that
Jul 04 09:36:12 <dirkk> zmatt :  ./pru_loader ./pru_egp_output.bin Executing program and waiting for termination All done
Jul 04 09:36:15 <zmatt> it doesn't acccept an empty list either
Jul 04 09:36:30 <zmatt> oh right
Jul 04 09:36:30 <zmatt> lol
Jul 04 09:36:32 <zmatt> haha
Jul 04 09:36:33 <dirkk> no error
Jul 04 09:36:51 <zmatt> then you can make the child node even simpler:   child {};
Jul 04 09:37:15 <zmatt> you're right, although it logs an error it does continue after that (unlike the "No children" which is fatal)
Jul 04 09:38:44 <dirkk> I see err failed to create the overlay but I can call prussdrv_open() so...
Jul 04 09:39:06 <zmatt> that's weird though, there shouldn't be a failure
Jul 04 09:39:39 <dirkk> I mean the error in the kernel log
Jul 04 09:40:00 <dirkk> not when I execute the prog
Jul 04 09:40:03 <zmatt> isn't that al older error?
Jul 04 09:40:05 <zmatt> *an
Jul 04 09:40:16 <zmatt> since if creating the overlay failed you shouldn't have any uio device
Jul 04 09:42:34 <dirkk> I still have uio in /sys/class/uio uio0 ... uio7 even if I don't know what it represents
Jul 04 09:48:08 <zmatt> o.o
Jul 04 09:48:21 <zmatt> ehm
Jul 04 09:49:04 <zmatt> it might represent a suggestion to reboot, hehe
Jul 04 09:50:04 <dirkk> haha
Jul 04 10:07:31 <dirkk> zmatt: Thanks for your help ;) toggle pins with pru works
Jul 04 10:08:56 <zmatt> yay :)
Jul 04 10:29:43 <Sinestro> Hey, zmatt, is there any kind of a license on that code?
Jul 04 12:15:05 <zmatt> Sinestro: my start.S ?
Jul 04 12:15:20 <Sinestro> Yeah
Jul 04 12:15:55 <zmatt> it's just a tiny fragment, consider it an educational example
Jul 04 12:20:45 <zmatt> Sinestro: btw since it's always good to check errata, you can find those of the Cortex-A8 revision used in the am335x here -> https://e2e.ti.com/support/arm/sitara_arm/f/791/p/400530/1418692#1418692
Jul 04 12:20:59 <zmatt> fortunately they are few and not really serious
Jul 04 12:21:46 <Sinestro> And thanks! Was just making sure that you weren't linking me to nicely formatted pages based on code from some GPLed project or whatever!
Jul 04 12:22:03 <zmatt> no it's
Jul 04 12:22:05 <zmatt> no it's my own code
Jul 04 12:22:36 <zmatt> it
Jul 04 12:22:37 <zmatt> aregh
Jul 04 12:22:51 <zmatt> ok keyboard, let's try this again
Jul 04 12:24:29 <KotH> zmatt: your keyboard is telling you that it wants more swiss chocolate
Jul 04 12:24:34 <KotH> :-P
Jul 04 12:25:00 <zmatt> it's useful to have a good example of using the new srs/rfe instructions to get exception handling with a unified stack like the cortex-M, there's still an awful lot of code out there that uses crufty exception handling from the ARMv4/v5 era
Jul 04 12:25:24 <KotH> zmatt: it works [tm]
Jul 04 12:37:10 <kremlin> https://marc.info/?l=openbsd-tech&m=146762506326850&w=2
Jul 04 12:37:15 <kremlin> i wrote a driver for the PRU
Jul 04 12:37:17 <kremlin> on openbsd
Jul 04 12:37:46 * kremlin fanfare
Jul 04 12:59:14 <KotH> kremlin: sounds like you have too much free time :)
Jul 04 15:51:09 <zmatt> interesting, TI published a whole bunch of docs on stuff they were previously uptight about;  MII_RT (ethercat) on the am335x, hdvpss in the dm814x, the trm of the dm8127 and dm38x
Jul 04 16:07:04 <zmatt> omap-L13x TRMs also updated (first time in many years)
Jul 04 16:07:26 <zmatt> they've been busy
Jul 04 16:15:08 <zmatt> o.o  public TRMs for automotive parts?  /me falls off chair
Jul 04 16:16:22 <tbr> impossibru!
Jul 04 16:17:18 <tbr> so using ethernet from the PRU was not documented so far?
Jul 04 16:19:05 <zmatt> nope
Jul 04 16:25:37 <kremlin> i hope they release pasm assembler source
Jul 04 16:28:59 <zmatt> https://github.com/beagleboard/am335x_pru_package/tree/master/pru_sw/utils/pasm_source
Jul 04 16:29:35 <kremlin> zmatt: !!
Jul 04 16:29:37 <kremlin> thanks!
Jul 04 16:29:51 <zmatt> you're welcome
Jul 04 20:59:38 <enrutador> hi developers
**** ENDING LOGGING AT Tue Jul 05 02:59:59 2016