**** BEGIN LOGGING AT Sun Jan 21 03:00:02 2018
Jan 21 03:01:03 <ravikp7> Abhishek_: Hi :)
Jan 21 05:55:15 <ravikp7> Abhishek_: just got your issue with node-beagle-boot, will look into it and get back to you asap
Jan 21 07:44:52 <ravikp7> Abhishek_: So, seems like you got the SPL transferred then it's not transferring the uboot binary. It's a known issue with the upstream uboot. I couldn't fix it. See thread https://groups.google.com/forum/#!topic/beagleboard-gsoc/8osyK8ttvVk
Jan 21 07:47:33 <ravikp7> Abhishek_: I'm using old spl binary built from older source when it worked. For now you can also try with old spl binary (provided with repo) or build it from old source. It can transfer uboot built from latest source
Jan 21 08:16:47 <Abhishek_> ravikp7: It looks like USB is receiving packets but is not able to parse the packets sent by uboot
Jan 21 08:17:53 <Abhishek_> I did some wireshark sleuthing.
Jan 21 08:37:43 <ravikp7> Abhishek_: hmm, can't remember exactly how I concluded that back then, have been months since I looked into this. I think it's time to give it a spin ;)  will try it today
Jan 21 08:55:44 <Abhishek_> Actually u-boot is sending DHCPDISCOVER packet instead of BOOTP packet so the parsing is not being done properly I guess
Jan 21 08:55:53 <Abhishek_> ravikp7: ^
Jan 21 09:34:11 <ravikp7> Abhishek_: It says BOOTP braodcast1 - n
Jan 21 09:34:34 <Abhishek_> yeah, I'm saying that's how it appears under when seen from Wireshark
Jan 21 09:34:37 <ravikp7> Abhishek_: and I'm not even getting this BOOTP broadcast with the upstream boot
Jan 21 09:34:40 <ravikp7> U-Boot SPL 2018.01-00353-g557767ed29-dirty (Jan 21 2018 - 14:42:32)
Jan 21 09:34:41 <ravikp7> Trying to boot from USB eth
Jan 21 09:34:47 <ravikp7> stuck on this
Jan 21 09:34:48 <Abhishek_> Do you have wireshark?
Jan 21 09:35:09 <ravikp7> will install and check
Jan 21 09:35:11 <Abhishek_> Did you apply the rcn-ee patches?
Jan 21 09:35:24 <ravikp7> no
Jan 21 09:35:26 <Abhishek_> There are two patches that need to be applied.
Jan 21 09:35:47 <ravikp7> links please
Jan 21 09:35:49 <Abhishek_> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
Jan 21 09:38:01 <Abhishek_> Also in am335x_evm_defconfig, insert the following lines:
Jan 21 09:38:44 <Abhishek_> https://www.irccloud.com/pastebin/0MOcvEOA/
Jan 21 09:44:41 <ravikp7> Abhishek_: still not getting bootp broadcast even after applying patch :(
Jan 21 09:45:25 <Abhishek_> this happened with me also when I was on am335x_evm_usbspl_defconfig
Jan 21 09:46:07 <ravikp7> I'm also using this
Jan 21 09:46:34 <Abhishek_> Switch to am335x_evm_defconfig after you have added those lines in there.
Jan 21 09:46:59 <Abhishek_> Hopefully you should see the BOOTP broadcasts then.
Jan 21 09:50:52 <ravikp7> Abhishek_: those lines? you mean the patch?
Jan 21 09:51:43 <Abhishek_> I posted a pastebin:
Jan 21 09:51:49 <Abhishek_> https://www.irccloud.com/pastebin/0MOcvEOA/
Jan 21 09:54:49 <ravikp7> aren't those already included in am335x_evm_usbspl_defconfig ?
Jan 21 09:55:19 <Abhishek_> I used am335x_evm_defconfig to build my u-boot here
Jan 21 09:55:44 <Abhishek_> By adding those lines, you can enable the same functionality in the default bootloader
Jan 21 10:03:22 <ravikp7> thanks, getting bootp broadcast now
Jan 21 10:03:45 <Abhishek_> Now, come to your nodejs script in node-beagleboot
Jan 21 10:04:54 <Abhishek_> Do you stop after SPL is transferred and get "Ready to Flash"?
Jan 21 10:06:36 <ravikp7> I configured it according to vid and pid provided by evm_usbspl config
Jan 21 10:07:17 <ravikp7> the vid and pid shown by spl device now is different from what was set by that config
Jan 21 10:07:29 <Abhishek_> Correct, that's what I am seeing
Jan 21 10:07:40 <ravikp7> this vid, pid was set for the mass storage device
Jan 21 10:07:46 <Abhishek_> yep
Jan 21 10:08:10 <Abhishek_> The ether.c driver in uboot has changed a lot since 2014 that's what I understand from this thing
Jan 21 10:08:53 <Abhishek_> So to bypass that I changed SPLVID and SPLPID in your main.js script to the ones from mass storage.
Jan 21 10:09:28 <ravikp7> yeah, let me check by modifying those ids and some code if it works
Jan 21 10:09:46 <Abhishek_> It will stop at "Interface claimed". I tried that yesterday :)
Jan 21 10:12:13 <ravikp7> will work on this after an hour, time for lunch :)
Jan 21 10:12:58 <Abhishek_> In the meantime I'll post here if I catch on to something.
Jan 21 10:14:28 <ravikp7> when m_w submitted this patch https://patchwork.ozlabs.org/patch/774899/ last year bootp broadcast got working on evm_usbspl, it's broken again, time for another patch
Jan 21 10:15:00 <Abhishek_> I've mailed m_w as well
Jan 21 10:15:27 <Abhishek_> Right now I suspect the problem is in the nodejs script.
Jan 21 10:15:35 <Abhishek_> Working on it.
Jan 21 11:30:42 <Abhishek_> After some really ugly hacking:
Jan 21 11:34:02 <Abhishek_> https://www.irccloud.com/pastebin/eJqqECZk/
Jan 21 14:10:23 <ravikp7> Abhishek_: great! so what's the catch?
Jan 21 14:25:41 <Abhishek_> ravikp7: First, there's some subtle difference in the packets U-Boot sends vs what the AM335x Boot ROM sends
Jan 21 14:25:53 <Abhishek_> This I got via Wireshark
Jan 21 14:26:13 <Abhishek_> It sends DHCPDISCOVER packets instead of BOOTP packets
Jan 21 14:26:38 <Abhishek_> So first hack was in u-boot to force it to BOOTP instead of DHCP
Jan 21 14:26:52 <Abhishek_> and then a little bit in your script to account for the packet types/
Jan 21 17:58:44 <Abhishek_> Some more digging, and finally got it to run without the ugly hack in uboot
Jan 21 17:59:29 <Abhishek_> Basically, you have to add a DHCP ACK into the BOOTP reply packet (in the vendor section)
**** ENDING LOGGING AT Mon Jan 22 03:00:02 2018