**** BEGIN LOGGING AT Wed May 30 03:00:02 2018 **** BEGIN LOGGING AT Wed May 30 07:24:24 2018 May 30 09:58:48 Pulling my hair out trying to get SPI working on my BBBW. I'm running "Debian 9.3 2018-03-05 4GB SD IoT" and have followed instructions to modify my /boot/uEnv.txt to have the line "uboot_overlay_addr4=/lib/firmware/BB-SPIDEV0-00A0.dtbo". After rebooting, I still don't get anything when I ls /dev/spi*. Anyone know what I might be doing wrong? May 30 09:59:17 Do I need to do anything other than rebooting to apply the uboot overlay? May 30 10:05:24 I'm trying to flash eMCC from the microcard. In /boot.uEnv.txt I've got: cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh. Gnd LEDs should do 'galloping' and when the installation is finished the power should go off. Neither happen. May 30 10:08:21 Guest13792: are you holding down the button S2 when powering up the device? May 30 10:17:40 saml212: you don't need to mess with overlays at all May 30 10:18:21 oh? May 30 10:18:29 saml212: if you leave uEnv.txt at its default, the spidev devices will already exist and all you have to do is configure the pins using "config-pin $PIN spi" May 30 10:19:16 however the overlay should still work too, so there's something else wrong May 30 10:19:21 are you booting from eMMC or SD card? May 30 10:19:27 hmm, I booted fresh off the image and they weren't there May 30 10:19:30 SD card May 30 10:19:40 i don't need a SPI device attached for them to appear, do I? May 30 10:19:41 bingo. you're suffering from an old bootloader on eMMC May 30 10:20:03 which is causing both mechanisms (config-pin and overlays) to not work May 30 10:20:19 images should detect that and print out warnings everywhere :D May 30 10:20:31 if you don't care about the contents of eMMC, wipe it with sudo blkdiscard /dev/mmcblk1 and reboot, and your problems shall be gone May 30 10:21:30 aha, I'll try that. I didn't notice any warnings anywhere though, where should have I been checking? May 30 10:21:51 tbr: I agree, it's really annoying that this frequently-occurring situation results in seemingly-successful boot but not a properly working system May 30 10:22:16 saml212: there aren't any afaik May 30 10:22:40 woo, that fixed it. thanks! :D May 30 10:23:03 just out of curiosity, what was the issue? that the bootloader was out of date and couldn't apply the overlays? May 30 10:23:09 yes May 30 10:23:18 old u-boot on eMMC takes precedence over the new u-boot on SD card May 30 10:23:35 and it booted from emmc first, but then switched to SD card for rootfs etc May 30 10:23:51 and while this old u-boot does manage to boot linux from sd card, it doesn't understand most of the config vars in a modern /boot/uEnv.txt May 30 10:24:04 if you'd have pressed down S2, it would have used the sd-card U-boot May 30 10:24:39 yeah if you had a need to preserve eMMC I was going to suggest that as alternative to wiping May 30 10:25:21 ahh right. and wiping the emmc causes the sd uboot to be chosen as there's no valid bootloader on the emmc, I'm guessing? May 30 10:25:27 yep May 30 10:25:39 it's BB-classic all over ;-) May 30 10:25:47 "Wipe NAND first!" May 30 10:25:49 (wiping sector 256 of eMMC would have sufficed) May 30 10:26:01 where does that first stage bootloader code live then? May 30 10:26:51 the boot stages are: rom bootloader -> u-boot SPL -> full u-boot -> linux May 30 10:27:24 the SPL, with a header prepended, is located at sector 256 (and up) of eMMC or SD May 30 10:27:36 the main u-boot.img is at sector 768 (and up) May 30 10:28:14 rom bootloader prefers loading SPL from eMMC over loading it from SD (unless the boot order is modified by powering on with the S2 button held down) May 30 10:28:29 SPL always loads u-boot from the same device as it came from itself May 30 10:28:42 u-boot prefers loading linux from sd over loading linux from emmc May 30 10:29:00 ahh ok. it's confusing to me that the rom bootloader will choose the emmc u-boot but then the emmc u-boot boots from SD May 30 10:29:14 yeah it's pretty messy May 30 10:29:53 i wasn't sure if i needed to hold down S2 to boot from SD so I tried it without and when it booted from SD, figured that was all there was to it, haha May 30 10:29:53 luckily that got fixed a while ago. Still there are enough devices circulating with that version May 30 10:30:19 tbr: ? May 30 10:30:40 oh you're talking about the kernel/rootfs mismatch that could happen with old images May 30 10:30:45 zmatt: the old U-boot, which loads from emmc, but boots sd May 30 10:30:55 yes May 30 10:30:57 every beaglebone u-boot does that May 30 10:31:20 yes? no? you're saying yes but then you're saying something that's different from what I said May 30 10:31:41 hmm, now I confused myself May 30 10:32:09 everything before you said "luckily that got fixed a while ago" was just me describing how it works (and is intended to work), the bug wasn't mentioned by me so you were already confused at that point May 30 10:33:07 I thought at some point images were modified that u-boot would ignore SD when it was on emmc, but I haven't played with it in ages May 30 10:34:46 it would have been saner if u-boot only loaded linux from the same device it came from itself. the major downside of that would be that you would then *have to* power on with the S2 button held down (or make eMMC unbootable) to be able to boot from sd card May 30 10:36:54 which I guess wouldn't be entirely unreasonable, but I also understand rcn wanted to make it low-hassle to boot from sd card. unfortunately that didn't work out too well when major changes were introduced in u-boot and /boot/uEnv.txt May 30 10:39:43 yeah May 30 10:46:39 hi May 30 10:47:11 how to check sd card in beagle board black May 30 10:47:44 turn it upside down and look at the receptacle May 30 10:48:48 i have inserted sd card how to check memory May 30 10:49:19 can you describe in more detail what you are trying to achieve? May 30 10:49:52 how to install android os in beagle board black May 30 10:49:59 can you share any link May 30 10:50:55 no clue about android on bbb, sorry. I think TI had something once. May 30 11:04:04 iirc TI moved android support for the am335x to a third party May 30 11:50:11 Hi, is there any commercial cape to make all pins available with screw terminals ? (or as many as possible) May 30 14:16:29 I've been installing the new Debian image on the BBB. Two points: It takes about 30 minutes to copy the image onto my PC - it's easy to stop too soon. Then it takes nearly an hour to flash the eMMC. When that's done, the BBB should power down but mine didn't. It won't boot up on the new Debian, so I've booted off the card and its flashing again. Any suggestions? May 30 15:35:42 per my finidings, you cannot epoll on /dev/i2c-x, but the question is, is that finding correct? May 30 15:39:07 well O_NONBLOCK has no effect on i2c-dev, so even if (e)poll were supported it would be completely useless May 30 15:39:14 (which is also why it isn't supported) May 30 15:40:24 similar thing for spi May 30 16:44:47 zmatt: thanks May 30 18:06:23 zmatt: there was a short down-time while some parts went out-of-stock... hit at a time of increased orders. both GHI and Embest ramped up to catch up. May 30 23:58:23 jkridner: thanks! figured it was something like that **** ENDING LOGGING AT Thu May 31 03:00:07 2018