**** BEGIN LOGGING AT Sat Nov 25 03:00:01 2017 Nov 25 03:42:44 Can Someone help me with programmig using C in BeagleBone Nov 25 08:52:38 ann. http://exploringbeaglebone.com/chapter5/ Nov 25 15:23:55 hi everybody Nov 25 15:24:10 I am connected to BBB using RNDIS via USB Nov 25 15:24:58 I can establish which eth port is connected to RNDIS using dmesg Nov 25 15:25:33 my question is, can I obtain this information in other ways instaed of parsing dmesg ? Nov 25 16:36:14 hi there channel :-) will bbb rev. c support sdhc micro sd-card 128gb? Nov 25 16:37:06 will it perform successfully? Nov 25 16:38:36 I might be able to check that right now... Nov 25 16:39:21 myself, you're telling that to me? Nov 25 16:41:03 yup, I have a 128GB card here, and a bbgreen, which I have to assume would behave the same; there's nothing different about the SD circuitry Nov 25 16:43:30 myself, right I see Nov 25 16:46:16 Oh hey. https://groups.google.com/d/msg/beagleboard/rK3y2ih1kig/v6rdkaVOBAAJ Nov 25 16:53:38 myself, jeessuss, wanna know if there is not issues on raspberry pi 3 model b, too Nov 25 16:54:07 that's off-topic anyway Nov 25 16:54:28 sorry, I know Nov 25 22:26:02 why wouldn't a 128GB card work? I'm pretty sure there haven't been any significant protocol changes since the 2GB transition Nov 25 22:26:17 oh wait Nov 25 22:26:23 * zmatt calculates Nov 25 22:26:31 that thread talks about a few Nov 25 22:27:13 apparently speed-related only Nov 25 22:27:32 the next limit should be 1 or 2 TB or so Nov 25 22:28:03 transfer speeds are not a compatibility issue Nov 25 22:28:08 just a performance issue Nov 25 22:29:21 okay now I feel motivated to check the spec Nov 25 22:29:57 since reading about people having issues is making me doubt myself Nov 25 22:35:00 yeah, no, I was remembering correctly. the only thing that distinguishes SDHC from SDXC is whether the card is >= 32 GB (that actually *defines* SDXC), there are no significant protocol differences Nov 25 22:37:41 one of the timeouts is larger, and the card may negotiate with host for drawing more power to be able to attain its speed class Nov 25 22:37:46 that seems to be about it Nov 25 22:42:21 so anything that supports SDHC should support SDXC, at most requiring a small timeout tweak Nov 25 23:09:59 Mostly software save the FS on the card. Most appear to use MS file systems because somehow that became a "standard". Nov 26 01:22:02 oh sure, the filesystem actually *is* part of the standard. SDXC is supposed to be exFAT. but in this context that's irrelevant of course Nov 26 01:25:58 oh boy, SDXC Nov 26 01:27:21 ? Nov 26 01:38:52 I have a Beaglebone Wireless, and I flashed it with the latest Debian image. However, when I run "connmanctl technologies" I only see ethernet, the built in wireless isnt detected. I ran a kernel update and a dist upgrade. No success, anybody else have this issue before? Nov 26 01:39:12 beaglebone black wireless or green wireless? Nov 26 01:39:41 Beaglebone Black Wireless Nov 26 01:40:57 can you check the output of this: Nov 26 01:41:00 head -c 32 /sys/bus/nvmem/devices/0-00500/nvmem | hexdump -C Nov 26 01:41:48 (and copy/paste it to pastebin.com or a similar site) Nov 26 01:42:14 https://pastebin.com/4f1EksqT Nov 26 01:42:29 misprogrammed eeprom Nov 26 01:42:44 leading u-boot to think it's a beaglebone black rather than a black wireless Nov 26 01:43:51 jkridner|pd: what are people who have this problem expected to do? just work around it by overriding the dtb selection? report it to manufacturer? Nov 26 01:47:55 bmcginn1: bytes 12-15 (the last four bytes on the first line) are supposed to be 42 57 41 35 ("BWA5") for the black-wireless Nov 26 01:48:51 and bytes 16-27 on the second line normally contain a serial number in ascii Nov 26 01:51:10 Alright, guess I can't just throw it in vim to change that file. Nov 26 01:51:16 hehe Nov 26 01:51:57 actually you *can* write to the eeprom via sysfs like that (although i'm not sure how good idea it would be to do it with vim...) Nov 26 01:52:04 but the eeprom is write-protected normally Nov 26 01:52:49 there's a testpoint on the pcb that needs to be connected to ground to disable write-protection Nov 26 01:53:58 yeah, I just found that. Oh man, this is not what I was expecting to be doing with it. Haha, should I try loading a new device tree? Nov 26 01:54:12 so it's not terribly hard, but do keep in mind that if you mess up any of the first 12 bytes then you will created an even bigger problem :) Nov 26 01:54:25 yeah overriding the dtb selection is the safe workaround Nov 26 01:54:45 although I'm not entirely sure how to do it correctly since the introduction of u-boot overlays Nov 26 01:56:46 but without u-boot overlays, it's just dtb=am335x-boneblack-wireless.dtb in /boot/uEnv.txt Nov 26 01:57:37 I'll try that. Its been a while since I've messed with device trees. First time using a board that isnt just a BBB. Nov 26 01:57:49 if you do intend to try fixing the eeprom, I'd use echo -ne '\xaaU3\xeeA335BNLTBWA5' >/sys/bus/nvmem/devices/0-00500/nvmem Nov 26 02:00:11 looks like you can disable the u-boot overlays Nov 26 02:01:08 you can, but u-boot overlays also has advantages like easily being able to enable one of the two ways of using pruss, and being able to selectively disable functionality like hdmi to free up the pins Nov 26 02:02:54 Good thing I actually have a need for HDMI for once then. haha. I'm gonna attempt to fix the eeprom. See how that goes. Else I'll disable u-boot for now. Nov 26 02:04:24 it's also not very hard to rig u-boot to ignore the eeprom and hardcode the board type... that's also the solution if somehow the eeprom gets messed up entirely :) Nov 26 02:05:33 disable u-boot overlays you mean Nov 26 02:18:17 may have accidently hit a pin i didnt mean to and caused it to reboot. I think I will just take care of the u-boot overlay. Haha Nov 26 02:20:01 yeah do be careful with hardware Nov 26 02:21:42 the testpoint is pretty easy to access on a BBB though, near the edge and away from other stuff, but I don't know if the same is true on the BBBW Nov 26 02:22:46 test point 4 right? Nov 26 02:24:31 TP4 on the BBB, TP1 on the BBBW according to the schematics Nov 26 02:34:04 Haha, that worked. Nov 26 02:36:43 BT and WL status lights are on and the EEPROM shows up properly Nov 26 02:36:55 \o/ Nov 26 02:37:06 good to hear Nov 26 02:39:23 Should we add the solution to the wiki for anyone else who may have that problem? Nov 26 02:39:39 if you want to write it up, go for it Nov 26 02:44:01 Good idea save some other individual from undo stress. **** ENDING LOGGING AT Sun Nov 26 03:00:00 2017