**** BEGIN LOGGING AT Tue Mar 19 02:59:57 2019 Mar 19 03:00:22 Sorry zmatt I lost connection. Yes I am using the CAN overlay Mar 19 03:05:13 okay. easiest is probably to continue to do so in the latest image. the settings in /boot/uEnv.txt are different, but you can still specify overlays to be loaded Mar 19 03:05:50 (it's no longer required, you can also use config-pin to select pinmux at runtime) Mar 19 03:06:33 configuring the can interface should work the same, except I'm guessing in your case it's called can0 while it should be can1 on current images Mar 19 03:07:27 that's probably the only changes Mar 19 06:44:34 thinkfat: yup it's BB unrelated but I usually get good tips here so that's why I asked Mar 19 06:44:38 :p Mar 19 06:45:32 manufacturer's manual didn't help though Mar 19 07:37:16 das: what SoC were you talking about? Mar 19 07:38:34 without documentation of the SoC, pretty much the only option is to analyze existing software to learn about any details of the SoC Mar 19 07:39:12 (augmented by experimentation to clarify unclear details) Mar 19 08:06:26 zmatt: it's a SAMA5 from Atmel, the memory mapping described in its documentation is not what I observe using JTAG, although this could stem from many things I don't understand Mar 19 08:07:49 das: first, there is #at91 specifically for that chip. second, you are almost certainly missing the remap operation that the bootloeder does Mar 19 08:08:12 hence the memory layour appears "non-fitting" Mar 19 08:12:17 "remap operation" ? Mar 19 08:14:10 zmatt: its been quite a while, but if i'm not super totally mistaken the at91 rom (or u-boot, really not sure) remaps 0x10000000 to 0x00000000 on the at91 during boot sequence Mar 19 08:15:15 oh alright, thanks Mar 19 08:15:30 if I have enough time i'll try to reverse the romcode Mar 19 08:15:35 are you referring to the MMU? does openocd not offer a way to access the physical address space? Mar 19 08:15:40 might be only in conjunction with boot from parallel flash or such, but there *IS* something Mar 19 08:16:14 das: and really no need to reverse anything here, the documentation is totally correct. you probably just have to really read it en detail. Mar 19 08:16:23 using openocd I can dump the filesystem, which is what I was after anyways Mar 19 08:16:35 "dump the filesystem" ? Mar 19 08:17:03 it's a linux target, I dumped the mounted filesystems Mar 19 08:17:49 trying to get a reverseshell now, might take a while :) Mar 19 08:19:06 jsut try to find the serial debug console pins. Mar 19 08:19:29 tis locked somehow Mar 19 08:19:37 but again. this is so remote to the topics of this channel, that i would like the topic being moved out rather soon. Mar 19 08:19:49 yes, thanks for the help Mar 19 10:53:05 i want to permanently upload a open cv code on beagle bone black,please help Mar 19 11:13:39 plase reply Mar 19 13:38:07 so where does the MLO file reside? I can see the backup of it .. is it squirelled away in the first blocks of the sdcard? Mar 19 13:55:03 yep, both MLO (or technically configuration header + MLO) and u-boot.img are (start sector 256 and 768 respectively) Mar 19 13:55:40 so firmware on the chip loads that block? Mar 19 13:56:16 yeah it looks for configuration header in sector 0, 256, 512, and 768, and if found loads MLO starting from the next sector Mar 19 13:56:24 neat Mar 19 13:56:31 ok .. mystery solved Mar 19 13:58:13 so I'm booting MLO off an sdcard that has a /boot/uEnv.txt and a /uEnv.txt .. everything else gets loaded from the usb hardrive now Mar 19 14:16:18 this is what I ended up with zmatt Mar 19 14:16:22 https://dpaste.de/3y1m Mar 19 14:24:29 oh, and of course the /etc/fstab uses /dev/sda4 Mar 19 15:04:44 what is the common practice into a script to: if "process" is running then do something ? Mar 19 15:05:10 uh wrong channel Mar 19 15:05:26 but surely someone knows here... :-)) Mar 19 15:06:28 fred__tv: pidof. Mar 19 15:09:13 thanks, so if [[ $? -ne 0 ]] ; then the program is running ?? Mar 19 15:09:52 fred__tv: i don't have the exact steps at hand. but probably something along those lines. Mar 19 15:10:31 * zmatt smells an http://xyproblem.info/ Mar 19 15:10:42 zmatt: thats not just a smell. Mar 19 15:11:36 anyone know the FCC ID for the beaglebone blue wifi? Mar 19 15:12:11 pidof returns process id , so if pid is different from 0 it means process is running, am I wrong ? Mar 19 15:13:38 tkwhite: see https://raw.githack.com/beagleboard/beaglebone-blue/master/regulatory/beaglebone-blue-fcc-ce-report.pdf page 38 Mar 19 15:14:17 This device contains an FCC approved radio module (2.4 GHz), FCC ID: Z64-WL18SBMOD Mar 19 15:16:46 thank you, that was helpful Mar 19 15:17:07 and easy to find by googling "beaglebone blue fcc" :P Mar 19 16:51:25 Hi, I was wondering, what exactly gets flashed to eMMC? Since I only have 4 GB, I wanted to be able to install lots more packages to a microSD, but I was worried that if I flash the Debian image, it might be difficult to install packages in other storage. Mar 19 16:52:11 galaxie: spreading a system across eMMC and sd card is in general a complicated thing to do Mar 19 16:53:00 zmatt: Ah, OK. So what would you advise? Keep everything on microSD card? Mar 19 16:53:03 (other than simple cases like using the sd card for a single directory, e.g. your home directory or some data directory containing large files Mar 19 16:53:06 ) Mar 19 16:53:32 Would it by default install packages to eMMC? Mar 19 16:54:28 don't install packaged "to eMMC" or "to SD", you install them onto your system, regardless of whether that system is located on eMMC or SD Mar 19 16:54:35 *packages Mar 19 16:55:27 So if flashed to eMMC, they get installed to eMMC? OK. Then I'm definitely going with SD. Mar 19 16:55:39 I've personally never had any problems with the amount of eMMC storage, 4GB is plenty of space for most purposes, but if you really think you need more than that for some reason then it may be easiest to just wipe eMMC and boot from sd card instead Mar 19 16:56:13 How can I tell if eMMC has been flashed? I think I might have done that a year or two ago. Mar 19 16:56:45 (I do recommend wiping eMMC if you intend to boot from sd card, this ensures it will use the bootloader located on eMMC to load the system from sd card, which may cause subtle problems if the bootloader is older than the system) Mar 19 16:57:15 I mean, eMMC will have something flashed on it unless you explicitly wiped it Mar 19 16:57:39 ehh, wait that sentence failed Mar 19 16:57:55 *this ensures it _won't_ use the bootloader located on eMMC Mar 19 17:00:41 I typically use Etcher to flash to SD/microSD cards. Any experience with it? Or do I need to use dd? Mar 19 17:00:53 etcher is generally recommended Mar 19 17:01:38 dd can be used of course, but etcher has the benefit of verifying the image after it has been written Mar 19 17:02:43 Is there signature files? I'm trying to verify my download. Mar 19 17:03:10 the download should already be via https Mar 19 17:03:30 Yes, but like PGP signed. Mar 19 17:03:42 and sha256sum values are listed on the download page Mar 19 17:03:47 no Mar 19 17:03:57 (afaik) Mar 19 17:15:48 anyone know the power and frequency range of the Ti WiLink 8 wifi antenna? Mar 19 17:16:38 "wilink 8" is the wifi/bt chipset, not an antenna Mar 19 17:18:22 and the power and frequency range should be basically the same as any other 802.11b/g/n wifi chipset, since those are determined by regulations Mar 19 17:18:31 ok Mar 19 17:24:18 zmatt, this probably not related to beaglebone but do 433/900MHz have FCC ID's? I'm having trouble searching on fccid.io. I'm wondering if FCC ID's are not applicable at those frequencies. Mar 19 17:24:58 the wilink module does not operate at those frequencies Mar 19 17:26:04 I know, but I'd like to connect the beaglebone to LoRa transceivers. Mar 19 17:27:53 those should definitely have FCC IDs, if modular certification is being used (like with the wilink module), otherwise you'll have to get it all certified yourself Mar 19 17:28:35 note also that co-locating another RF transmitter/receiver next to the wilink module will iirc invalidate its modular certification Mar 19 17:31:08 sorry, just transmitters Mar 19 17:32:22 anyway, I'm not an expert on all this Mar 19 17:32:38 ok thanks for your help Mar 19 17:56:50 oh wow, the esp32's pinmux can route any io to pad any peripheral input and any peripheral output to almost any io pad (six that are input-only)... that's a big pile of muxes Mar 19 17:57:05 *six are Mar 19 17:58:03 I guess it helps that it doesn't have a lot of io pads Mar 19 18:16:48 Ok, so I finally found my miniUSB cable and powered on my BBB. No microSD was inserted and it booted up, so the eMMC was flashed for sure. I can't access the web server, I can't ping the 192.168.7.2 address even. LEDs are blinking and I can access the drive, what might be wrong? Mar 19 18:27:52 I did the driver installation, which stated that it wasn't required, but just to be sure. Mar 19 18:30:07 Also, how do I shut this thing down beyond pulling the plug? I can't SSH to shut it down so... is there a button I press? Mar 19 18:56:17 galaxie, did you try to check which new network interfaces your PC's got? It could be 192.168.6.2 or 192.168.8.2 as well (can't remember which is for what). Mar 19 19:04:37 Knaldgas: I did ifconfig but nothing unusual showed up. Mar 19 19:05:27 Try to unplug, then replug the BBB (Black or Blue btw?) Mar 19 19:05:29 are you running a recent image? Mar 19 19:06:03 if the contents of eMMC is unknown, you may want to reflash with the latest stretch-iot image Mar 19 19:06:06 Well, not from eMMC, but I've been trying to run from SD and that's not working. Mar 19 19:06:55 if the contents of eMMC might be obscure or ancient, try powering on with the S2 button held down (the one closest to the sd card slot) when booting from sd card. you can let go of the button once the power led has turned on Mar 19 19:07:15 BeagleBone Black Industrial, by element14. Mar 19 19:07:32 this ensures any bootloader on eMMC is bypassed and the one on sd card is used instead Mar 19 19:07:44 zmatt: I tried that, but only the power LED lits up. Mar 19 19:08:07 sounds like your sd card is not correctly programmed, or simply misbehaving Mar 19 19:10:16 Well, I flashed the latest stretch-iot but with an older form of Etcher, because they switched their repos. Mount is showing some weird output, though. Let me paste that somewhere.. Mar 19 19:11:32 Here: https://pastebin.com/WqB79hS7 Mar 19 19:11:50 I have the microSD card plugged in through some sort of USB adapter that fits both SD and microSD cards in it. Mar 19 19:12:33 uhhh Mar 19 19:12:49 Maybe I should update Etcher then reflash to microSD? Mar 19 19:13:17 is sde supposed to be the card? why does it have two partitions? and why does it look like the second partition is mounted twice? (I hope that's just a bind mount or something) Mar 19 19:14:04 My machine does weird things, it often mounts things twice I believe. I'm not sure what's the actual card, but that's the only USB thing plugged in. Mar 19 19:14:34 I'll assume it's just a bind mount, since I think the kernel would prevent mounting the fs twice Mar 19 19:14:35 On pcmanfm it shows boot and then rootfs twice. Mar 19 19:15:16 however I don't understand why it looks like it has two partitions (fat + ext4). there should be only one partition (ext4) Mar 19 19:16:02 That might be one of the issues, then? Perhaps I should wipe it with gdisk or whatever then reflash after updating? I have to go soon. Mar 19 19:16:40 normally flashing an sd card completely overwrites its contents, including the partition table Mar 19 19:17:27 anyway, since this is looking weird as hell, and the beaglebone is not booting from it, I'm inclined to assume the card is not correctly flashed for whatever reason Mar 19 19:17:39 but I kinda have to go too Mar 19 20:29:42 galaxie, what command are you using to write the image to the SD card? Mar 19 20:30:09 \o Mar 19 20:30:52 don't you need to use 'dd' so it copies the hidden MLO image? Mar 19 20:32:17 * goes off to see what etcher does Mar 20 01:15:31 What's the best framework for communicating between the DSP and ARM chip on the Beagleboard XM? Mar 20 01:30:08 OK, so I finally realized that my USB to SD was faulty or at least didn't work with Etcher, so that issue is fixed, hurray. Mar 20 01:32:05 Unfortunately, I can't connect to the web server. I'm using the Debian image. My first hunch is the firewall is acting up, I see there's mDNS and stuff. What iptables rules do I need to configure? Mar 20 01:38:11 Oh, and this is the BeagleBone Black Industrial. Mar 20 01:38:53 there should be no iptables rules unless you did something Mar 20 01:40:59 Uh, I use iptables for my firewall. You mean udev? I did install it last year.. should I remove it? Mar 20 01:43:39 what ? Mar 20 01:43:50 I mean that there are no iptables rules at startup on a regular linux box Mar 20 01:43:57 so if there is a firewall acting up, then it's the rules you set up Mar 20 01:44:01 if you set up any rule at all Mar 20 01:45:13 No, iptable rules on my laptop, which is powering the BBB via miniUSB. I'm trying to get the virtual Ethernet/RNDIS/whatever it is working. Mar 20 01:45:25 right Mar 20 01:45:32 well try to also remove them Mar 20 01:46:58 All rules flushed. I don't see any filtered traffic from the BBB though, anyways. I think it's the RNDIS or whatever. Mar 20 01:49:43 yeah Mar 20 01:49:56 well you have an address on the ethernet adapter on your laptop ? Mar 20 01:50:21 It's not showing up, no. Mar 20 01:50:48 no adapter at all ? even with no address Mar 20 01:50:54 if that's the case it's not a firewall issue no Mar 20 01:50:58 rather an issue with the board itself Mar 20 01:51:11 or maybe with your computer but I'm sure you have all the required kernel modules Mar 20 01:51:21 That's what I figured. Now, rndis is showing up as registered in dmesg.. that's what's confusing me now. Mar 20 01:51:38 yeah but it's not rndis is it ? Mar 20 01:51:42 it's cdc-ether Mar 20 01:52:08 That's registering, too. Mar 20 01:52:20 good Mar 20 01:52:26 maybe something with the board then Mar 20 01:53:18 It worked last year, I don't know what's wrong. Mar 20 01:54:26 you tried rebooting the board? Mar 20 01:55:04 Yes, just did. Still nothing. But still registering. Mar 20 01:57:12 so when you do ip addr you don't see the interface Mar 20 01:57:17 What if I connected the BBB to my router directly through Ethernet? What would it's IP address be then? Mar 20 01:57:40 something the router will attribute it Mar 20 01:57:48 if the bbb does dhcp automatically Mar 20 01:57:51 I guess it does Mar 20 01:57:52 Oh, ip addr? I was using ifconfig. Uh, I'm getting lines like enx84eb18e20b05: mtu 1500 qdisc noop state DOWN group default qlen 1000... Mar 20 01:57:57 ah Mar 20 01:58:01 but then an interface is here Mar 20 01:58:02 it's good Mar 20 01:58:04 you just need an address Mar 20 01:58:13 do dhclient -v enx84eb18e20b05 Mar 20 01:58:15 as root Mar 20 01:59:03 Well, that worked. I forgot to add the -a flag to ifconfig. Alright, well, good night! Mar 20 01:59:17 good night ! **** ENDING LOGGING AT Wed Mar 20 02:59:57 2019