**** BEGIN LOGGING AT Sun Aug 20 03:00:01 2017 Aug 20 04:20:43 PWM as audio? Aug 20 04:21:59 maybe… for playing mod files? Aug 20 04:22:10 mod files may work Aug 20 04:22:15 I was using it for speech Aug 20 04:22:35 probably do better using a serial out Aug 20 04:23:08 I suspect for music, you need to be a little bit more complex (put a filter in there and run it as a higher sample rate Aug 20 04:23:16 no, PWM is fine Aug 20 04:23:37 I was doing a very basic setup w/min. HW (emitter follower and letting the headset do the LPF) Aug 20 04:24:00 for music, you probally want to put in at least a 1-2 pole filter Aug 20 04:24:56 IIRC - mods aren't very demanding audio wise Aug 20 05:24:07 what's the difference between vdd_5v and sys_5v? Aug 20 07:56:25 MagusOTB: the former connects directly to the 5v barrel connector, can be used to power the bbb (if no adapter is connected) or draw power (if an adapter is connected) Aug 20 07:56:46 if powered via usb, you cannot draw power from vdd_5v Aug 20 07:58:32 sys_5v is available regardless of how the bbb is powered, but the amount of current you're allowed to draw is more limited Aug 20 07:58:55 also, when powered off (by software command), sys_5v goes down Aug 20 12:11:57 Hi! On my BeagleBone Black I run Debian 9.1 with Kernel 3.8.13-bone 50. I try to update to Kernel 4.9.44-bone7 by command /opt/scripts/tools/update_kernel.sh --lts-4_9. The new Kernel is downloaded and installed to /boot. But it doesn't boot to it. What do I need to fix it? Aug 20 12:28:12 uhhh, debian 9.1 with kernel 3.8 .. what? Aug 20 13:45:51 zmatt: I started with Debian 7.5 a time ago. When I upgraded to 9.1 the Kernel didn't get updated Aug 20 13:54:47 you probably have an old sd-card geometry with MLO on FAT Aug 20 13:55:07 I'm not sure what the transition/upgrade procedure is for that Aug 20 13:55:25 RCN probably would know Aug 20 13:56:18 make a backup of important stuff and start from a clean slate? ;P Aug 20 13:57:01 yes, that would have been also my course of action. I do sense a slight aversion to this though. ;) Aug 20 13:58:58 while I could probably *do* the necessary surgery I wouldn't feel comfortable trying to talk anyone through it :P Aug 20 15:19:17 Hi, I'd like to erase all partitions on the emmc, any idea how to do it? Aug 20 15:19:21 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 8192 6963199 6955008 3.3G 83 Linux Disk /dev/mmcblk1: 1.8 GiB, 1920991232 bytes, 3751936 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 Aug 20 15:24:07 a bit better described, is there a tool how to erase the partitions on the flash of the BBB? Aug 20 15:24:40 because I would need the full space, so that I can flash Debian on the EMMC flash of the board Aug 20 15:30:33 Franz_: normally if you run a flasher it will completely reformat the eMMC anyway Aug 20 15:33:08 thanks, then it must be a different problem then, since I can run Debian from the SD drive, but flashing does not work Aug 20 15:33:21 the LEDs show the typical 1-2-3-4.. pattern Aug 20 15:33:30 and then the LED flash at the same time Aug 20 15:33:47 when I disconnect the SD card and start again, the board does not boot up Aug 20 15:33:50 any idea? Aug 20 15:34:14 I thought it's that the internal drive is not large enough and therefore the flashing does not work Aug 20 15:34:15 although it's hard to say from what you're pasted (please don't paste multi-line text in irc, next time use pastebin.com or such), it looks like you have an older BBB with only 2GB of eMMC and are probably trying to flash a 4GB image onto it? Aug 20 15:34:45 I guess I need to get a mini HDMI cable, so that I can see what's happening during the flashing - does this make sense? Aug 20 15:35:13 I have no idea if the flasher produces any output on hdmi Aug 20 15:35:14 well, this is a good point Aug 20 15:35:34 I have the REVB5 board Aug 20 15:35:59 and when I type in the command fdisk -l Aug 20 15:36:03 I get following output: Aug 20 15:36:28 so this makes sense then Aug 20 15:36:42 1.8G 83 Linux Aug 20 15:36:55 so I need a new BBB with a larger space then, it seems Aug 20 15:36:58 B5 ? there's a rev B but not B5 Aug 20 15:37:13 yes, RevB5 Aug 20 15:37:22 PCB RevB5 Aug 20 15:37:34 oh wait right, pcb has its own revisions Aug 20 15:38:04 latest is B6, so yeah you have some version with 2GB Aug 20 15:39:03 and, well, if you need more than 2GB of space then yes you'll need to get a current revision BBB. for lots of purposes 2GB is plenty Aug 20 15:39:37 yes, and this is explains, why it did not work, thanks, then I just stick to the SD card and I am fine Aug 20 16:17:09 moin Aug 20 19:11:41 anyone suggest a product for debugging the sitara via the BBB's unpopulated jtag header? Aug 20 19:26:37 you mean which jtag debugger? xds100v2 would be the obvious choice Aug 20 19:30:36 be aware there are variants with different connectors, you'll want the version with the compact 20-pin TI connector that matches the header on the BBB (once you populate it) Aug 20 21:31:55 hey how do i write a executable image to sd card for the BBB? the instructions here are out of my realm of knowledge: https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone Aug 20 21:50:04 hi i am getting this error when trying create file system on sd card for BBB exeutable image Aug 20 21:50:05 mkfs.vfat: Device partition expected, not making filesystem on entire device '/dev/sda' (use -I to override) Aug 20 21:50:19 I am trying to follow this: https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone Aug 20 21:51:16 getting this error with the -I option: WARNING: Not enough clusters for a 16 bit FAT! The filesystem will be misinterpreted as having a 12 bit FAT without mount option "fat=16". mkfs.vfat: Attempting to create a too large filesystem Aug 20 23:04:05 hi can someone point me to the process to write a executable image to sd card for the BBB? the instructions here are out of my realm of knowledge: https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone Aug 21 00:25:16 zarzar: you should have a partition number on that /dev/sda would be the raw device /dev/sda1 would be the first partition Aug 21 00:25:51 zarzar: that is wrt your error with mkfs.vfat Aug 21 00:33:54 hi freemor Aug 21 00:35:01 i ran this: udo fdisk -lu /dev/sda Disk /dev/sda: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xca52207f Device Boot Start End Sectors Size Id Type /dev/sda1 * 8192 6963199 6955008 3.3G 83 Linux Aug 21 00:36:53 i'm not sure i understand the sda sda1 partitions Aug 21 00:37:02 i'm sure i don't actually Aug 21 00:39:08 freemor: Here's the current state: sudo fdisk -l [sudo] password for nth: Disk /dev/sda: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Aug 21 00:39:29 freemor: nothing at sda1 now Aug 21 00:42:49 ok first and most important question are we 100% sure that sda is what we should be working on.. Aug 21 00:43:03 don't want to be borking a working system Aug 21 00:44:41 freemor, not sure how to verify now that I erased it Aug 21 00:46:24 now i get no such device or directory when i execute this step: sudo mkfs.vfat -F 16 -n "boot" /dev/sda1 mkfs.fat 3.0.28 (2015-05-16) mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows /dev/sda1: No such file or directory Aug 21 00:46:45 lol well since you still have a live system guess you're ok. Aug 21 00:47:08 what system are you doing this work on Aug 21 00:47:31 vm guest ubuntu host windos 10 Aug 21 00:48:23 and what does df -h show (i'll give me an idea of your drive layout) Aug 21 00:48:42 df -h Filesystem Size Used Avail Use% Mounted on udev 3.9G 0 3.9G 0% /dev tmpfs 797M 9.3M 788M 2% /run /dev/sdb1 98G 57G 36G 62% / tmpfs 3.9G 212K 3.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 84K 797M 1% /run/user/1000 Aug 21 00:48:59 sorry for the formatting there Aug 21 00:51:16 yeah thats hard to read.. what is mounted at / Aug 21 00:52:21 udev 3.9G 0 3.9G 0% /dev Aug 21 00:52:21 part of thae problem is those insructions you linked.. seem to have completely left out the partitioning instructions Aug 21 00:52:30 tmpfs 797M 9.3M 788M 2% /run Aug 21 00:52:48 yea the instructions seem to b for advanced users Aug 21 00:52:56 glossing over a whole bunch Aug 21 00:53:13 even for advanced users it is lacking Aug 21 00:53:17 i want to run from sd card with a core image minimal i made via yocto Aug 21 00:54:10 for raspberry pi i use win32 disk imager with a *.sdimg file that yocto builds Aug 21 00:54:38 maybe the bbb build also makes an sd card image but i am not sure which file it is Aug 21 00:56:10 ok what kind of file did yocto spit out for you? Aug 21 00:57:09 there are a bunch Aug 21 00:59:09 lookinng more at those instruction that does not look like a modern boot set-up... Aug 21 00:59:11 core-image-minimal-beaglebone-20170815015324.rootfs.tar.bz2 Aug 21 00:59:18 and this is for a BBB? Aug 21 00:59:30 core-image-minimal-beaglebone-20170815015324.rootfs.jffs2 Aug 21 00:59:45 MLO Aug 21 00:59:52 zImage-beaglebone.bin Aug 21 01:00:01 freemor yes for beaglebone black Aug 21 01:01:02 lots of files generated, not sure if one can be used with win32 disk imager, would be much easier if they could or if there was a simplier way to format the card and load Aug 21 01:01:09 ok let me fire up my BBGW (basically a black with wireless and no hdmi) I want to check the disk structure Aug 21 01:01:21 ok thanks freemor Aug 21 01:01:59 more files: core-image-minimal-beaglebone-20170815215649.rootfs.tar.bz2 , core-image-minimal-beaglebone-20170815015324.rootfs.tar.bz2 Aug 21 01:02:11 MLO-beaglebone-v2016.03+gitAUTOINC+df61a74e68-r0 Aug 21 01:02:39 i was expecting a *.sdimg file or a *.img file Aug 21 01:08:08 ok so as I thought no FAT boot partition Aug 21 01:09:17 it really looks like Yocto is putting out some old stuff there... Aug 21 01:14:00 freemor is that an executable or an image to flash emmc with? Aug 21 01:15:21 the rootfs.tar is an archive of the root file system Aug 21 01:16:08 the jffs2 is probably a partition image (of the root fs Aug 21 01:16:30 the problem is non of this set up a modern Uboot Aug 21 01:16:53 there are uboot files also Aug 21 01:17:06 u-boot-beaglebone.img Aug 21 01:17:32 several uboot related files Aug 21 01:22:05 you are going to have to find someone with Yocto experience WRT modern BB Black boards. Aug 21 01:24:18 what yacto is trying to create is a SD with 2 partitions a fat one with Uboot parts and the and the root FS in a linux partition Aug 21 01:25:29 all the images I've seen have an unpartitioned gap (with the uboot stuff at specific locations in it and then a Single linux partition Aug 21 01:27:01 I'm unsure if the black can boot from the 2 partition set-up that Yocto is sugesting you create. and I'd be unsure how to modify it to make it a newer set-up Aug 21 01:28:12 basically you need someone more BBB guru then I. and probably someone that has played with Yocto Aug 21 01:29:51 ok Aug 21 01:30:24 thanks for checking into it freemor Aug 21 01:30:30 yw Aug 21 01:30:41 wish i could have been more help Aug 21 01:40:17 no worries freemor, i'll figure it out one of these days **** ENDING LOGGING AT Mon Aug 21 03:00:01 2017