**** BEGIN LOGGING AT Tue Feb 26 02:59:57 2019 Feb 26 03:18:23 lol Feb 26 15:53:50 Hi Feb 26 15:54:27 Is there a 5vdc point somewhere in the BeagleBoard x15 card? Feb 26 16:03:12 Or should i take 5v from outside the board. Feb 26 16:09:39 on the silkscreen I see a bunch of points named 5V Plg123 Feb 26 16:10:13 Let me check Feb 26 16:12:12 What do you mean by silkscreen or can u send a link please. Feb 26 16:13:10 https://elinux.org/images/1/13/BBX15-TOP_SIDE.jpg Feb 26 16:15:51 Thabks a lot i found. Feb 26 16:15:56 Thanks Feb 26 18:55:40 Hi how can I turn the LCD gpio's off so I can use them as a normal gpio's on BBB Feb 26 19:14:24 some DT overlay, i guess? Feb 26 20:52:21 mmm, so 4GB eMMC came with BBB rev. C? today i found that my BBB is rev B6. it has 4GB eMMC though Feb 26 20:52:58 or does the wiki have an error? https://elinux.org/Beagleboard:BeagleBoneBlack#Revision_C_.28Production_Version.29 Feb 26 20:53:56 there are "pre-C" 4GB, they were either made by embest, before it was stated to rename as C's, and a few guys reballed Rev Bx's.. Feb 26 20:55:48 ah, that makes sense Feb 26 22:13:37 Ciao. Feb 26 22:13:47 So, I have a pocketBeagle. Feb 26 22:14:01 I also have a 128GB SD card. Feb 26 22:14:20 My question is: is there a limit to the size of card the unit will take? Feb 26 22:15:02 For instance, reading up on the spec, a given SDHC compliant controller will be able to deal with up to 32GB cards etc. Feb 26 22:16:06 It's not clear to me but it looks like the controller on the pocketBeagle is an SDHC compliant controller. Feb 26 22:16:44 So, would the card downgrade both the speed and the max size available to the unit, or does something else happe Feb 26 22:17:02 Or, am I totally misunderstanding this and am in need of correction? :-) Feb 26 22:19:16 128GiB would be SDXC duncan^ Feb 26 22:19:56 only SDXC host controller can handle SDXC card, according to sandisk Feb 26 22:21:15 Yeah, so I am really wondering if it would work at all Feb 26 22:21:19 "some" SDXC cards will work with the am335x's interface.. Feb 26 22:21:45 test one, before you buy a bunch, and make sure they are the exact same model id.. Feb 26 22:21:49 I can't actually find much information about the controller other than assuming it's the same as on the older omap33xx devices Feb 26 22:22:40 I only really care about such sizes as I like to play music off my pocketBeagle and I have acquired too much music. Feb 26 22:22:55 am335x mmc ip controller fully supports SDHC, it "includes" some of the SDXC functions, but not 100% compatible, (it doesn't have split voltage rail, and some of the high end transfer protocals) Feb 26 22:27:58 it's said in the reference manual duncan^ Feb 26 22:28:06 « SD Host Controller Standard Specification sets as defined in the SD card specification Part A2 v2.00 » Feb 26 22:28:28 Ah, OK. So it's SDHC. Feb 26 22:29:42 yeah, that specification says that it supports up to « High Capacity Ver.2.00 Card » Feb 26 22:29:47 rcn-ee[m]: uhh, all SDXC cards should work on the beaglebone Feb 26 22:29:58 but maybe there's retrocompatibility Feb 26 22:30:13 sandisk's site says no; but they maybe have incentive to make people buy the newest stuff Feb 26 22:30:18 yes, newer cards are required to support the older transfer protocols Feb 26 22:30:43 note that there's no protocol difference between SDHC and SDXC, it's just a naming change once you go over a certain size limit Feb 26 22:31:02 (32G iirc) Feb 26 22:31:16 yes all 'should'.. for compatibility sake.. Feb 26 22:32:39 sandisk site greatly emphasizes that it's not the case Feb 26 22:32:48 but maybe they don't mention partial compatibility Feb 26 22:32:49 well it's more than that... all sd cards initially use the older 3.3V transfer speeds and will only go to 1.8V once this has been negoatiated Feb 26 22:32:52 eg not using the full size of the card Feb 26 22:33:04 mawk: what are you talking about? what is not the case? Feb 26 22:33:20 SanDisk SDXC's are the only ones i've tested on the Beagle's.. Feb 26 22:33:38 that there is retrocompatibility Feb 26 22:33:38 they say that only a sdxc compliant host controller can read sdxc cards Feb 26 22:33:39 they're full of shit Feb 26 22:34:05 the only compatibility problem is that sdxc cards are required to be exFAT formatted by default Feb 26 22:34:15 of course that's irrelevant, you can just reformat it Feb 26 22:34:34 yeah Feb 26 22:34:41 https://pastebin.com/raw/AA69BQMm Feb 26 22:34:58 here's a summary I made of card sizes and protocols Feb 26 22:36:17 nice Feb 26 22:36:55 indeed in the spec SDHC and SDXC are the same bit when identifying the card Feb 26 22:36:59 going from SDSC to SDHC was a major change because SDSC expresses sizes in bytes and SDHC in sectors Feb 26 22:37:12 SDXC however required no further change, it's basically just a marketing term Feb 26 22:37:27 https://pix.watch/WEoZXu/nALcGz.png Feb 26 22:37:31 yeah Feb 26 22:40:27 oh yeah, and they added an optional control bit that the host can use to tell the card it's allowed to draw 150 mA instead of 100 mA, and this may be required to reach its speed rating Feb 26 22:44:22 Ah cool, this is interesting Feb 26 22:45:13 Now I'm wondering what happens when we get cards over 2TB... ;-) Ie beyond SDXC standard Feb 26 22:46:18 with the am335x's transfer speeds it would take forever to use up.. ;) Feb 26 22:49:48 the am335x implements the specification v2.0, where no mention was of the sdxc things Feb 26 22:49:57 so it's in compatibility mode forever Feb 26 22:50:16 remember, sdxc didn't exist when the am335x was first designed.. Feb 26 22:50:28 yeah Feb 26 23:26:15 Hi, is there a library to install to use c++ for programming gpios in BeagleBoard - x15 ? Feb 27 00:03:42 Hi, i have a beagleboard-x15, i want to test led in gpios, first should i use pinmux tool from Texas Instruments ? Feb 27 00:03:55 or is there other solution? Feb 27 00:04:09 Is pinmux tool free to use? Feb 27 00:21:43 hello? Feb 27 00:28:56 hi Enfield350 Feb 27 00:29:00 you have several choices Feb 27 00:29:16 but using the GPIOs in a library-less manner isn't that hard Feb 27 00:30:14 and it's often the best solution if you plan to get notified on state change for instance Feb 27 00:31:14 so Enfield350 that library-less manner is either to open the /dev/gpiochipX file that corresponds to the GPIO bank of the pin you want to toggle; you can act on several pins from a single bank; or to open some file I don't remember in /sys Feb 27 00:31:30 some people here might tell you that the /sys way is superior Feb 27 00:31:46 you ol Feb 27 00:32:37 you open() the special file, then you can run several ioctl() calls to get other special files corresponding to the pin you select from the bank, then on that secondary file you can do further write() or ioctl() to toggle the pin, etc Feb 27 00:57:45 sysfs is way easier than the chardev Feb 27 00:59:41 after exporting the gpio (done by DT or manually by writing the gpio number to /sys/class/gpio/export ) you can simply read/write the value and direction via sysfs attributes Feb 27 01:05:10 ok Feb 27 01:06:24 thank you so much Feb 27 01:07:53 Enfield350: I actually declare my gpios in DT (using a gpio-of-helper node) and use an udev rule to create convenient symlinks: https://pastebin.com/c9jq54wJ Feb 27 01:08:57 thanks a lot Feb 27 01:09:01 thus applications don't need to know about gpio numbers, and if we need to move a gpio (e.g. because it's using a pin we need for some other interface) then only a DT change is required, the application wouldn't know or care Feb 27 01:11:36 another benefit of using gpio-of-helper is that the pin direction (and, in case of output, the initial level) is set in DT, so it's applied early and applications can't change the direction of an input to output (which could easily damage hardware), notice how the 'direction' attributes in my pastebin are readonly **** ENDING LOGGING AT Wed Feb 27 02:59:56 2019