**** BEGIN LOGGING AT Thu Feb 04 02:59:59 2016 Feb 04 04:06:45 veremit: it's virtualization, not simulation :P Feb 04 04:07:38 it could be useful to split the cpu between an RTOS and Linux Feb 04 04:07:49 assuming the former isn't particularly RAM hungry Feb 04 04:08:36 If that's what you want, use a hypervisor to run two hyper-processes, one an RTOS kernel, one Linux. Feb 04 04:08:44 (TrustZone could be used for the same purpose, which is one of the reasons it pisses me off that TI renders it unusable) **** BEGIN LOGGING AT Thu Feb 04 04:10:39 2016 Feb 04 11:54:11 panto: may I suggest a better error for when capemgr does not find the firmware ? I just forgot update-initramfs xD Feb 04 12:00:37 dwery, yeah, a lot of things are changing Feb 04 12:01:36 panto: noticed :) I'm trying to port a dts to 4.1.. it just oaded but devices are not kicking in Feb 04 12:02:27 dwery, err, you do know I keep a tree against mainline don't you? Feb 04 12:03:04 panto: yes.. I just fall a bit behind Feb 04 12:03:21 got a lot of "could not find pctldev ".. any suggestion? Feb 04 12:03:44 https://github.com/pantoniou/linux-beagle-track-mainline Feb 04 12:04:08 pctldev? maybe that's a phandle reference? Feb 04 12:07:22 guess so. I'm checking the dts, device tree at al. Feb 04 12:08:17 dump the dtbo with fdtdump Feb 04 12:08:22 that might give you a clue Feb 04 12:12:00 panto: c_can_platform 481d0000.can: could not find pctldev for node /ocp/ocmcram@40300000, deferring probe Feb 04 12:12:06 something is not yet loaded it seems Feb 04 12:12:19 yeah Feb 04 12:12:30 panto: my cape has an eeprom and it is trying to enable can1 Feb 04 12:13:53 there a problem with the can device Feb 04 12:14:02 it's got nothing to do with the overlay Feb 04 12:14:06 oh :D Feb 04 12:14:18 ocmcram@40300000 is not enabled Feb 04 12:14:31 there's a reference to it from the can device node Feb 04 12:14:51 anything I should do enable it? Feb 04 12:15:02 the can driver defers the probe hoping for it to be enabled eventually Feb 04 12:15:17 find the node and see if it Feb 04 12:15:21 's enabled Feb 04 12:15:39 if not enable it in another fragment Feb 04 12:16:04 but how does BB-CAN1-00A) enable it? I can't see anything peculiar init Feb 04 12:19:27 maybe it's supposed to be enabled in the base dts Feb 04 12:20:11 it seems spi has the same problem 481a0000.spi: could not find pctldev for node /ocp/interrupt-controller@48200000 Feb 04 12:20:22 like something is missing before capemgr kicks in Feb 04 12:20:59 I'musing the latest Debian 8.3 / 4.1.15-ti-rt-r43 Feb 04 12:22:20 can you try to load the overlay at runtime? Feb 04 12:22:32 then everything should have been loaded Feb 04 12:22:46 panto: will disable the cape in uenv and see if it works at runtime Feb 04 12:23:01 or can I remove a loaded cape at runtime? Feb 04 12:23:54 -# removed it, nice Feb 04 12:23:56 you can remove it Feb 04 12:26:15 but re-adding doesn't work. will go the uenv route, will let you know. ty. Feb 04 12:37:58 (a reboot doesn't shutdown the opened ssh connection corretly.. I must admit I feel this Debian 8.3 much less stable than the older one) Feb 04 12:40:25 panto: runtime probning gives a write error: No such file or directory . while echo BB-CAN1 works. There's no indication in what went wrong in dmesg. Feb 04 12:43:41 panto: file naming problem, dts loaded. ocrcram still missing, and spi has some missing bits too. bbl Feb 04 14:42:45 dwery: about the ssh connection thing, that's a config issue: enable UsePAM in the sshd_config to fix Feb 04 14:43:36 zmatt: ty Feb 04 14:44:17 that will ensure a proper session is setup/registered with systemd, and that in turn will get properly terminated before network is lost on shutdown Feb 04 14:44:49 I need to remember to pounce rcn-ee to fix that Feb 04 16:36:57 what is your favorite development system for the Beaglebone black and it's pru's? Feb 04 16:37:16 The BeagleBone Black itself. Feb 04 16:37:46 Having a Linux desktop/laptop is handy. Even a Chromebook is good enough. Feb 04 16:43:04 I have had some success with qt creator, but because I need to use the pru's I tried to get the TI ccs working, but I'm stuck - it only compiles bare metal executables Feb 04 16:43:49 maybe I should go back to Qt and stick a pru compiler on to it Feb 04 16:53:52 Hello Feb 04 16:54:03 hi Feb 04 16:54:58 what's your name? Feb 04 16:55:49 ? Gaseous Farticus Feb 04 16:55:52 I have a BB and I need to make the installation of the Debian operating system on board, could you help me? Feb 04 16:57:32 http://beagleboard.org/getting-started Feb 04 16:57:37 did you read that? Feb 04 16:57:52 http://beagleboard.org/getting-started#update Feb 04 16:58:32 I'm opening here Feb 04 16:59:13 Yeah! It did not help me at all Feb 04 17:07:17 I'm wanting to put Debian Operating System Feb 04 17:07:57 these two link that u sent me not speak any OS installation Feb 04 17:09:50 of course they do Feb 04 17:11:09 yes they do so, the problem I'm not able to install the Debian Operating System Feb 04 17:18:28 all you have to do is write a micro-SD card .. can you manage that? Feb 04 17:20:45 I put the picture in SD and then the off BeagleBone put the card and called the BeagleBone more nothing happened Feb 04 17:21:35 is it possible to use qemu to run the debian installer to install to a sd card? Feb 04 17:21:46 qemu? Feb 04 17:21:48 what for? Feb 04 17:21:55 just write the SD image to the sd card Feb 04 17:21:59 insert card Feb 04 17:22:21 ...Insert SD card into your (powered-down) board, hold down the USER/BOOT button (if using Black) and apply power... Feb 04 17:23:01 That's it. I want to use the SD card to install the Debian Operating System Feb 04 17:23:02 that should at least boot the latest image off the card Feb 04 17:23:12 so you need a "flasher image!" Feb 04 17:23:16 av500: you mean write the debian net-installer image to the sdcard? but i want to have debian installed on the sdcard. does it overwrite the space where the image was? Feb 04 17:23:25 sorry? Feb 04 17:23:42 if you write a debain image to a card, you will have debian on a card Feb 04 17:24:00 if you write a flasher image, it will upon boot flash to image to the BBB Feb 04 17:24:09 the image* Feb 04 17:25:15 oh I see what you mean. Yes I understand that. What if I want to do a fresh install of debian to an sdcard, is that possible? Is it a bad idea? That's why I was thinking to use qemu Feb 04 17:25:29 define "fresh install" Feb 04 17:25:53 all I can tell you how to get a "known to work" debian onto the BBB Feb 04 17:25:57 you is* Feb 04 17:26:07 By fresh install I mean walk through the net installer, choose partition size, choose what I want to have installed... like I would normally do for an x86 install Feb 04 17:26:24 no idea, I never used debian Feb 04 17:26:27 actually I have a beagleboard-xm. I'm just trying to get ideas Feb 04 17:27:18 The flasher is already installed Feb 04 17:27:34 you can't and/or dont' really want to do a x86 build on an arm board ;) Feb 04 17:27:35 I want to install Debian Feb 04 17:27:48 that's alright. I did manage to get debian installed but I had to use some kind of mkimage script. When I first started this, I wanted to use qemu to run the debian installer but I always just got a black screen Feb 04 17:27:49 not to mention .. the install process is subtley different, so its much easier to use a pre-baked official image Feb 04 17:29:01 the memory card layout is fairly important for successful boot Feb 04 17:29:13 Debian installation is done from the command line? Feb 04 17:29:15 so .. as long as you use a sensible sized memory card .. there is no particular issue Feb 04 17:29:45 if you're concerned about pre-installed packages .. start with a "console" image and work up Feb 04 17:29:47 Debian installation is done from the command line? Feb 04 17:29:55 veremit: I've got a 2 Gb card. does that seem sensible? Feb 04 17:30:09 mikedh: I'd consider that a minimum Feb 04 17:30:15 I also have an 8 Mb card but i figured that'd be pushing it Feb 04 17:30:31 lol yeah probably .. your kernel image is probably gonna fill that :p Feb 04 17:30:33 I have a 8gb Feb 04 17:31:29 want to know how does the installation for SD Card Feb 04 17:31:51 It is not the flasher Feb 04 17:34:34 how do I do that? Feb 04 17:34:48 help me Feb 04 17:37:12 help me Feb 04 17:37:56 Bone__: ? Feb 04 17:38:06 help me Feb 04 17:38:07 you have an 8GB card with a valid image on it? Feb 04 17:38:28 I need to install Debian on BBB Feb 04 17:38:33 Bone__: say "help me" one more time and I'll boot you. please try to stay constructive. Feb 04 17:38:44 yes Feb 04 17:39:03 okay... http://beagleboard.org/project/debian of any help? or http://beagleboard.org/latest-images Feb 04 17:39:04 ? Feb 04 17:40:39 It has downloaded this image this link http://beagleboard.org/latest-images Feb 04 17:42:06 yes Feb 04 17:42:42 http://beagleboard.org/getting-started#update instructions not clear enough? Feb 04 17:42:49 'm already with the image on the SD card Feb 04 17:43:15 no Feb 04 17:46:43 help me Feb 04 17:47:25 If using BeagleBone Black and desire to write the image to your on-board eMMC, you'll need to follow the instructions at http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC. When the flashing is complete, all 4 USRx LEDs will be steady on or off. The latest Debian flasher images automatically power down the board upon completion. This can take up to 45 minutes. Power-down your board, remove the SD card and app Feb 04 17:47:25 ly power again to be complete. Feb 04 17:47:33 comes from that page... Feb 04 17:48:01 again, that's the last time you'll get "help me" out on this channel without getting booted. See http://beagleboard.org/chat for rules of engagement. Feb 04 17:48:15 I do not want to install the not flash Feb 04 17:48:34 so, you want to simply run off the microSD... Feb 04 17:48:49 *but* you have an eMMC flasher image that would otherwise program your eMMC? Feb 04 17:48:58 I think you did not understand until now what I MAKE THE SYSTEM INSTALLATION OPERATING DEBIAN SO THAT is not the flasher Feb 04 17:49:32 on the microSD card, there is a file in the Linux partition called /boot/uEnv.txt. Feb 04 17:49:34 -facepalm- lol good luck guys Feb 04 17:49:50 Bone__: see.... this line: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC Feb 04 17:50:02 ##enable BBB: eMMC Flasher: Feb 04 17:50:02 cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh Feb 04 17:50:15 Change those two lines to: Feb 04 17:50:17 ##enable BBB: eMMC Flasher: Feb 04 17:50:17 #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh Feb 04 17:50:38 that's about as baby stepped as I can make it without losing my sanity. Feb 04 17:53:27 I will refrain from making remarks about young children and feeding methods .. oh woops .. Feb 04 18:06:51 putting the debian image on was easy for me - then I found out quick that I had to partition the emmc so make room for added apps Feb 04 18:07:41 usually the emmc is max'd out by the setup script Feb 04 18:07:56 thats not quite the same for uSD cards though Feb 04 18:08:01 rather than writing an image to a disk, can I just copy all the boot files to the first partition of the sdcard? Feb 04 18:08:22 mikedh: not if you want it to boot correctly :p Feb 04 18:08:29 as I understand it the first partition needs the MLO, uboot, and the linux kernel image Feb 04 18:08:40 what else is there? Feb 04 18:08:59 I thought there was some magic still needed for the location of some binaries .. but perhaps that's been ... "corrected" Feb 04 18:09:22 is there still a fat partition for the bbb? I don't remember Feb 04 18:10:11 I'm working with a beagleboard-xm if that makes a difference. from what i've read online the bbxm will look for MLO on the first partition and boot from there Feb 04 18:10:28 but I'm still very new at all this so I'm figuring it out as I go along Feb 04 18:14:32 ah is the xm the "other" processor .. or is it still the am335x Feb 04 18:14:41 I'm struggling with Code Composer Studio v6 - when I make a new project for Beaglebone Black it sets the compiler to build a bare metal executable - how do I select to build a 32 bit Linux binary? Feb 04 18:14:47 but yeah .. first partition, mlo used to be on fat partition Feb 04 18:15:11 my BBB is running Debian Feb 04 18:15:20 twoten: sounds like your target is wrong Feb 04 18:15:47 most people would likely just gcc the source .. possibly even on the target :) Feb 04 18:19:55 yeah I was thinking that - I could go back to Qt creator and tell it to save my project on the BBB and run gcc there too Feb 04 18:22:00 there are -ways- to cross compile . else we'd have no kernels :D Feb 04 18:24:54 yeah I hit a wall there too - it's hard to tell where's the best place to exert one's sysiphisian labor Feb 04 18:25:29 veremit: bbxm has an AM37x. not sure if that makes a difference Feb 04 18:32:48 it makes a huge difference for low-level stuff, but not for (cross-)compiling linux applications Feb 04 18:33:09 and I thought it was a DM37xx rather than the AM edition? Feb 04 18:33:39 (if you dig deep enough you can also still find references to its old name, OMAP37xx) Feb 04 18:49:03 so if I wanted to emulate a bbxm system using qemu-system-arm, does anyone know what machine I would specify? does the machine make a difference? Feb 04 18:50:52 mikedh: depends on how accurate you need the emulation to be... Feb 04 18:51:34 mikedh: but i don't see a machine target for beagleboard-xm qemu 2.1 ... not sure if newer versions have it Feb 04 18:52:21 mikedh: machine "beagle" (cpu omap3) is closest you'll get I think Feb 04 18:52:51 mikedh: note that it's not in mainline qemu afaik, but it is in linaro's qemu tree Feb 04 18:53:05 well I see that https://wiki.linaro.org/Resources/HowTo/Qemu-beagleboard provides a version that allows machine beaglexm Feb 04 18:53:15 ah well there you go then Feb 04 18:56:21 it's noteworthy that omap3.c is by far the largest file in https://git.linaro.org/qemu/qemu-linaro.git/tree/HEAD:/hw/arm Feb 04 18:58:41 zmatt: thanks, that's what I was looking for Feb 04 18:59:29 Nokia clearly put a lot of effort into this Feb 04 18:59:51 zmatt: like theeffort they put in musb .. Feb 04 19:02:22 veremit: I'm not sure whether that statement was meant seriously or sarcastically, mostly since I don't know whether the linux musb driver is dealing with the hardware to the best of its ability or not Feb 04 19:03:07 zmatt: technically complete statement .. +2 :D Feb 04 19:03:28 I don't think it was nokia's fault .. I'd direct more abuse towards mentor graphics tbh :) Feb 04 19:03:42 but I think it was them to deploy it mainstream Feb 04 19:03:45 who* Feb 04 19:03:50 w * Copyright 2005 Mentor Graphics Corporation Feb 04 19:03:50 * Copyright (C) 2005-2006 by Texas Instruments Feb 04 19:03:50 * Copyright (C) 2006-2007 Nokia Corporation Feb 04 19:04:06 oo so we get to rally some abuse to TI :D Feb 04 19:04:41 to be fair, I think a significant amount of trouble is actually caused by TI's phy Feb 04 19:06:15 and the lovely CPPI 4.1 DMA engine of course, if you choose to enable it (lol) Feb 04 19:07:05 not to be confused with the CPPI 3.1 DMA engine that's in the Ethernet subsystem, which does not even remotely resemble CPPI 4.1 Feb 04 19:07:22 (the Ethernet DMA is quite sane) Feb 04 19:08:40 the BBB is probably also causing its own share of problems, especially with things like wifi sticks Feb 04 19:09:20 by having omitted the semi-obligatory large cap on the usb 5V (on the _output_ side of the power switch) Feb 04 19:09:46 thus increasing the risk of dipping the 5V, which causes the OTG phy go nuts Feb 04 19:11:30 but there are driver bugs there too, since the port fails to recover on its own after that... but again the issue might be specific to TI's phy rather than to musb in general Feb 04 19:13:18 ok, really need to kick myself to the supermarket... bbl Feb 05 00:43:24 hmm, I probably only further added to the confusion by trying to explain BCH codes in terms of fourier analysis Feb 05 00:53:20 who doesn't understand fourier and laplace?! Feb 05 00:54:50 https://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/467975/1761244#1761244 Feb 05 00:56:26 (of course an "all-pole IIR filter" over GF(2) is exactly the same as an LFSR) Feb 05 01:00:38 I like the fourier viewpoint though... makes it immediately obvious that cyclic codes (such as CRCs) are good at catching burst errors, since those will have a broadband spectrum hence no or negligible chance of leaving some particular spectral line untouched Feb 05 01:49:08 Hi. I'm trying to create a custom Ubuntu image for my BeagleBone Black Feb 05 01:49:08 At the moment I'm reading through http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 trying to understand what's necessary to put on the SD card in order to flash it into the internal eMMC. Feb 05 01:49:13 Does the structure of the SD card need to match exactly what goes into the eMMC so that when I press & hold the boot button, it flashes exactly what's on the card, or does the flash process have some built-in intelligence that puts the boot loader & such in the right place? Feb 05 01:49:13 Also, is there any risk of permanently bricking the BBB through the flashing process, or will it continue to work regardless of whether I mess up what's in the eMMC? Feb 05 01:50:26 you can't brick a BBB by writing bogus data to eMMC Feb 05 01:50:54 if you power up with the S2-button held down then the ROM bootloader will in fact entirely ignore eMMC Feb 05 01:53:51 I don't really know anything about the flasher script Feb 05 02:22:55 zmatt: I thought if you kept holding the button it would flash the eMMC. Or is that simply a feature of the SD image? i.e. When you boot from SD, it looks to see if the button is still pressed, and if so, invokes the flasher script. Feb 05 02:23:37 the S2 button is read by the am335x processor on power-up to define the source of bootloader Feb 05 02:23:51 nothing more, nothinig less. Feb 05 02:24:18 well, in theory the system is *able* to check the button after that (provided it doesn't enable the display output) Feb 05 02:24:28 but it doesn't as far as I know Feb 05 02:25:02 whether the SD card proceeds to flash eMMC normally depends on whether the SD card contains a flasher or a standalone image Feb 05 02:25:31 OK - make sense Feb 05 02:25:45 *makes Feb 05 02:27:19 zmatt: in fact, merely the contents of the /boot/uEnvt.txt I believe .. Feb 05 02:27:26 whether init is set to the flasher script or not Feb 05 02:27:30 veremit: yeah true Feb 05 02:27:46 So does that mean also that my original question (about how to set up the SD card ready for flashing eMMC) also depends on the script on the SD card? Feb 05 02:28:16 blahdeblah: you could do worse than to look at that script ;) Feb 05 02:28:34 but that's the 'doing' end .. not the 'creating' end Feb 05 02:28:49 the whole lot is in RN's git repo though Feb 05 02:29:21 I suppose 500 lines isn't that large to read through Feb 05 02:30:04 https://github.com/RobertCNelson/omap-image-builder Feb 05 02:46:06 What distributions are being used with Beaglebone Black for Industrial applications? **** ENDING LOGGING AT Fri Feb 05 02:59:59 2016