**** BEGIN LOGGING AT Mon Sep 11 03:00:01 2017 Sep 11 04:54:42 hello, has anyone installed the debian stretch image on their BBBlue with the 4.4.87 RT kernel? Sep 11 05:49:49 braincore: tip: just ask whatever question you have, rather than doing a poll on what people might or might not have installed :) Sep 11 08:24:17 For my BBblue, I installed the 4.9.45 ti-rt kernel. I'm getting an error ("PRU servo Controller not initialized") when running `rc_test_servos`. Any ideas? `rc_test_imu` and `rc_test_dsm` work without a hitch. Sep 11 08:24:28 These problems didn't occur on 4.4.* ti-rt Sep 11 08:27:42 hmm, didn't the PRU RPC default change between 4.4 and later kernels? Sep 11 09:09:41 braincore: any errors/messages in kernel log related to remoteproc-pru ? Sep 11 09:11:51 also, it looks like that error should only get printed if initialization of the rc_pru library previously failed... did no other error get printed before this? Sep 11 11:11:46 Hi Sep 11 11:14:39 how i can latest version U-boot and build same version Sep 11 11:14:48 download Sep 11 13:32:25 hi there all :-) Sep 11 13:33:13 BBB A5C revision Sep 11 13:34:44 what I can do with it...? I mean a right cool project for this release Sep 11 13:36:32 any suggestions for A5C revision Sep 11 13:36:54 dury: almost everything you can do with a BBB revC. the main difference is 2GB less of eMMC, instead of 4GB in the revC. Sep 11 13:39:18 samael, with 2gb of eMMC, for example what? Sep 11 13:42:36 samael, which distro fits better in 2GB of eMMC Sep 11 13:42:47 dury: you could take a tour here to find something interesting https://beagleboard.org/project Sep 11 13:43:30 you are overthinking it. Debian (the BBB standard distro nowadays) will do well with 2GB. Ubuntu probably also will do Sep 11 13:49:17 samael, which debian? Sep 11 13:49:42 samael, I mean jessie? Sep 11 13:52:18 samael, which image will fit better in 2GB eMMC Sep 11 14:02:14 samael, are you there? Sep 11 14:03:21 dury: http://beagleboard.org/latest-images pick the old Debian 7.5 (BeagleBone Black - 2GB eMMC) 2014-05-14 Sep 11 14:05:37 that's debian wheezy, isn't it.. samael? Sep 11 14:06:50 yep. though the latest console images should be working too, i suspect. IIRC they are smaller than 1GB, so they can be flashed on older 2GB BBBs too Sep 11 14:07:40 dury: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_console Sep 11 14:08:10 samael, you mean without gui? Sep 11 14:09:56 yep. i don't use any graphics on BBBs, so i don't know how much disk space these images actually take. but i think they are tailored for 4 GB eMMCs in revC BBBs Sep 11 14:11:15 samael, you got rev A5C? Sep 11 14:12:38 i still have a few somewhere, they still work good Sep 11 14:20:08 samael, did you try beaglebone blue one? Sep 11 14:25:02 no. i only use BBBs and embest industrial BBBs Sep 11 14:25:27 the red one, samael? Sep 11 14:26:35 yes Sep 11 14:32:26 have to go, be back later Sep 11 16:39:55 i'm trying to update u-boot on my beaglebone black. can anyone recommend the correct documentation? Sep 11 16:41:14 (ultimately i am trying to permanently adjust the uboot boot delay) Sep 11 16:46:54 specifically, i'm wondering if i can run 'loadx 0x80000' and then send u-boot.img.. but i don't know how recoverable the board will be if i'm wrong Sep 11 19:35:11 zmatt: need your help again if you have time, with cross compiling in eclipse for bbb Sep 11 19:42:00 drue: I don't quite get what you're saying... if you want to update u-boot on the eMMC, just write it to eMMC Sep 11 19:42:35 drue: if you mess up, just boot from sd card and you can again replace u-boot on eMMC Sep 11 19:44:37 drue: writing u-boot to eMMC is dd if=MLO of=/dev/mmcblk1 seek=256 && dd if=u-boot.img of=/dev/mmcblk1 seek=768 Sep 11 19:46:57 zarzar: don't ask to ask, just ask your question. maybe I have the answer, maybe someone else does Sep 11 19:47:11 (I don't actually know much about eclipse) Sep 11 19:53:13 zmatt: ok will ask on eclipse Sep 11 20:13:42 does anyone have an assembly file I can use to test my eclipse cross compile setup? Sep 11 20:14:57 why assembly? if you want to test the cross-compiler shouldn't you use C/C++ ? Sep 11 20:15:20 zmatt: already tested c and c++ Sep 11 20:15:31 i haven't tested the assembler Sep 11 20:16:34 https://github.com/mvduin/bbb-asm-demo Sep 11 20:16:54 i ran $ arm-linux-gnueabihf-as on command line but the assembler never returned after spitting out version Sep 11 20:17:08 so i'm not 100% sure it works Sep 11 20:17:19 well the assembler gets invoked by the compiler, so.. Sep 11 20:19:15 zmatt: if that is true it doesn't print anything during the build Sep 11 20:24:30 correct Sep 11 20:24:35 why would it? Sep 11 20:26:46 zmatt: i don't think it is invoked during the build unless there is an assembly file to process Sep 11 20:37:45 well, it does Sep 11 20:38:07 run gcc with the -### option to see which commands are invoked by the frontend Sep 11 20:39:41 when compiling a C or C++ file it first invokes cc1 or cc1plus, which are the actual C and C++ compiler respectively, which produces an assembly file. the frontend then invokes as Sep 11 20:44:40 where do i add that option? Sep 11 20:44:54 any invocation of gcc or g++ Sep 11 20:45:27 one that performs a compilation, that is Sep 11 20:47:13 "-###"? Sep 11 20:47:42 yeah, literally like that Sep 11 20:47:50 as in gcc -### -c -o foo.o foo.c Sep 11 20:55:17 i see a call to arm-linux-gnueabihf/bin/as Sep 11 20:56:10 there ya go Sep 11 20:59:39 zmatt: thanks again, not sure what arm-linux-gnueabihf-as is, that's not the same as what gcc involjkes Sep 11 21:01:57 it's a symlink Sep 11 21:02:25 oh ok Sep 11 21:03:22 Hi, I managed to download the linux uImage to my BBB via usb_ether. The booting starts, however, it ends in a perpetual loop: Sep 11 21:03:22 [ 2452.193403] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Sep 11 21:03:22 [ 2462.191999] Waiting up to 110 more seconds for network. Sep 11 21:03:22 Could any of you be kind to guide me here, thanks! Sep 11 21:03:40 zarzar: at least on debian, gcc invokes /usr/lib/gcc-cross/arm-linux-gnueabihf/7/../../../../arm-linux-gnueabihf/bin/as which simplifies to /usr/arm-linux-gnueabihf/bin/as which is a symlink to /usr/bin/arm-linux-gnueabihf-as Sep 11 21:03:50 (with gcc I mean arm-linux-gnueabihf-gcc ) Sep 11 21:05:00 ok cool Sep 11 21:05:12 vavula: you seem to be trying to use the kernel's builtin netboot support, but that only works for ethernet Sep 11 21:05:26 (as far as I know) Sep 11 21:05:52 if you want to netboot via usb, use an initramfs which deals with that Sep 11 21:07:29 zmatt: Thank you, so should I try configuring the kernel for usb_ether support? Sep 11 21:09:05 sure, I shall try the second option thatyou suggested. But I was trying out the tutorial from TI as-is, the tutorial made no mention of any special configs, so it left me clueless. Sep 11 21:10:52 which tutorial? Sep 11 21:13:21 http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Setup_Script#TFTP_Setup Sep 11 21:13:21 Using information from: Sep 11 21:14:28 With information from: Sep 11 21:14:29 https://www.denx.de/wiki/view/DULG/LinuxNfsRoot Sep 11 21:14:29 http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User%27s_Guide#Using_the_network_.28Wired_or_USB_Client.29 Sep 11 21:16:16 Most certainly, I will reconfigure my target's uImage with option for RNDIS or similar based on your hints Sep 11 21:17:22 the first two use real ethernet, not via usb Sep 11 21:17:41 the last just describes u-boot functionality (and that part works) Sep 11 21:18:13 hmm Sep 11 21:18:30 actually the last one does seem to imply it should cover booting linux Sep 11 21:19:09 except I think they gloss over that detail Sep 11 21:19:26 yes, but after a bit of trails I found I can unable IPoverUSB interface between host<-->BBB via "setenv ethact usb_ether" and it worked getting DHCP IP, loaded kernel. So, it was promising Sep 11 21:19:50 Sorry, I meant I was able to establish link Sep 11 21:21:13 I think nfsroot via g_ether should be possible, but you'll need a kernel that has g_ether compiled-in rather than as module Sep 11 21:21:42 It required a lot of tweaking on the settings although they weren't mentioned in tutorial. Sep 11 21:22:03 sure, I will try this option Sep 11 21:22:10 yeah you're definitely not taking an easy route :) Sep 11 21:22:31 The whole setup is a run-up to this tutorial: Sep 11 21:22:31 http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5#Perform_SPL_Debug Sep 11 21:23:28 I can take that challenge with hints like yours. Thanks again! Sep 11 21:23:55 why are you doing this via usb anyway? using the ethernet port would probably make things a lot easier Sep 11 21:25:05 My laptop got just one NIC.. Sep 11 21:26:22 I intend setting this way, so I can progress to learning U-Boot internals. Sep 11 21:42:21 You are right. The kernel is configured for USB_ETH [=m]. I'll change this to in-built. Shall update you of the results :) Sep 12 00:40:54 I'm in the process of upgrading BBB RevC to 9.1. using putty to login and finding I can't just login as root with no password now Sep 12 00:42:00 what is the root password I should be using with the Debian 8.7 2017-03-19 4GB SD IoT Sep 12 00:45:18 Is it that I need to login using a different username and password and then enable root login for the SSH server? Sep 12 01:03:39 mjn: debian/temppwd is the default login/password Sep 12 01:04:04 the account has sudo rights so there's usually no reason to actually log in as root Sep 12 01:05:57 by default ssh doesn't allow root Sep 12 01:06:35 by default ssh doesn't allow root login using password authentication rather than public key authentication, and also by default it doesn't allow logging in with a blank password on any account Sep 12 01:07:04 these defaults used to be overridden, but they've been restored for security reasons Sep 12 01:12:53 (if you do decide to enable root login using password authentication, then either set a good password or make very sure the beaglebone never ends up being accessible from the internet... port 22 gets constantly hammered with root login attempts, presumably by botnets) Sep 12 01:21:27 Thanks zmatt. I'm still stuck on how to log in Sep 12 01:22:21 login "debian" password "temppwd" Sep 12 01:22:36 From what I know, I need to edit the uEnv.txt to enable flashing the 9.1 image to emmc Sep 12 01:23:07 if you downloaded a standalone image rather than a flasher then yes Sep 12 01:24:05 I went here https://debian.beagleboard.org/images/bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz Sep 12 01:25:05 why such an old image? Sep 12 01:25:17 (and yes that's a standalone one, not a flasher) Sep 12 01:31:22 hmmm Sep 12 01:31:31 you can always rename root Sep 12 01:50:56 zmatt: thanks for the clue on the default username and password. Sep 12 01:51:09 It really unstuck things. Sep 12 01:52:44 We put a stake in the ground months ago at 7.11 due to compatability issues with a variety of libraries. It seems that revision is just too old to run on the latest BBB Sep 12 01:54:15 So I'm trying to flash something later than what was shipped with the board (8.3) to verify the flashing process. An naturally since the 8.3 root access was disabled Sep 12 02:15:47 PLease excuse my inexperience but lsb_release -a now returns -bash: lsb_release: command not found both for the debian user and root (now that I changed the password and logged in as root) Sep 12 02:31:30 presumably it's just not installed **** ENDING LOGGING AT Tue Sep 12 03:00:00 2017