[beagleboard] Re: PRU phandle is changing
Hi! I'm facing the same issue... Have you found a way to get pruss running from kernel module? Best regards Igor On Wednesday, 10 July 2019 02:10:18 UTC+2, kaigeis...@googlemail.com wrote: > > I'm writing a kernel driver that needs to control the PRUs' state using > rproc_boot(...)/rproc_shutdown(...) > from linux/remoteproc.h. The functions take a `struct rproc *` as > argument. I tried using `rproc_get_by_phandle(...)` to get the reference > to the PRUs. The problem is that the phandles are actually different from > one installation to the other. E.g. after flashing a fresh image, the PRU > phandles could be 0xF4 and 0xF5. The next time, after flashing the image, > the phandles are 0xF6 and 0xF7. They seem, however, to remain the same, if > I don't flash a new image. > > - Why are the phandles different between one image and the other? > - Is there a way to fix them, such that I reliable get pointers to the > PRUs with `rproc_get_by_phandle()`? > - Is there another, better way to reliably get `struct rproc *`s to the > PRUs? > > Thanks, > Kai > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c98a1c5f-fe36-4417-a41f-be2bcd401228%40googlegroups.com.
[beagleboard] Re: Is RPMsg the fastest possible option?
Thank you for your reply. I've seen Maciej's DMA project and it is
certainly something I'd like to try myself, similarly as writing a kernel
module with similar capabilities as beaglelogic (using remoteproc to boot
pruss, exchanging data with pruss etc.). The problem I have right now is
that since kernel v4.9 which Kumar used in his newer beaglelogic some
things have changed (I'm using v4.19). For example the function pruss_get,
which in 4.9 was taking two arguments, first of them being struct device,
now takes one argument of type rproc. The thing is, I have no idea where to
get a handle to rproc from or how to get pruss handle without providing
rproc handle. I can't see remoteproc defined anywhere
in am335x-boneblack-uboot-univ.dts which I'm using and I don't know how
(and whether it's a good way to go) to define it myself. I'll appreciate
any hints regarding this topic.
My overlay:
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", "ti,beaglebone-green";
// identification
part-number = "DRONEDRIVER";
version = "00A0";
fragment@1 {
target-path="/";
__overlay__ {
/* Add default settings for the LA core */
pru-dronedriver {
compatible = "dronedriver,dronedriver";
pruss = <>;
interrupt-parent = <_intc>;
interrupts = <22>, <23>, <24>;
interrupt-names = "from_dd_1", "to_dd", "from_dd_2";
};
};
};
};
Fragment of kernel module I'm trying to get to work:
static struct dronedriver_private_data dronedriver_pdata = {
.fw_names[0] = "am335x-pru0-fw",
.fw_names[1] = "am335x-pru1-fw",
};
static const struct of_device_id dronedriver_dt_ids[] = {
{ .compatible = "dronedriver,dronedriver", .data = _pdata,
},
{ /* sentinel */ },
};
MODULE_DEVICE_TABLE(of, dronedriver_dt_ids);
static int dronedriver_probe(struct platform_device *pdev)
{
struct rproc *rproc;
struct device_node *node = pdev->dev.of_node;
//if (!node)
//return -ENODEV; /* No support for non-DT platforms */
printk(KERN_INFO "[1]\n");
match = of_match_device(dronedriver_dt_ids, >dev);
if (!match)
return -ENODEV;
printk(KERN_INFO "[2]\n");
dddev = kzalloc(sizeof(*dddev), GFP_KERNEL);
if (!dddev)
{
ret = -1;
goto fail;
}
printk(KERN_INFO "[3]\n");
dddev->fw_data = match->data;
dddev->miscdev.fops = _dronedriver_fops;
dddev->miscdev.minor = MISC_DYNAMIC_MINOR;
dddev->miscdev.mode = S_IRUGO;
dddev->miscdev.name = "dronedriver";
printk(KERN_INFO "[5]\n");
dddev->p_dev = >dev;
dev_set_drvdata(dddev->p_dev, dddev);
printk(KERN_INFO "[6]\n");
dev = >dev;
rproc = pru_rproc_get(node,NULL);
if(IS_ERR_OR_NULL(rproc))
{
ret = PTR_ERR(rproc);
if (ret != -EPROBE_DEFER)
dev_err(dev, "Unable to get rproc handle.\n");
goto fail_free;
}
printk(KERN_INFO "[OK] pruss handle\n");
printk(KERN_INFO "[OK] rproc:\nname = \n", rproc->name);
dddev->pruss = pruss_get(rproc);
if (IS_ERR(dddev->pruss))
{
ret = PTR_ERR(dddev->pruss);
if (ret != -EPROBE_DEFER)
dev_err(dev, "Unable to get pruss handle.\n");
goto fail_free;
}
goto fail_free;
printk(KERN_INFO "[OK] pruss handle\n");
...
}
static int dronedriver_remove(struct platform_device *pdev)
{
return 0;
}
static struct platform_driver dronedriver_driver = {
.driver = {
.name = DRV_NAME,
.owner = THIS_MODULE,
.of_match_table = dronedriver_dt_ids,
},
.probe = dronedriver_probe,
.remove = dronedriver_remove,
};
module_platform_driver(dronedriver_driver);
After insmoding this module the last log in dmesg is "Unable to get rproc
handle.". Before I commented out checking "if (!node)" it wasn't making it
to [1] in dmesg. I don't understand the relationship between device tree
and kernel driver enough to tell why of_node is a null pointer here...
Please, help.
On Monday, 23 March 2020 13:11:09 UTC+1, hajo.k...@gmail.com wrote:
>
> I achieved decent throughput by using the standard RPMSG PRU driver with a
> larger buffer size (MAX_FIFO_MSG in rpmsg_pru.c changed from 32 to 4096)
> and by batching the PRU data into 496 byte chunks (512 byte RPMSG message -
> header).
>
> There is a project using the DMA controller which might be a very fast
> option, I haven't tested it yet (but it looks promising):
> https://github.com/maciejjo/beaglebone-pru-dma
>
> IIRC there are other projects that use the second PRU for data shoveling
> instead.
>
>
> Am Mittwoch, 18. März 2020 01:22:01 UTC+1 s
[beagleboard] Is RPMsg the fastest possible option?
I'm checking how fast can I copy data from Beaglebone Black PRU to an userspace app on ARM. I'm using kernel v4.19 TI PREEMPT-RT. So far I simply modified the PRU_RPMsg_Echo_Interrupt1 example from here: https://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#LAB_5:_RPMsg_Communication_between_ARM_and_PRU . Added IEP timer value as part of 480 byte message sent from PRU to ARM to check time delta between data dispatches. For RPMsg I'm using "rpmsg-pru" channel and on the ARM side in userspace app I'm reading the data from /dev/rpmsg_pru31 with function read() to get the data. In this configuration I'm reading the data on ARM side every 90us. Here I wonder whether there is anything I could gather after writing custom kernel module (beaglelogic approach?) over using RPMsg character device. If yes, how much and what would be the best approach to collect the PRU data as quickly as possible? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/66a49c8e-37bb-4648-be3a-ec26a22155b5%40googlegroups.com.
[beagleboard] uEnv.txt not taken into account on debian + 4.19-ti-rt
Hi, I've installed debian + kernal 4.19-ti-rt on my BBB according to this instruction: https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black After I finally started the system I'm trying now to change pins roles to start using PRU. When I change /boot/uEnv.txt file to enable overlays and select which one to use, it doesn't seem to work at all - after reboot pins' roles remain default, no PRU pins enabled. What am I doing wrong? /opt/scripts/tools/version.sh git:/opt/scripts/:[15198b3b7ff40ef517a305eeb7cd20e57f18d37a] eeprom:[A335BNLTEIA05115BBBK0079] model:[TI_AM335x_BeagleBone_Black] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-dirty]:[location: dd MBR] kernel:[4.19.31-ti-rt-r19] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[disable_uboot_overlay_video=1] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19 -TI-00A0.dtbo] pkg check: to individually upgrade run: [sudo apt install --only-upgrade ] pkg:[bb-cape-overlays]:[4.4.20190610.0-0rcnee0~stretch+20190610] WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED] pkg:[kmod]:[23-2rcnee1~stretch+20171005] WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED] pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217] groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c netdev gpio pwm eqep bluetooth admin spi tisdk weston-launch xenomai cloud9ide] cmdline:[console=ttyO0,115200n8 root=UUID=702af096-c19d-4ce1-ac79- 0ad255340345 ro rootfstype=ext4 rootwait] dmesg | grep remote [2.715739] remoteproc remoteproc0: wkup_m3 is available [2.717172] remoteproc remoteproc1: 4a334000.pru is available [2.717809] remoteproc remoteproc2: 4a338000.pru is available [3.051770] remoteproc remoteproc0: powering up wkup_m3 [3.109595] remoteproc remoteproc0: Booting fw image am335x-pm-firmware. elf, size 217168 [3.122818] remoteproc remoteproc0: remote processor wkup_m3 is now up dmesg | grep pru [2.717172] remoteproc remoteproc1: 4a334000.pru is available [2.717362] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully [2.717809] remoteproc remoteproc2: 4a338000.pru is available [2.718000] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully dmesg | grep pinctrl-single [1.229997] pinctrl-single 44e10800.pinmux: 142 pins, size 568 dmesg | grep gpio-of-helper [1.232540] gpio-of-helper ocp:cape-universal: ready lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub END /boot/uEnv.txt uname_r=4.19.31-ti-rt-r19 uuid=702af096-c19d-4ce1-ac79-0ad255340345 enable_uboot_overlays=1 disable_uboot_overlay_video=1 uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo Cheers -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3bcbbc1d-811d-49e3-a778-6d2164ba8f83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: /dev/rpmsg_pruXX missing
OK, problem solved! I didn't know about that: /* The PRU-ICSS system events used for RPMsg are defined in the Linux device tree PRU0 uses system event 16 (To ARM) and 17 (From ARM) PRU1 uses system event 18 (To ARM) and 19 (From ARM) */ I have uploaded firmware with INT 18 and 19 to PRU0 and so I got my problem. I still don't know why is /sys/class/remoteproc absent. Anybody? Greetings On Tuesday, 22 August 2017 18:03:36 UTC+2, Igor Jędrzejczak wrote: > > Hi, > > I'm experiencing an issue with pru_rproc & rpmsg_pru driver. I'm trying to > follow TI Hand-on LAB5 ( > http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#LAB_4:_Introduction_to_Linux_driver) > in > order to be able to exchange data between PRU and ARM. After loading both > projects to PRUs (PRU_RPMsg_Echo_Interrupt1 and PRU_Halt) and modprobe > rpmsg_pru and pru_rproc the device /dev/rpmsg_pruXX doesn't show up. I've > set CHAN_NAME to "rpmsg-pru" in PRU firmware. What could be wrong? > > Another question is: I don't have /sys/class/remoteproc on my BBB. Instead > of remoteproc I have uio directory. Is this normal by my kernel and config > or have I messed something up? > > uname -a: Linux arm 4.4.68-ti-rt-r111 #1 SMP PREEMPT RT Wed Jun 28 > 15:12:37 UTC 2017 armv7l armv7l armv7l GNU/Linux > > uEnv.txt: > uname_r=4.4.68-ti-rt-r111 > uuid=3922138d-29fd-482a-b7fb-24878c566a84 > dtb=am335x-boneblack-emmc-overlay.dtb > > # Overlays > #enable_uboot_overlays=1 > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo > #enable_uboot_cape_universal=1 > > In dtb-overlay files I have disabled uio driver and enabled rproc. > > Greetings > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ce811521-0540-4277-bece-fe4c399550d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] /dev/rpmsg_pruXX missing
Hi, I'm experiencing an issue with pru_rproc & rpmsg_pru driver. I'm trying to follow TI Hand-on LAB5 ( http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#LAB_4:_Introduction_to_Linux_driver) in order to be able to exchange data between PRU and ARM. After loading both projects to PRUs (PRU_RPMsg_Echo_Interrupt1 and PRU_Halt) and modprobe rpmsg_pru and pru_rproc the device /dev/rpmsg_pruXX doesn't show up. I've set CHAN_NAME to "rpmsg-pru" in PRU firmware. What could be wrong? Another question is: I don't have /sys/class/remoteproc on my BBB. Instead of remoteproc I have uio directory. Is this normal by my kernel and config or have I messed something up? uname -a: Linux arm 4.4.68-ti-rt-r111 #1 SMP PREEMPT RT Wed Jun 28 15:12:37 UTC 2017 armv7l armv7l armv7l GNU/Linux uEnv.txt: uname_r=4.4.68-ti-rt-r111 uuid=3922138d-29fd-482a-b7fb-24878c566a84 dtb=am335x-boneblack-emmc-overlay.dtb # Overlays #enable_uboot_overlays=1 #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo #enable_uboot_cape_universal=1 In dtb-overlay files I have disabled uio driver and enabled rproc. Greetings -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1381318a-af4e-4b66-af1c-582e60a2d0c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] could not insert 'g_ether': No such device
Thanks for the info. Now, even when I run *dhclient eth1 *I cannot get IP assigned... Like I said, it's lottery... So it doesn't work and I don't know why... Great... On Sunday, 16 July 2017 04:21:52 UTC+2, RobertCNelson wrote: > > On Sat, Jul 15, 2017 at 7:45 PM, Igor Jędrzejczak <rog...@gmail.com > > wrote: > > @Robert - I did everything as you described here: > > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget > > > > > Why do I have two USB interfaces showing up (USB0 and USB1)? If I cannot > > load g_ether because u_ether is already loaded, do I need to run > > beaglebone-black-g-ether-load.sh during every boot? > > The two interfaces are normal for all images linked from my elinux.org > pages: > > http://elinux.org/BeagleBoardUbuntu > > On the eewiki.net page i haven't migrated things to the dual usb option > yet.. * > > This usb option, allows both Microsoft (7, 8.x, 10) to automatly > install a built-in usb-networking driver without our signed driver.. > the "other" inteface also works with a built-in MacOSX driver.. > > It's just linux that see's both interfaces... > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e15f9d51-9825-4b55-a93b-953e988b72ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] could not insert 'g_ether': No such device
@Robert - I did everything as you described here: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget Why do I have two USB interfaces showing up (USB0 and USB1)? If I cannot load g_ether because u_ether is already loaded, do I need to run beaglebone-black-g-ether-load.sh during every boot? Regards On Sunday, 16 July 2017 01:22:54 UTC+2, RobertCNelson wrote: > > Yeah your right for Ubuntu.. > > Try > > sudo dhclient eth1 > > To see if you can get a proper ip from the beagle. > > Regards, > > On Jul 15, 2017 6:17 PM, "Igor Jędrzejczak" <rog...@gmail.com > > wrote: > >> As I manetioned above - I've got Ubuntu image, not debian. >> >> Command ubu...@192.168.7.2 returns "*No route to host*" >> >> *ifconfig -a* >> >> eth0 Link encap:Ethernet HWaddr d4:be:d9:62:dc:b3 >> inet6 addr: fe80::d6be:d9ff:fe62:dcb3/64 Scope:Link >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:153 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:540 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:69476 (69.4 KB) TX bytes:101702 (101.7 KB) >> Interrupt:18 >> >> eth1 Link encap:Ethernet HWaddr 68:c9:0b:b7:e9:c1 >> inet6 addr: fe80::6ac9:bff:feb7:e9c1/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:33 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:2 errors:58 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:3744 (3.7 KB) TX bytes:268 (268.0 B) >> >> eth3 Link encap:Ethernet HWaddr 1c:ba:8c:a2:ed:72 >> inet6 addr: fe80::1eba:8cff:fea2:ed72/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:32 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:3695 (3.6 KB) TX bytes:7203 (7.2 KB) >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 Metric:1 >> RX packets:564 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:564 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:75634 (75.6 KB) TX bytes:75634 (75.6 KB) >> >> wlan0 Link encap:Ethernet HWaddr 08:3e:8e:29:3d:e2 >> inet addr:192.168.1.16 Bcast:192.168.1.255 Mask:255.255.255.0 >> inet6 addr: fe80::a3e:8eff:fe29:3de2/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:174561 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:61701 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:221739854 (221.7 MB) TX bytes:9156592 (9.1 MB) >> >> Regards >> >> On Sunday, 16 July 2017 01:09:33 UTC+2, RobertCNelson wrote: >>> >>> ssh deb...@192.168.7.2 >>> >>> If that doesn't work.. >>> >>> sudo ifconfig -a >>> >>> Regards, >>> >>> On Jul 15, 2017 5:28 PM, "Igor Jędrzejczak" <rog...@gmail.com> wrote: >>> >>>> Why isn't this connection working then? Network manager in my host >>>> Ubuntu shows it's still connecting. On the list of connections I already >>>> have my BBB, I can ping it, but when i try to ssh to it, I get no route to >>>> host error... >>>> >>>> Here is an image of my networks list: http://imgur.com/a/GUQck >>>> >>>> Regards >>>> >>>> On Sunday, 16 July 2017 00:00:04 UTC+2, RobertCNelson wrote: >>>>> >>>>> On Sat, Jul 15, 2017 at 3:37 PM, Igor Jędrzejczak <rog...@gmail.com> >>>>> wrote: >>>>> > >>>>> > Hi, >>>>> > >>>>> > I'm trying to make Ubuntu 16.04.2 with TI v4.4.x: Real-Time kernel >>>>> work. I'm >>>>> > stuck with a problem to configure ethernet over USB. I'm doing >>>>> everything as >>>>> > explained here: >>>>> > >>>>> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget >>>>> &
Re: [beagleboard] could not insert 'g_ether': No such device
Thanks for this solution - after running *dhclient eth1 *that interface got a proper IP address and I was able to connect through ssh with BBB. I don't consider this a final solution though, as this involves too much uncertainity and manual work in order to simply connect with the device (especially as this can happen automatically). Unfortunately I don't feel myself to be that strong in networking topics to be able to find a final solution myself. So thanks for that one, but could you tell me what else can I do? Regards On Sunday, 16 July 2017 01:22:54 UTC+2, RobertCNelson wrote: > > Yeah your right for Ubuntu.. > > Try > > sudo dhclient eth1 > > To see if you can get a proper ip from the beagle. > > Regards, > > On Jul 15, 2017 6:17 PM, "Igor Jędrzejczak" <rog...@gmail.com > > wrote: > >> As I manetioned above - I've got Ubuntu image, not debian. >> >> Command ubu...@192.168.7.2 returns "*No route to host*" >> >> *ifconfig -a* >> >> eth0 Link encap:Ethernet HWaddr d4:be:d9:62:dc:b3 >> inet6 addr: fe80::d6be:d9ff:fe62:dcb3/64 Scope:Link >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:153 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:540 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:69476 (69.4 KB) TX bytes:101702 (101.7 KB) >> Interrupt:18 >> >> eth1 Link encap:Ethernet HWaddr 68:c9:0b:b7:e9:c1 >> inet6 addr: fe80::6ac9:bff:feb7:e9c1/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:33 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:2 errors:58 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:3744 (3.7 KB) TX bytes:268 (268.0 B) >> >> eth3 Link encap:Ethernet HWaddr 1c:ba:8c:a2:ed:72 >> inet6 addr: fe80::1eba:8cff:fea2:ed72/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:32 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:3695 (3.6 KB) TX bytes:7203 (7.2 KB) >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 Metric:1 >> RX packets:564 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:564 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:75634 (75.6 KB) TX bytes:75634 (75.6 KB) >> >> wlan0 Link encap:Ethernet HWaddr 08:3e:8e:29:3d:e2 >> inet addr:192.168.1.16 Bcast:192.168.1.255 Mask:255.255.255.0 >> inet6 addr: fe80::a3e:8eff:fe29:3de2/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:174561 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:61701 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:221739854 (221.7 MB) TX bytes:9156592 (9.1 MB) >> >> Regards >> >> On Sunday, 16 July 2017 01:09:33 UTC+2, RobertCNelson wrote: >>> >>> ssh deb...@192.168.7.2 >>> >>> If that doesn't work.. >>> >>> sudo ifconfig -a >>> >>> Regards, >>> >>> On Jul 15, 2017 5:28 PM, "Igor Jędrzejczak" <rog...@gmail.com> wrote: >>> >>>> Why isn't this connection working then? Network manager in my host >>>> Ubuntu shows it's still connecting. On the list of connections I already >>>> have my BBB, I can ping it, but when i try to ssh to it, I get no route to >>>> host error... >>>> >>>> Here is an image of my networks list: http://imgur.com/a/GUQck >>>> >>>> Regards >>>> >>>> On Sunday, 16 July 2017 00:00:04 UTC+2, RobertCNelson wrote: >>>>> >>>>> On Sat, Jul 15, 2017 at 3:37 PM, Igor Jędrzejczak <rog...@gmail.com> >>>>> wrote: >>>>> > >>>>> > Hi, >>>>> > >>>>> > I'm trying to make Ubuntu 16.04.2 with TI v4.4.x: Real-Time kernel >>>>> work. I'm >>>>> > stuck with a problem to configure ethernet over USB. I'm doing >>>>> everything as &g
Re: [beagleboard] could not insert 'g_ether': No such device
As I manetioned above - I've got Ubuntu image, not debian. Command ubuntu@192.168.7.2 returns "*No route to host*" *ifconfig -a* eth0 Link encap:Ethernet HWaddr d4:be:d9:62:dc:b3 inet6 addr: fe80::d6be:d9ff:fe62:dcb3/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:153 errors:0 dropped:0 overruns:0 frame:0 TX packets:540 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69476 (69.4 KB) TX bytes:101702 (101.7 KB) Interrupt:18 eth1 Link encap:Ethernet HWaddr 68:c9:0b:b7:e9:c1 inet6 addr: fe80::6ac9:bff:feb7:e9c1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:33 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:58 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3744 (3.7 KB) TX bytes:268 (268.0 B) eth3 Link encap:Ethernet HWaddr 1c:ba:8c:a2:ed:72 inet6 addr: fe80::1eba:8cff:fea2:ed72/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:32 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3695 (3.6 KB) TX bytes:7203 (7.2 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:564 errors:0 dropped:0 overruns:0 frame:0 TX packets:564 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:75634 (75.6 KB) TX bytes:75634 (75.6 KB) wlan0 Link encap:Ethernet HWaddr 08:3e:8e:29:3d:e2 inet addr:192.168.1.16 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::a3e:8eff:fe29:3de2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:174561 errors:0 dropped:0 overruns:0 frame:0 TX packets:61701 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:221739854 (221.7 MB) TX bytes:9156592 (9.1 MB) Regards On Sunday, 16 July 2017 01:09:33 UTC+2, RobertCNelson wrote: > > ssh deb...@192.168.7.2 > > If that doesn't work.. > > sudo ifconfig -a > > Regards, > > On Jul 15, 2017 5:28 PM, "Igor Jędrzejczak" <rog...@gmail.com > > wrote: > >> Why isn't this connection working then? Network manager in my host Ubuntu >> shows it's still connecting. On the list of connections I already have my >> BBB, I can ping it, but when i try to ssh to it, I get no route to host >> error... >> >> Here is an image of my networks list: http://imgur.com/a/GUQck >> >> Regards >> >> On Sunday, 16 July 2017 00:00:04 UTC+2, RobertCNelson wrote: >>> >>> On Sat, Jul 15, 2017 at 3:37 PM, Igor Jędrzejczak <rog...@gmail.com> >>> wrote: >>> > >>> > Hi, >>> > >>> > I'm trying to make Ubuntu 16.04.2 with TI v4.4.x: Real-Time kernel >>> work. I'm >>> > stuck with a problem to configure ethernet over USB. I'm doing >>> everything as >>> > explained here: >>> > >>> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget >>> >>> > but when I run the beaglebone-black-g-ether-load.sh script, I get >>> modprobe: >>> > ERROR: could not insert 'g_ether': No such device... >>> > >>> > Here is my dmesg: https://pastebin.com/KWBgdTTm >>> > Here is my lsmod: https://pastebin.com/vr7J6QHA >>> > >>> > I've been facing similar problem before, when I've been setting up 4.4 >>> > non-rt kernel, and up then solution to my problem was this script >>> added to >>> > rc.local: https://pastebin.com/s7K8Kjrf >>> > >>> > This time it doesn't help though... >>> >>> usb based ethernet is already runnin: >>> >>> [ 17.951533] usb0: HOST MAC 68:c9:0b:b7:e9:c1 >>> [ 17.956656] usb0: MAC 68:c9:0b:b7:e9:c2 >>> [ 17.969298] usb1: HOST MAC 1c:ba:8c:a2:ed:72 >>> [ 17.974212] usb1: MAC 1c:ba:8c:a2:ed:73 >>> [ 18.257950] configfs-gadget gadget: high-speed config #1: c >>> >>> usb_f_rndis25919 2 >>> u_ether14331 2 usb_f_ecm,usb_f_rndis >>> snd_timer 23856 1 snd_pcm >>> libcomposite 54157 14 usb_f_acm,usb_f_ecm,usb_f_rndis >>> >>> Regards, >>> >>> -
Re: [beagleboard] could not insert 'g_ether': No such device
Why isn't this connection working then? Network manager in my host Ubuntu shows it's still connecting. On the list of connections I already have my BBB, I can ping it, but when i try to ssh to it, I get no route to host error... Here is an image of my networks list: http://imgur.com/a/GUQck Regards On Sunday, 16 July 2017 00:00:04 UTC+2, RobertCNelson wrote: > > On Sat, Jul 15, 2017 at 3:37 PM, Igor Jędrzejczak <rog...@gmail.com > > wrote: > > > > Hi, > > > > I'm trying to make Ubuntu 16.04.2 with TI v4.4.x: Real-Time kernel work. > I'm > > stuck with a problem to configure ethernet over USB. I'm doing > everything as > > explained here: > > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget > > > but when I run the beaglebone-black-g-ether-load.sh script, I get > modprobe: > > ERROR: could not insert 'g_ether': No such device... > > > > Here is my dmesg: https://pastebin.com/KWBgdTTm > > Here is my lsmod: https://pastebin.com/vr7J6QHA > > > > I've been facing similar problem before, when I've been setting up 4.4 > > non-rt kernel, and up then solution to my problem was this script added > to > > rc.local: https://pastebin.com/s7K8Kjrf > > > > This time it doesn't help though... > > usb based ethernet is already runnin: > > [ 17.951533] usb0: HOST MAC 68:c9:0b:b7:e9:c1 > [ 17.956656] usb0: MAC 68:c9:0b:b7:e9:c2 > [ 17.969298] usb1: HOST MAC 1c:ba:8c:a2:ed:72 > [ 17.974212] usb1: MAC 1c:ba:8c:a2:ed:73 > [ 18.257950] configfs-gadget gadget: high-speed config #1: c > > usb_f_rndis25919 2 > u_ether14331 2 usb_f_ecm,usb_f_rndis > snd_timer 23856 1 snd_pcm > libcomposite 54157 14 usb_f_acm,usb_f_ecm,usb_f_rndis > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/653c8fed-8c98-44f5-a298-80be035cfac8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] could not insert 'g_ether': No such device
Hi, I'm trying to make Ubuntu 16.04.2 with TI v4.4.x: Real-Time kernel work. I'm stuck with a problem to configure ethernet over USB. I'm doing everything as explained here: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget but when I run the beaglebone-black-g-ether-load.sh script, I get modprobe: ERROR: could not insert 'g_ether': No such device... Here is my dmesg: https://pastebin.com/KWBgdTTm Here is my lsmod: https://pastebin.com/vr7J6QHA I've been facing similar problem before, when I've been setting up 4.4 non-rt kernel, and up then solution to my problem was this script added to rc.local: https://pastebin.com/s7K8Kjrf This time it doesn't help though... I'll appreciate any help. Regards Igor -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f440b156-1304-4397-9be7-aadc55b585e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Unable to find remote_proc in the latest kernel build image
Have* -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/263a7fa1-bbff-4f82-b6ac-5e07ab3f416e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Unable to find remote_proc in the latest kernel build image
Hi, I am experiencing the exact same problem... How you found a fix already? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6287809e-8863-477b-85c7-92f2c25f2063%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Remoteproc not loading firmware
BTW - does the 4.9 ti rt kernel support pru through remoteproc driver? If yes, is it described somewhere how to configure it in this version of kernel? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/54a633c8-bef5-4466-ae2d-180032fbd52b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Remoteproc not loading firmware
I don't get it... What I did now is: git pull in dtb-rebuilder; then make all_arm and make install_arm - everything successfull; then sudo reboot; Now whenever I boot the board or I do sudo modprobe pru_rproc - nothing happens, there is even no message saying that prus were probed successfully... On Tuesday, 11 July 2017 20:52:06 UTC+2, RobertCNelson wrote: > > On Tue, Jul 11, 2017 at 1:36 PM, Igor Jędrzejczak <rog...@gmail.com > > wrote: > > I also now noticed that there is a message from remoteproc about loading > > some elf fw file... Here is my whole dmesg, maybe there is some > misconfig > > there... > > > > https://pastebin.com/1HGLkRi2 > > The elf file is for the Cortex-M3 which is used for power management. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9a98ce3f-c20d-4cb3-a0bb-4ef658c473ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Remoteproc not loading firmware
I also now noticed that there is a message from remoteproc about loading some elf fw file... Here is my whole dmesg, maybe there is some misconfig there... https://pastebin.com/1HGLkRi2 Thanks for a quick reply Regards On Tuesday, 11 July 2017 20:19:45 UTC+2, Igor Jędrzejczak wrote: > > @Robert - tried it, didn't help... > > On Tuesday, 11 July 2017 18:15:31 UTC+2, RobertCNelson wrote: >> >> On Tue, Jul 11, 2017 at 10:57 AM, Igor Jędrzejczak <rog...@gmail.com> >> wrote: >> > >> > Hello! >> > >> > I'm facing an issue with Beaglebone Black PRU. I have successfully >> compiled >> > a C program for PRU0 and copied it to /lib/firmware with name >> > am335x-pru0-fw. But when I type sudo rmmod pru_rproc and then sudo >> modprobe >> > pru_rproc I see only that both PRUs have been probed successfully, but >> there >> > is no sign of firmware being loaded. My program doesn't work at all so >> it >> > seems it hasn't been loaded... I have no idea why that could be. I'm >> coming >> > back to PRU programming after a while, so this might be I'm missing >> > something, but what is this? >> > >> > My kernel is 4.9.36 ti rt >> > >> > Dmesg output: >> > [ 361.101046] pru-rproc 4a338000.pru1: pru_rproc_remove: removing >> rproc >> > 4a338000.pru1 >> > [ 361.113437] remoteproc remoteproc2: releasing 4a338000.pru1 >> > [ 361.113740] pru-rproc 4a334000.pru0: pru_rproc_remove: removing >> rproc >> > 4a334000.pru0 >> > [ 361.114703] remoteproc remoteproc1: releasing 4a334000.pru0 >> > [ 365.601110] remoteproc remoteproc1: 4a334000.pru0 is available >> > [ 365.601329] pru-rproc 4a334000.pru0: PRU rproc node >> > /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000 probed >> successfully >> > [ 365.608375] remoteproc remoteproc2: 4a338000.pru1 is available >> > [ 365.608639] pru-rproc 4a338000.pru1: PRU rproc node >> > /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000 probed >> successfully >> > >> > >> > My uEnv file in /boot: >> > uname_r=4.9.36-ti-rt-r45 >> > uuid=0e71d59c-6852-49b0-92b3-1769eaed1c2e >> > dtb=am335x-boneblack-emmc-overlay.dtb >> >> it might not see the firmware.. >> >> sudo update-initramfs -uk `uname -r` >> >> sudo reboot >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a095aabf-0948-42c7-bdfb-6739b8826d26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Remoteproc not loading firmware
@Robert - tried it, didn't help... On Tuesday, 11 July 2017 18:15:31 UTC+2, RobertCNelson wrote: > > On Tue, Jul 11, 2017 at 10:57 AM, Igor Jędrzejczak <rog...@gmail.com > > wrote: > > > > Hello! > > > > I'm facing an issue with Beaglebone Black PRU. I have successfully > compiled > > a C program for PRU0 and copied it to /lib/firmware with name > > am335x-pru0-fw. But when I type sudo rmmod pru_rproc and then sudo > modprobe > > pru_rproc I see only that both PRUs have been probed successfully, but > there > > is no sign of firmware being loaded. My program doesn't work at all so > it > > seems it hasn't been loaded... I have no idea why that could be. I'm > coming > > back to PRU programming after a while, so this might be I'm missing > > something, but what is this? > > > > My kernel is 4.9.36 ti rt > > > > Dmesg output: > > [ 361.101046] pru-rproc 4a338000.pru1: pru_rproc_remove: removing rproc > > 4a338000.pru1 > > [ 361.113437] remoteproc remoteproc2: releasing 4a338000.pru1 > > [ 361.113740] pru-rproc 4a334000.pru0: pru_rproc_remove: removing rproc > > 4a334000.pru0 > > [ 361.114703] remoteproc remoteproc1: releasing 4a334000.pru0 > > [ 365.601110] remoteproc remoteproc1: 4a334000.pru0 is available > > [ 365.601329] pru-rproc 4a334000.pru0: PRU rproc node > > /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000 probed > successfully > > [ 365.608375] remoteproc remoteproc2: 4a338000.pru1 is available > > [ 365.608639] pru-rproc 4a338000.pru1: PRU rproc node > > /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000 probed > successfully > > > > > > My uEnv file in /boot: > > uname_r=4.9.36-ti-rt-r45 > > uuid=0e71d59c-6852-49b0-92b3-1769eaed1c2e > > dtb=am335x-boneblack-emmc-overlay.dtb > > it might not see the firmware.. > > sudo update-initramfs -uk `uname -r` > > sudo reboot > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ff88820e-a436-4a01-b574-3577113af2cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Remoteproc not loading firmware
Hello! I'm facing an issue with Beaglebone Black PRU. I have successfully compiled a C program for PRU0 and copied it to /lib/firmware with name am335x-pru0-fw. But when I type sudo rmmod pru_rproc and then sudo modprobe pru_rproc I see only that both PRUs have been probed successfully, but there is no sign of firmware being loaded. My program doesn't work at all so it seems it hasn't been loaded... I have no idea why that could be. I'm coming back to PRU programming after a while, so this might be I'm missing something, but what is this? My kernel is 4.9.36 ti rt Dmesg output: [ 361.101046] pru-rproc 4a338000.pru1: pru_rproc_remove: removing rproc 4a338000.pru1 [ 361.113437] remoteproc remoteproc2: releasing 4a338000.pru1 [ 361.113740] pru-rproc 4a334000.pru0: pru_rproc_remove: removing rproc 4a334000.pru0 [ 361.114703] remoteproc remoteproc1: releasing 4a334000.pru0 [ 365.601110] remoteproc remoteproc1: 4a334000.pru0 is available [ 365.601329] pru-rproc 4a334000.pru0: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000 probed successfully [ 365.608375] remoteproc remoteproc2: 4a338000.pru1 is available [ 365.608639] pru-rproc 4a338000.pru1: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000 probed successfully My uEnv file in /boot: uname_r=4.9.36-ti-rt-r45 uuid=0e71d59c-6852-49b0-92b3-1769eaed1c2e dtb=am335x-boneblack-emmc-overlay.dtb Best regards Igor -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b56086f4-0d51-4f38-9f20-bdc53c7c9517%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Ethernet over USB works only after plugging in the eth cable
Yupi, it works! Had to put this into rc.local: https://pastebin.com/R3rUc5rx It was ssh that was getting up too early. Thanks a lot for your help Robert! Regards -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3985406d-fe5c-4e1b-b29e-9e7f2d5e984b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Ethernet over USB works only after plugging in the eth cable
What I'm trying to do is to configure my BBB so, that when I boot it, ethernet over USB gets configured automatically so that I wouldn't have to use ethernet cable at all, just USB. And udchcpd gets restarted after beaglebone-black-g-ether-load.sh is done, isn't it? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e9ae294a-9ee0-49b8-b442-4f0c7467b97f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Ethernet over USB works only after plugging in the eth cable
Yup, I pasted wrong script name, but meant beaglebone-black-g-ether-load.sh When should I restart dnsmasq/udchpd/etc? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/37310d93-15e6-49c8-96a5-dd760512b2c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Ethernet over USB works only after plugging in the eth cable
One message from journal which I don't know what actually means: "is interface usb0 up and configured?: Cannot assign requested address". Does that mean, that bbb-eMMC-flasher-eewiki-ext4.sh is called too early? On Sunday, 16 April 2017 14:12:33 UTC+2, Igor Jędrzejczak wrote: > > Thank you Robert for a quick answer. Unfortunately disabling that script > didn't help and I still have to plug int eth cable in order to 'unlock' > ethernet over USB. > > I had an idea, that maybe setting eth to allow-hotplug instead of auto in > /etc/network/interfaces might help, but did only for one boot - later the > system needed 90s to shut down, and when booted again I couldn't connect > through USB anymore... > > When should I actually run bbb-eMMC-flasher-eewiki-ext4.sh? I tried: > - from rc.local with settings After=network.target > in /etc/systemd/system/rc-local.service and After=network-online.target in > /etc/systemd/system/rc-local.service.d/debian.conf > - from rc.local with settings After=network.target > in /etc/systemd/system/rc-local.service and After=network.target in > /etc/systemd/system/rc-local.service.d/debian.conf > - from rc.local with settings After=local-fs.target > in /etc/systemd/system/rc-local.service and After=local-fs.target.target in > /etc/systemd/system/rc-local.service.d/debian.conf > > How about setting usb0 to auto in /etc/network/interfaces? > > It seems to me, that either ssh or USB0 gets up only after plugging > ethernet cable... > > Journal output after disabling generic service: > https://pastebin.com/2hLpHTnW > > Regards > > On Sunday, 16 April 2017 03:51:44 UTC+2, Igor Jędrzejczak wrote: >> >> Hi, >> >> I'm having an issue with connection to my BBBI over USB. I have installed >> today a new system on the board - Ubuntu 16.04.2 with 4.9.21-ti-rt-r29 >> kernel. I've been following the steps from here: >> https://eewiki.net/display/linuxonarm/BeagleBone+Black >> >> Now, that my system is flashed to eMMC and (almost) ready to use, I have >> a strange issue with USB connection. When I plug in my USB cable and >> connect host PC with BBB, after ~30s of booting, my host finally gives me >> an announcement that new wired connection was made. Then when I try "ssh >> ubuntu@192.168.7.2" connection gets refused... Now the funny thing is >> that when I plug in an ethernet cable to BBB, after few seconds I can try >> again with "ssh ubuntu@192.168.7.2" and then it works - until the next >> boot... >> >> I have copied beaglebone-black-g-ether-load.sh script to my beaglebone >> and am calling it from /etc/rc.local (whose settings I have changed to be >> called after file system is initialized, not as it was set up previously >> after network interfaces are up - then I had even worse situation where I >> have been getting connection timeouts instead of refusal) >> >> I'm out of ideas... I'll appreciate every hint. Below some basic commands >> outputs: >> ubuntu@arm:~$ uname -a >> Linux arm 4.9.21-ti-rt-r29 #1 SMP PREEMPT RT Sat Apr 15 00:04:36 CEST >> 2017 armv7l armv7l armv7l GNU/Linux >> >> dmesg https://pastebin.com/FXEn1knE >> >> ifconfig https://pastebin.com/5NseyN1P >> >> journalctl https://pastebin.com/RhbFPdEa >> >> Regards >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1a7b1b44-4c3d-466a-826f-b92bbb2bf34b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Ethernet over USB works only after plugging in the eth cable
Thank you Robert for a quick answer. Unfortunately disabling that script didn't help and I still have to plug int eth cable in order to 'unlock' ethernet over USB. I had an idea, that maybe setting eth to allow-hotplug instead of auto in /etc/network/interfaces might help, but did only for one boot - later the system needed 90s to shut down, and when booted again I couldn't connect through USB anymore... When should I actually run bbb-eMMC-flasher-eewiki-ext4.sh? I tried: - from rc.local with settings After=network.target in /etc/systemd/system/rc-local.service and After=network-online.target in /etc/systemd/system/rc-local.service.d/debian.conf - from rc.local with settings After=network.target in /etc/systemd/system/rc-local.service and After=network.target in /etc/systemd/system/rc-local.service.d/debian.conf - from rc.local with settings After=local-fs.target in /etc/systemd/system/rc-local.service and After=local-fs.target.target in /etc/systemd/system/rc-local.service.d/debian.conf How about setting usb0 to auto in /etc/network/interfaces? It seems to me, that either ssh or USB0 gets up only after plugging ethernet cable... Journal output after disabling generic service: https://pastebin.com/2hLpHTnW Regards On Sunday, 16 April 2017 03:51:44 UTC+2, Igor Jędrzejczak wrote: > > Hi, > > I'm having an issue with connection to my BBBI over USB. I have installed > today a new system on the board - Ubuntu 16.04.2 with 4.9.21-ti-rt-r29 > kernel. I've been following the steps from here: > https://eewiki.net/display/linuxonarm/BeagleBone+Black > > Now, that my system is flashed to eMMC and (almost) ready to use, I have a > strange issue with USB connection. When I plug in my USB cable and connect > host PC with BBB, after ~30s of booting, my host finally gives me an > announcement that new wired connection was made. Then when I try "ssh > ubuntu@192.168.7.2" connection gets refused... Now the funny thing is > that when I plug in an ethernet cable to BBB, after few seconds I can try > again with "ssh ubuntu@192.168.7.2" and then it works - until the next > boot... > > I have copied beaglebone-black-g-ether-load.sh script to my beaglebone and > am calling it from /etc/rc.local (whose settings I have changed to be > called after file system is initialized, not as it was set up previously > after network interfaces are up - then I had even worse situation where I > have been getting connection timeouts instead of refusal) > > I'm out of ideas... I'll appreciate every hint. Below some basic commands > outputs: > ubuntu@arm:~$ uname -a > Linux arm 4.9.21-ti-rt-r29 #1 SMP PREEMPT RT Sat Apr 15 00:04:36 CEST 2017 > armv7l armv7l armv7l GNU/Linux > > dmesg https://pastebin.com/FXEn1knE > > ifconfig https://pastebin.com/5NseyN1P > > journalctl https://pastebin.com/RhbFPdEa > > Regards > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/452e6c46-9ae2-4b92-a9bc-46b81f3a2945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
