**** BEGIN LOGGING AT Wed Jun 21 03:00:04 2017 Jun 21 03:31:55 it is the nature of the device Jun 21 03:32:05 it isn't a broadband device Jun 21 12:46:29 hi ds2: I got your waveform outputs, I just wanted to ask what distance you kept b/w sensors and how did you received the waveforms Jun 21 15:50:14 hi all Jun 21 15:50:45 only see 4 reports in the email Jun 21 15:53:21 hi all Jun 21 15:53:46 hi, Jun 21 15:54:46 hello Jun 21 15:54:58 hi Jun 21 15:56:23 hello Jun 21 15:57:24 hey Jun 21 16:00:08 ee: thetransformerr[: did you submit reports to the mailinglist? Jun 21 16:00:13 <_av500_> aloo Jun 21 16:00:18 hello ! Jun 21 16:00:19 o/ Jun 21 16:00:23 I did Jun 21 16:00:27 hej Jun 21 16:00:36 yesterday Jun 21 16:01:01 ah, I see them Jun 21 16:01:07 just making sure Jun 21 16:01:08 Yes, I submitted my report yesterday around 6pm EST. Is it not visible? Jun 21 16:01:16 ok :) Jun 21 16:01:36 so we got them all this week! Jun 21 16:01:54 <_av500_> yay Jun 21 16:02:14 _av500_: ready to get this party started? Jun 21 16:02:24 looks like everyone is here Jun 21 16:02:24 <_av500_> 1) Welcome everybody Jun 21 16:02:46 <_av500_> 2) everybody here? yes? ok! :) Jun 21 16:03:04 yes Jun 21 16:03:12 Hi Jun 21 16:03:55 should i fill the silence with a fart? Jun 21 16:04:04 <_av500_> nerdboy: kickban! Jun 21 16:04:13 eww.... Jun 21 16:04:16 <_av500_> 3) weekly reports Jun 21 16:04:31 <_av500_> I count 6 Jun 21 16:04:38 don't leave any empty space... Jun 21 16:05:07 looks like 6 alright Jun 21 16:05:11 <_av500_> right Jun 21 16:05:30 <_av500_> anybody blocked on anything? Jun 21 16:05:41 nope Jun 21 16:05:47 so far so good Jun 21 16:05:54 things looking good over here Jun 21 16:06:12 <_av500_> good Jun 21 16:06:17 <_av500_> the other three? Jun 21 16:06:20 working on correlation of input and output to calculate tof Jun 21 16:06:29 yeah, I'm having trouble on claiming interface of SPL device on windows :( Jun 21 16:06:44 hi all Jun 21 16:06:52 im moving forward Jun 21 16:06:54 hey!!! Jun 21 16:07:57 jkridner: there are two configs in the SPL device. The kernel is configuring the default 0 Jun 21 16:07:58 <_av500_> good Jun 21 16:08:09 and the bulk transfer endpoints are in config 1 Jun 21 16:08:25 and I can't set the config 1 Jun 21 16:08:30 <_av500_> jkridner: ping Jun 21 16:08:39 libusb is showing error Jun 21 16:08:48 cannot set configuration other than the default one Jun 21 16:09:02 hmmm Jun 21 16:10:03 hi ds2: what did you do, to get those waveforms Jun 21 16:10:14 and what was distance b/w them Jun 21 16:10:33 prudaq sampling for the input... Jun 21 16:10:38 <_av500_> ravikp7: I will see that jkridner gets back to you Jun 21 16:10:46 <_av500_> ds2: can you maybe help here too? Jun 21 16:11:30 av500: ok.. Jun 21 16:11:41 also you have sample data until your board comes Jun 21 16:11:44 <_av500_> 4) 1st term evals Jun 21 16:11:51 well, synthetic data Jun 21 16:12:35 <_av500_> so, this years its three evals, not two Jun 21 16:12:41 <_av500_> due to start next monday Jun 21 16:13:06 ah, ok Jun 21 16:13:20 only by one mentor or both? Jun 21 16:13:33 only by one Jun 21 16:13:38 thx Jun 21 16:13:40 <_av500_> one per project Jun 21 16:13:56 <_av500_> as the google tinmeline says, students continue working Jun 21 16:14:05 <_av500_> eval period are no holidays :) Jun 21 16:14:13 did jkridner ordered maxq for me also??? Jun 21 16:14:26 _av500_: ???? Jun 21 16:14:29 <_av500_> !!1 Jun 21 16:14:33 thetransformerr[: post-processing seems like the best way overall, since we're sampling instead of looking for pulse edge Jun 21 16:14:36 thetransformerr[: I used the maxq board + a scope Jun 21 16:14:40 <_av500_> ds2: you know everything Jun 21 16:14:53 maciejjo_: Want to see your GitHub repo and code in there before filling up your evaluation Jun 21 16:15:02 _av500_: what is the problem in a nutshell Jun 21 16:15:09 <_av500_> ds2: see the report pls Jun 21 16:15:09 be happy to look at it Jun 21 16:15:15 thetransformerr[: there should be some on the way Jun 21 16:15:18 <_av500_> or ask ravikp7 after the meeting Jun 21 16:15:23 Abhishek_: do you have link? Jun 21 16:15:32 * nerdboy hasn't received anything yet either Jun 21 16:15:42 _av500_: ok Jun 21 16:15:44 <_av500_> thx Jun 21 16:15:55 ravikp7: what times are you around? Jun 21 16:16:07 yeah nerdboy: I also think that too, because in outdoor conditions it is almost certain that we are going to have noise Jun 21 16:16:17 maciejjo_: I want to see *your* code and GitHub for your project Jun 21 16:16:30 Abhishek_: I pushed code, for now it is in 'wip' directory Jun 21 16:16:32 sensor data looks kinda noisy already Jun 21 16:16:37 well I wanted to say, I dont need maxq, because my focus is mostly on sw Jun 21 16:16:49 nerdboy/thetransformerr[: I found some potential SW to let me acquire live data.... will update you later if I can get it to work Jun 21 16:16:58 <_av500_> ok guys, before we drop back to in depth tech talk Jun 21 16:17:04 thetransformerr[: understood Jun 21 16:17:08 <_av500_> 5) standup reports Jun 21 16:17:12 and also we cant use maxq in outdoor condition Jun 21 16:17:16 <_av500_> who was on for this week? Jun 21 16:17:30 I and ? Jun 21 16:17:39 me IIRC Jun 21 16:17:44 m_w rounded up 2 i thought Jun 21 16:17:46 ee I guess... Jun 21 16:17:47 ds2: your timezone? Jun 21 16:17:49 thetransformerr[: I wonder if we can just toss it into a goretex bag Jun 21 16:17:55 ee went last week Jun 21 16:17:57 ravikp7: PDT Jun 21 16:18:16 Yep, I did my report last week Jun 21 16:18:33 pmezydlo: maciejjo_: who wants to go first? Jun 21 16:18:49 i'm ready Jun 21 16:19:25 Are you ready? Jun 21 16:19:29 yeah although we should be concerned abt that later but maxq board firstly raises cost highly and require some hacking Jun 21 16:19:50 ok I'm starting Jun 21 16:19:53 yes go ahead Jun 21 16:19:57 it's proof-of-concept for now Jun 21 16:19:59 In this week I configured gpmc, Jun 21 16:20:06 <_av500_> pmezydlo: gogogo Jun 21 16:20:06 GPMC is a unified memory controller dedicated to interfacing external memory devices: SRAM-like memories (AM335 Datasheet), Jun 21 16:20:07 optimazation come later Jun 21 16:20:12 ds2: 9 pm to 2 pm PDT Jun 21 16:20:17 <_av500_> nerdboy: ravikp7: shhh Jun 21 16:20:18 *optimize even Jun 21 16:20:20 I use it for communication between BBB and ICE40, Jun 21 16:20:43 it's good that gpmc pins are located in BBB headers, Jun 21 16:20:56 GPMC controller is configured from the DTS file. It looks like this: https://github.com/pmezydlo/BeagleWire/blob/master/DTS/BW-ICE40Cape-00A0.dts#L136 Jun 21 16:21:16 This is an easy and efficient solution because gpmc clock working with 25MHZ and gpmc data bus has 16 bits, Jun 21 16:21:31 After gpmc configuration I wrote simple application and using /dev/mem I sent first data to fpga, it is gpmc component: https://github.com/pmezydlo/BeagleWire/blob/develop/components/gpmc-sync.v Jun 21 16:21:43 what kind of protocol? Jun 21 16:22:04 parallel interface Jun 21 16:22:20 LEDs blinking very well but for different solutions We want to do something generic, Jun 21 16:22:37 Now I'm preparing dual port memory component, Jun 21 16:22:44 and I want connect first port to gpmc and second to other component. https://github.com/pmezydlo/BeagleWire/blob/develop/components/dp-sync-ram.v Jun 21 16:22:56 pmezydlo: are you muxing Address and data? Jun 21 16:23:00 yes Jun 21 16:23:12 I use only register as memory because most component like a spi, gpio, i2c need only a few memory cell, but we can take data directly from gpmc component, Jun 21 16:23:46 Complicated is synchronization between dual port memory and gpmc still I'm working on it. Jun 21 16:24:00 got a diagram for that? Jun 21 16:24:15 i don't have Jun 21 16:24:33 Recent tests showed that it is already ok, Jun 21 16:25:01 gpmc bus and dual port ram working with diferent clock Jun 21 16:25:17 how much of the ICE40 is used up? Jun 21 16:25:36 few Jun 21 16:25:45 5% Jun 21 16:26:18 I think that's all Jun 21 16:26:31 do you have any questions? Jun 21 16:27:24 <_av500_> sounds good Jun 21 16:27:30 your report says that development is moving slowly, any reason for that? Jun 21 16:28:26 hmm because fpga development is difficult Jun 21 16:29:03 okay Jun 21 16:29:11 thanks for attention :) Jun 21 16:29:19 <_av500_> pmezydlo: do you need specific ice40 questoins answered? Jun 21 16:29:22 you need to provide more granular commits with better commit logs Jun 21 16:30:11 no, for now I know how Jun 21 16:30:22 remember to send me an email when you get stuck on anything for too long Jun 21 16:30:32 <_av500_> pmezydlo: ok Jun 21 16:30:38 yes thanks m_w Jun 21 16:31:27 <_av500_> ok Jun 21 16:31:29 thetransformerr[: yes Jun 21 16:31:32 <_av500_> who is next Jun 21 16:31:35 <_av500_> ? Jun 21 16:31:38 me I think Jun 21 16:31:43 <_av500_> then go ahead Jun 21 16:31:45 ok Jun 21 16:32:02 so my project is DMA transfers support for PRU Jun 21 16:32:47 until now I managed to set up interrupts between PRU and kernel module Jun 21 16:32:51 * m_w needs coffee Jun 21 16:33:03 and another kernel module for performing DMA transfers Jun 21 16:33:14 which uses dmaegnine api from kernel Jun 21 16:33:58 now I am working on controlling the dma hw from PRU Jun 21 16:34:14 here is the code for irq: https://github.com/maciejjo/beaglebone-pru-dma/tree/master/wip/pru_interrupt Jun 21 16:34:25 and for dma: https://github.com/maciejjo/beaglebone-pru-dma/tree/master/wip/pru_dma_test Jun 21 16:36:40 when I will be able to trigger DMA transfers from PRU I will create one application where kernel suppiles address of kernel buffer and direction, and pru controls the transfer Jun 21 16:37:05 maciejjo_: so now , DMA is able to transfer data to the PRU memories ? Jun 21 16:37:48 I tested only with PRU0 SRAM Jun 21 16:38:02 but I think other should work as well Jun 21 16:38:09 and the reverse? will there be an example of streaming data out of the PRU (prehaps ping-ponging between 2 blocks) Jun 21 16:39:45 yes I want to do both way transfers, currently I only did a8->pru Jun 21 16:41:11 maciejjo_: I think must be some direct mapping of DMA interrupts to the PRU INTC channels ? Jun 21 16:41:21 yes, there is Jun 21 16:41:38 shouldnt be difficult then .. Jun 21 16:42:26 and a8->pru was already there throught rpmsg ? Jun 21 16:43:19 *through Jun 21 16:43:29 I din't use rpmsg, I set up own interrupt, should I be using rpmsg? Jun 21 16:44:10 what I mean is, there are already ways to for PRU-A8 interaction. Jun 21 16:44:23 PRU-DMA is what needs to be worked on Jun 21 16:45:22 specifically - PRU-DMA-DDR and DDR-DMA-PRU Jun 21 16:46:24 ok, I am now focusing on this part Jun 21 16:48:38 maciejjo_: Which kernel version are you currently using? Jun 21 16:49:10 Abhishek_: 4.9.30-ti-r38 Jun 21 16:49:54 <_av500_> maciejjo_: thanks Jun 21 16:50:04 <_av500_> so who is on next week? Jun 21 16:50:21 me... :) Jun 21 16:50:47 <_av500_> and? Jun 21 16:50:51 who else hasn't done a report yet? Jun 21 16:51:37 <_av500_> indu: ? Jun 21 16:51:49 <_av500_> ravikp7: ? Jun 21 16:51:54 me on next week Jun 21 16:51:56 <_av500_> ok Jun 21 16:52:19 <_av500_> so indu and thetransformerr[ next week Jun 21 16:52:26 <_av500_> thanks pmezydlo and maciejjo_ Jun 21 16:52:30 np Jun 21 16:52:43 <_av500_> 7) THE END Jun 21 16:52:45 ravikp7: does it work on a Linux host? Jun 21 16:52:47 <_av500_> continue the good work Jun 21 16:52:51 <_av500_> see you next week Jun 21 16:52:55 bye Jun 21 16:52:59 <_av500_> dont forget to commit Jun 21 16:53:00 <_av500_> ! Jun 21 16:53:04 ds2: yes Jun 21 16:53:05 <_av500_> we need to see what you do Jun 21 16:53:29 not all changes at once though Jun 21 16:53:29 ds2: It is able to boot BB into mass storage mode Jun 21 16:53:34 on linux Jun 21 16:53:35 :) Jun 21 16:55:04 ravikp7: so your problem is purely a Windows/Mac issue? Jun 21 16:55:19 ds2: yes Jun 21 16:57:39 ds2: for triggers what should I use in pru.. Jun 21 16:57:59 thetransformerr[: triggers as in starting TX? Jun 21 16:58:07 yup Jun 21 16:58:09 m_w: yes I will try to do more commits Jun 21 16:58:18 ds2: should I sum up the problem again ? Jun 21 16:58:32 ravikp7: not sure what I can help with.... I don't support either of the 2 OS'es. Prehaps, get a usb trace and post that? Jun 21 16:58:57 thetransformerr[: can you summerize your target alg? and how you plan to generate the 40KHz? Jun 21 16:59:45 as for this week, we can assume that interface for sensor is present, Jun 21 17:00:09 thetransformerr[: I am more interested in your algs Jun 21 17:00:54 I am planning to take trigger input wave and receiver adc wave and store each of them in 1d array Jun 21 17:02:18 and then using find cross correlation between them and I found out on some forum, this https://forums.ni.com/t5/LabVIEW/How-to-find-the-time-delay-using-cross-correlation-between-two/td-p/3126132 Jun 21 17:02:46 and on another page, Jun 21 17:03:58 but I am yet to find some official paper like thing, it seems like cross correlation is being used from a long time and is considered as 101 in signal processing Jun 21 17:04:17 for finding time of arrival delay Jun 21 17:06:20 ds2: in your hacked board setup you bypassed all the fancy stuff? Jun 21 17:06:33 thetransformerr[: Hmmm you could do something like this: tell PRU to start acquiring; tell the PWM stuff to start generating a 40KHz wave. stop wave; stop acquiring. All controlled by the A8 Jun 21 17:07:02 nerdboy: yep. the MAXQ chip is neutralized. I jumpered the reset pin so it is in permanent reset. You still can't drive it with > 5V but that should be moot Jun 21 17:07:07 and in this video he used some pre-built function https://youtu.be/L6YJqhbsuFY?t=14m8s Jun 21 17:08:40 thetransformerr[: what about the prudaq examples? i thought he had a timer Jun 21 17:09:12 ds2: ok, thanks. will post the trace Jun 21 17:09:21 also some gist on github Jun 21 17:09:43 nerdboy: we are going to need prudaq code for round robin fashion Jun 21 17:10:14 right, use the timer to trigger some pwm pulse or something Jun 21 17:10:46 jkridner: ping! Jun 21 17:10:56 the ti one has parameters for taht stuff Jun 21 17:10:59 or just have the PRU generate the 40KHz square wave Jun 21 17:11:07 assuming you have spare cycles/spare PRU Jun 21 17:12:00 ravikp7: i think your only hope on windows is sticking to one driver and matching the timing stuff Jun 21 17:12:14 *as much as possible Jun 21 17:12:25 if we generate 40khz from pru there might be difficulty in switching channels for prudaq Jun 21 17:12:50 poke mdp about usb timing... Jun 21 17:12:59 ravikp7: I seem to remember some issues on those 2 platforms in the original project... on the Mac, it was something about a signed driver... windows just didn't work... have you looked at the BB GSoC archives (donno where, got to as someone else) Jun 21 17:13:19 thetransformerr[: is both PRUs used up? Jun 21 17:13:22 thetransformerr[: do you need to switch channels for testing one axis? Jun 21 17:13:53 beaglelogic uses both, so does round-robin code Jun 21 17:14:20 i think "simple" (and slower) prudaq example uses one pru Jun 21 17:14:37 bcos the method I can think for 40kHz is by using loop and therfore we r goin to have difficulty for switching Jun 21 17:15:10 sigh... Jun 21 17:15:17 then use pru to trigger a pulse from pwm Jun 21 17:15:19 no, nerdboy: I dont need switching for one axis Jun 21 17:15:28 ds2: got most problems solved on Windows by looking at original project's windows port, it required rndis initialization by usb control transfer, now got till spl transfer Jun 21 17:15:54 ds2: spl device is having two configurations Jun 21 17:15:58 that is causing problems I think Jun 21 17:16:19 ravikp7: that should be allowed by the USB standard Jun 21 17:16:36 ravikp7: you could try to disable one of them in the SPL code to see if it helps Jun 21 17:16:45 ravikp7: what version of windows are you testing with? Jun 21 17:17:05 ds2: 10 Jun 21 17:17:42 ravikp7: 'k I don't think I can help here Jun 21 17:18:28 ds2: ok, thanks for having a look :) Jun 21 17:19:10 no windoze here either... Jun 21 17:19:46 ravikp7: I have windows 10, I used it for altium designer Jun 21 17:19:46 well still do actually Jun 21 17:20:06 what is required to duplicate your current setup? Jun 21 17:20:51 m_w: clone this branch https://github.com/ravikp7/node-beagle-boot/tree/windows-dev Jun 21 17:21:03 m_w: get node 6 lts version Jun 21 17:22:02 ravikp7: okay lemme see what it does Jun 21 17:22:32 m_w: node.js 6.11.0 , otherwise you would require vs code to build binaries for libusb, which you won't want :) Jun 21 17:22:50 IMO - windows does not work. Jun 21 17:23:31 not code, the original hefty visual studio Jun 21 17:25:27 ravikp7: okay, this might take a bit Jun 21 17:25:50 m_w: okay Jun 21 17:57:54 m_w: ds2: nerdboy: jkridner: I get all info for SPL device including device descriptor, config descriptors, interfaces in USB analyzer tool, but when using the node-usb library it can't access all the config descriptors, shows only 1 config and too wih 0 interfaces and the config description also doesn't match to the one shown by usb analyzer Jun 21 17:58:35 sounds very broken Jun 21 17:58:54 m_w: I used this http://www.usblyzer.com/ analyzer if you want to check Jun 21 18:00:00 should I try with libusb first with c server ? Jun 21 18:00:26 to check if it's problem with libusb or node-usb that binds libusb Jun 21 18:01:06 that seems logical Jun 21 18:02:38 last time when I tried c server on windows, it was unable to transfer spl even, gotta fix that first :( Jun 21 18:03:14 that is not good Jun 21 18:11:16 m_w: are you using a libusb on Windows or the native NDIS stuff? Jun 21 18:12:18 not sure what I am doing Jun 21 18:12:36 oops... I meant ravikp7 Jun 21 18:12:40 just installed WinUSB driver using Zadig Jun 21 18:13:01 ds2: native don't work with libusb to access device Jun 21 18:13:21 sigh...the spiral deepens Jun 21 18:16:57 m_w: here are APIs for node-usb https://github.com/tessel/node-usb check the config desciptors and device descriptors Jun 21 18:48:17 my windows box is very unhappy now :) Jun 21 18:48:25 it is taking forever to reboot Jun 21 18:49:23 this is why I stick to linux for development Jun 21 18:49:31 windoze... Jun 21 18:49:52 ravikp7: I hope it wakes up eventually Jun 21 18:50:30 or I might have to do exactly what it is telling me not to do right now Jun 21 18:51:49 my development also got really slow this week beacause of windows :( Jun 21 19:24:03 ravikp7: ooops installed the newer node Jun 21 19:25:02 looks like you can install the required tools for building using 'npm install --global --production windows-build-tools' as administrator Jun 21 19:25:58 well supposedly, it is still running Jun 21 19:26:29 m_w: server? Jun 21 19:26:43 huh? Jun 21 19:26:55 running? Jun 21 19:27:06 10 home edition I think Jun 21 19:27:20 oh.. Jun 21 19:28:38 installing node 6.11.0 would save more time I guess, don't know how much time it would take to install the build tools on windows Jun 21 19:29:33 m_w: the prebuilt binaries for node 6 are provided by node-usb for windows Jun 21 19:29:39 I am gonna let it run in the background Jun 21 19:30:25 can you install both versions of node at the same time? Jun 21 19:30:51 havn't tried on windows Jun 21 19:33:40 so the tools installed supposedly Jun 21 19:33:46 lets try running it Jun 21 19:33:56 hmm Jun 21 19:35:13 m_w: python installed? Jun 21 19:35:15 running 'npm install' on node-beagle-boot now Jun 21 19:35:24 yes it installs it for you Jun 21 19:36:31 m_w: git checked windows-dev branch ? Jun 21 19:36:45 ravikp7: yes Jun 21 19:37:16 I need to upgrade, this is going soooo sloooow Jun 21 19:37:42 funny thing is that linux runs fine on this same laptop Jun 21 19:38:31 m_w: linux revived many old PCs :) Jun 21 19:39:59 this is not that old, i7 with 12GB of RAM Jun 21 19:40:34 I think it is the hard drive or some errant windows happenings Jun 21 19:42:50 Windows 10 is the buggiest Windows I've used since 98 Jun 21 19:54:36 m_w: installed? Jun 21 20:01:00 bad an error on build Jun 21 20:01:36 had to comment out timespec in one of the system .h files Jun 21 20:01:49 due to redeclaration Jun 21 20:03:10 so now it is throwing an assertion with 'npm start' Jun 21 20:04:04 could not locate the bindings file Jun 21 20:05:09 something about deasync.node Jun 21 20:05:53 what node version you are using ? Jun 21 20:07:00 m_w: ^^ Jun 21 20:08:20 v8.1.2 Jun 21 20:08:52 have tested only with 6 and 7 Jun 21 20:09:04 8 is very recent Jun 21 20:09:19 most beagle-y node stuff isn't that new... Jun 21 20:09:33 no I only installed the latest Jun 21 20:10:17 i think debian iot image has support for 0.x 4.x and 6.x Jun 21 20:11:07 this is on the host side, windows specifically Jun 21 20:11:37 just had to 'npm install deasync' Jun 21 20:12:46 now installed? Jun 21 20:13:01 yup Jun 21 20:13:15 lemme send a pastebin of the output Jun 21 20:13:53 https://pastebin.com/Esawi5sj Jun 21 20:14:57 m_w: you would have to install WInUSB drivers for spl device also Jun 21 20:15:12 spl transfer was successful Jun 21 20:15:49 how do you install the WinUSB for the spl Jun 21 20:17:06 after spl transfer, spl device shows up as rndis device for a while, gotta install drivers with zidag quickly Jun 21 20:17:30 ah Jun 21 20:19:27 can you package/install the right windoze drivers from the bb side? Jun 21 20:20:39 how? Jun 21 20:20:42 actually aren't there drivers already on that weird vfat image? Jun 21 20:21:01 *on the beaglebone when you mount the storage Jun 21 20:21:17 TypeError: Cannot read property 'claim' of undefined Jun 21 20:21:54 m_w: here the interface is undefined :( Jun 21 20:22:44 check device descriptor console.log(device) Jun 21 20:23:05 or config descriptors Jun 21 20:23:16 where would I put this line? Jun 21 20:24:10 find comment "connect beaglebone via spl" Jun 21 20:24:52 line 248 Jun 21 20:25:52 okay Jun 21 20:28:04 m_w: you'll see 2 configs in device descriptor Jun 21 20:28:46 m_w: but it shows only 1 with 0 intefaces Jun 21 20:28:51 https://pastebin.com/B5emju7w Jun 21 20:29:27 appears so Jun 21 20:29:51 exactly Jun 21 20:29:59 m_w: got a usb analyzer installed? Jun 21 20:30:07 nope Jun 21 20:30:20 http://www.usblyzer.com/ try this Jun 21 20:30:59 m_w: one more thing, you connected BB to a usb 3.0 port? Jun 21 20:31:16 yes Jun 21 20:31:28 are you requiring usb3? Jun 21 20:31:34 m_w: are there any 2.0 ports? Jun 21 20:31:37 that is all my laptop has Jun 21 20:31:57 It doesn't work with 2.0 port on windows Jun 21 20:32:07 but I have an old 1.1 hub for just this problem :) Jun 21 20:32:33 It can't read config descriptor when connected to 2.0 port Jun 21 20:33:02 don't why why this is happening Jun 21 20:33:10 *don't know Jun 21 20:34:12 device can't be even opened Jun 21 20:34:25 very strange Jun 21 20:34:45 not the spl device, but the BB in usb boot mode Jun 21 20:36:09 and this is the problem with libusb, I tried even with the c code Jun 21 20:36:10 well it acts the same with the 1.1 hub Jun 21 20:36:35 maybe that *is* the problem? isn't this supposed to work within the usb 2.0 spec? Jun 21 20:38:19 wouldn't that also include 1.1 but slower? Jun 21 20:38:32 except in some edge cases i guess... Jun 21 20:39:03 * nerdboy also not the usb expert Jun 21 20:39:49 wormo 'splained it in a couple of talks Jun 21 20:40:30 the usb analyzer tool also can't access the config descriptor when connected to 2.0 port Jun 21 20:40:59 it's also showing just the device descriptor Jun 21 20:41:26 very strange Jun 21 20:41:45 https://github.com/VCTLabs/scale13x-presentations <= usb quirks might be helpful Jun 21 20:45:25 what can be cause the of this problem here Windows or the drivers ? Jun 21 20:45:53 ravikp7: do you have the BBB serial console output when running this? Jun 21 20:46:27 I still haven't found my debugging cable Jun 21 20:46:50 m_w: yes spl boots, but doesn't broadcast bootp Jun 21 20:47:09 error: remote end didn't respond in time Jun 21 20:47:41 can you post the output? Jun 21 20:48:05 m_w: https://pastebin.com/gJiJ2MD1 Jun 21 20:49:30 can you increase the timeout in u-boot? Jun 21 20:51:15 m_w: drivers/usb/gadget/ether.c here? Jun 21 20:51:22 #define USB_CONNECT_TIMEOUT (3 * CONFIG_SYS_HZ) this ? Jun 21 20:52:25 try jamming that to 30 seconds Jun 21 20:53:43 m_w: but I couldn't get the latest spl build to run :( Jun 21 20:54:02 I thought we figured that out? Jun 21 20:54:32 It broadcasts bootp but never starts tftp of uboot Jun 21 20:54:59 m_w: the usb_ether address not set was one error that we're getting Jun 21 20:54:59 can you post the output of that? Jun 21 20:55:13 yes Jun 21 20:55:42 we need to be able to use the latest versions if we want any kind of support from the U-Boot maintainers Jun 21 20:56:03 https://pastebin.com/zZLNWf0V Jun 21 20:57:01 m_w: the uboot load address in already defined in the spl build config? Jun 21 20:57:31 how spl knows where to load uboot? Jun 21 20:57:51 you would hope so Jun 21 20:58:01 that is the SPL's job :) Jun 21 20:59:07 I tried setting random ethernet address by selecting this option in config, that also didn't work Jun 21 20:59:50 I also changed the timeout to 15, that also didn't help Jun 21 21:00:42 okay, I will have to dig into the U-Boot and see what is going on Jun 21 21:00:58 the patch that I submitted was applied I believe Jun 21 21:01:49 m_w: test it on linux with the server, it's working good there Jun 21 21:02:59 which version of the bootloader works with linux? Jun 21 21:03:54 server? Jun 21 21:06:14 the master branch Jun 21 21:06:54 spl 2014 , the BBBlfs' pre compiled Jun 21 21:08:24 uboot U-Boot 2017.07-rc1-00163-g8cb3ce6 Jun 21 21:09:18 here's the diff of what I changed for uboot https://pastebin.com/rZ3R3zRs Jun 21 21:09:56 here's the working output for linux https://pastebin.com/fXd6VedP Jun 21 21:10:01 so you are using an old SPL and a new regular U-Boot? Jun 21 21:10:11 yes Jun 21 21:12:02 m_w: gotta go to sleep, 2:40 am here, leave messages here if required, I'll get back to you later today Jun 21 21:12:13 good night Jun 21 21:12:50 m_w: your timezone? Jun 21 21:13:09 us central Jun 21 21:13:17 4:13PM Jun 21 21:13:59 ok, bye Jun 21 21:22:41 is "ums 0 mmc 1;" really supposed to replace CONFIG_BOOTCOMMAND ? Jun 21 21:41:33 just wondering if something else needs init before that part **** ENDING LOGGING AT Thu Jun 22 03:00:01 2017