ravikp7 / node-beagle-boot Goto Github PK

All protocols used BOOTP, UDP, TFTP, IP, ARP, ETHER

Hi, I want to enable RNDIS in U-Boot. So I find your project.
I can not find RNDIS settings in U-Boot menuconfig.
How do you achieve this?

Hi! I'm trying to build u-boot binaries and instructions on main page produce spl file that does not work (only blank screen in serial console). What's more, I see that in 1.2.1 spl binary is from 2014 u-boot version (seems to be from ages of BBBlfs) and not 2018 that is in instructions.
Could you tell me how you created a recent working u-boot image, especially SPL?

• Choose binary parser modules for JavaScript and create an example
• Write code for ether packet and verify hardware address of BeagleBone from BOOTP request data packet received by server

Currently, an arbitrary bit is checked for request identification. Check https://github.com/ravikp7/node-beagle-boot/blob/master/main.js#L274
It should be replaced with a proper request identification.

Here's the issues we face on Windows

• After transferring SPL to the device.
• The device runs SPL, and the new device detected by host is SPL device.
• Now, this SPL device has two usb configurations. Config 1 has one interface while config 2 has two interfaces.
• For uboot transfer we need the host to use config 2.
• But on Windows, by default config 1 is set and changing usb configs by libusub isn't supported on Windows.
  So, for Windows Support, we need to change default usb configurations either by updating u-boot/SPL or by initiating control transfer to select desired one for transfer.

I got npm install to work via the instructions (+ adding libpcap-dev to the apt-get line) but when I try to start it via npm start I get teh following error:

> [email protected] start /home/debian/node-beagle-boot
> node runServer.js

internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module '/home/debian/node-beagle-boot/node_modules/usb/src/binding/usb_bindings.node'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/home/debian/node-beagle-boot/node_modules/usb/usb.js:5:38)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)

Having randomly working binaries isn't acceptable. We need to know how they were built.

I'd like to patch your u-boot with one that will take netconsole commands and use the netconsole commands to enter UMS mode, rather than enter it directly.... at least not without a timeout period. This would allow arbitrary u-boot commands to be executed, potentially changing the mmc to export, enabling us to probe various hardware features and more.