**** BEGIN LOGGING AT Thu Aug 17 03:00:00 2017 Aug 17 03:15:35 anyone have I2C exp with beagle, and know what the pull-up resistors should be? Aug 17 03:20:50 5.6K should work **** BEGIN LOGGING AT Thu Aug 17 04:44:25 2017 Aug 17 10:01:46 Does anyone know where to find good a reference on NTSC video signals? Aug 17 10:58:31 Hi - I booted off the eMMC and bricked my BBB. I can boot via the uSD card - can I get at the eMMC stuff? Aug 17 11:07:31 Peter_L: yes Aug 17 11:17:33 zmatt: how can I do this? Aug 17 11:18:18 mount /dev/mmcblk1p1 /path/to/mountpoint Aug 17 11:18:34 (mountpoint should be some empty directory) Aug 17 11:18:41 OK - then? Aug 17 11:19:05 then the eMMC filesystem is accessible through that mountpoint Aug 17 11:19:47 e.g. /boot/uEnv.txt on the eMMC would be /path/to/mountpoint/boot/uEnv.txt Aug 17 11:20:09 - you mean that /mountpoint is now the eMMC filesystem? Aug 17 11:21:10 that's what I said Aug 17 11:21:44 I'm being cautious because I don't want to foul things up worse. Thanks very much Aug 17 12:12:11 Is it right that I can't reprogram ROM area of BBB? I need to have specific functionality into the very first boot code Aug 17 12:13:38 yankovic: afaik you can't right Aug 17 12:15:05 yankovic: the ROM is literally that, it's read-only memory integrated into the AM335x's design Aug 17 12:16:31 on at91, if you have NOR memory it bypasses the integrated ROM loader. no idea about something comparable on AM3xxx Aug 17 12:17:55 there's a "fast xip" boot mode available if you connect NOR flash Aug 17 12:18:17 ah. guess that counts as "comaprable" Aug 17 12:18:19 in which case ROM will jump to the external code earlier than typical Aug 17 12:21:28 (e.g. PLLs are not setup) Aug 17 12:21:58 nothing like that warm feeling in the guts, setting up every pll and and memory yourself, right? Aug 17 12:22:25 setting up the PLLs isn't difficult Aug 17 12:23:16 and the memory controller is never configured by ROM regardless of boot mode Aug 17 12:23:27 LetoThe2nd zmatt: thanks Aug 17 12:23:31 most things hidden away in libraries and third party code are not super complex in the end, but i still don't want to redo everything Aug 17 12:23:39 (ROM relies solely on on-chip SRAM) Aug 17 13:44:25 hi , i am not able ssh via putty Aug 17 13:44:28 need help Aug 17 13:44:54 after connecting via putty , it says connection refused Aug 17 13:45:25 @av500 Aug 17 13:49:26 hello kayatwork Aug 17 13:49:38 need help Aug 17 13:49:46 i am not able ssh BBB via putty Aug 17 13:49:53 after connecting via putty , it says connection refused Aug 17 13:50:31 kindly suggest Aug 17 13:50:48 santy: if nobody answers, probably nobody knows. please do not ask every nick that you see join again. thank you. Aug 17 14:00:47 connection refused means the destination device sent a TCP reset in response to the SYN. Aug 17 14:02:48 typically IPTables is set with drop instead of reject for an action for blocked ports, so its likely the port is not blocked or there are no IPTable rules. Most likely sshd is not running on the port in question. Aug 17 14:25:57 more likely he's trying to connect to the wrong ip Aug 17 18:50:45 if i need to change pin muxing, e.g., from uart1 tx to gpio, do i ONLY need to change the appropriate dts/dtsi file, or do i also have to modify .c (source) code somewhere in the kernel tree? Aug 17 18:51:11 join ##kernel Aug 17 18:51:21 doh! Aug 17 19:03:43 yates: yes, dtb should be enough Aug 17 20:26:36 is it possible to run from sd card like a raspberry pi? Aug 17 20:31:56 zarzar: yes Aug 17 20:33:19 zarzar: It should just be a matter of dd'ing an appropriate omage to the SD card Aug 17 20:33:26 it's even better than RPi as it doesn't require all the binary crap and boot process is pure open source components Aug 17 20:33:45 s/omage/image Aug 17 20:34:01 also holding down the button or nuking MLO from eMMC Aug 17 20:35:18 so usually the image is copied from sd to emmc, then reboot with sd removed and the bbb runs from emmc Aug 17 20:35:43 not sure how to change that process to run from sd card without copying to emmc Aug 17 20:35:59 "nuke MLO on eMMC" Aug 17 20:36:22 then the board automatically will only boot from SD card Aug 17 20:36:36 and make sure it's not a "flasher" image Aug 17 20:38:36 "nuke MLO on eMMC" results are mainly for booting from emmc Aug 17 20:40:13 basically overwrite the first megabyte of eMMC with zeroes Aug 17 20:40:29 you can partition it and use it for storage of course Aug 17 20:40:59 so wipe out data on emmc Aug 17 20:41:12 erase emmc ? Aug 17 20:41:33 yes, the relevant part, MLO is at fixed offsets at the beginning of the device Aug 17 20:43:21 so i guess ROM looks at emmc first, then sd card? Aug 17 20:54:53 thanks for pointing me in the right direction tbr Aug 17 20:55:01 gotta run Aug 17 23:04:28 is it documented somewhere how the dts files, u-boot, and the kernel interact? Aug 17 23:04:41 for example, does uboot read the dts file and set up gpio mux selection and, if output, initial output? Aug 17 23:05:01 or is that deferred to some place in the kernel startup? Aug 17 23:05:11 or does the kernel keep the gpios "safe" (tristated) until a command from userland (e.g., via sysfs) comes along? Aug 17 23:05:26 we are having a problem with our imx6 processor (actually a Variscite DART 6UL SoM) getting really hot on our own custom board while booting linux and need to ensure the reason is not contention in the GPIOs aor other interface signals. Aug 17 23:06:02 zmatt: how are you, my friend? Aug 17 23:15:04 is this thing on? Aug 17 23:38:47 yates: u-boot might configure some pins, but most of it will be left to the kernel (based on DT) Aug 17 23:54:19 Mmmmmm IMX6 Aug 17 23:55:03 btw, which IMx6? Aug 18 02:07:02 has anyone tried streaming a asus RGBD cam using ROS from a beaglebone? Aug 18 02:58:57 is it possible to build via yocto the same type of image as the prebuilt images, *.img.xz **** ENDING LOGGING AT Fri Aug 18 03:00:01 2017