**** BEGIN LOGGING AT Tue Aug 23 02:59:58 2016 Aug 23 04:06:58 on beaglebone green, i see Ain are 1.8v max, but are gpio 5v tolerant (uarts) Aug 23 04:13:05 from what i am seeing, its 3.3v out, but 5v input tolerant? can anyone confirm or at least add a "worked fine for me" Aug 23 10:23:37 MrCurious: *only* the console port is 5v tolerant, absolutely no other I/O is Aug 23 10:25:16 the console port has a 5v tolerant isolation buffer (U15 on page 4 of bbb/bbg schematic) Aug 23 10:27:42 in general, applying to any pin a voltage significantly in excess of the power supply for that pin is one of the easiest ways of destroying the processor Aug 23 10:28:52 (that includes applying any voltage significantly in excess of 0V when the device is shut down or unpowered) Aug 23 10:30:50 to any processor pin I mean Aug 23 11:16:46 hello Aug 23 11:17:26 I wanted to know how can I enable the UART1 port for the BeagleBoneBlack Rev c for an ARM Image Aug 23 11:17:45 Does anyone have any details regarding this? Aug 23 11:22:48 jkridner: ping, is there actually any documentation on how one is supposed to do this on jessie images, since cape-universal broke most old instructions that used overlays Aug 23 11:22:52 ? Aug 23 11:35:00 So to elaborate more on my question, I am trying to build the zImage and dtb using the arm compiler Aug 23 11:36:08 I have added some part of the code to enable the UART1. However I am constantly getting "Bad Magic" Aug 23 11:36:21 with the error as "Bad Linux ARM zImage magic!: Aug 23 11:37:46 uhh, you don't need to (re)compile anything enable uart1 Aug 23 11:38:05 it's done via device tree Aug 23 11:39:33 bad zImage magic suggests you replaced the kernel by something that isn't Aug 23 11:40:01 (either copied the wrong file, or compiled a kernel for the wrong architecture) Aug 23 11:40:19 but like I said there's no need to recompile the kernel just to enable peripherals Aug 23 12:32:26 I got the beglebone green wireless now. wifi works find but bluetoothctl find no bluetooeh device Aug 23 12:32:30 what to do? Aug 23 12:33:24 run in circles while flailing arms Aug 23 12:34:02 hi zmatt, I took my time ordering the bbgw, and hoped it will all work fine after upgrading all Aug 23 12:34:19 I event cd /opt/scripts; git pull Aug 23 12:34:24 even Aug 23 12:35:23 zmatt: which module is the bluetooth at the bbgw? Aug 23 12:35:40 WL1835 Aug 23 12:36:11 thnaks Aug 23 12:36:21 Hi Zmatt, Can you please elaborate more on "Enabling the peripherals" through the Device tree? Aug 23 12:36:32 citylight2: the green's wiki page doesn't load for me, but google has a cached version: http://webcache.googleusercontent.com/search?q=cache:uHl6yshjkJ8J:www.seeedstudio.com/wiki/SeeedStudio_BeagleBone_Green_Wireless Aug 23 12:37:18 Or can you suggest some links where I can understand the same? Aug 23 12:38:01 Murtuza: https://github.com/mvduin/overlay-utils/blob/master/uart4.dtsi this uses some macros of mine to simplify doing pinmux Aug 23 12:38:15 And also when I say added some part of the Code means that "putting pinmux" details in the DTS file Aug 23 12:38:44 ok, after full power cycle bluetooth works Aug 23 12:38:48 after which I have been getting the "Bad Magic" and "bad ZImage" kind of errors Aug 23 12:39:03 Murtuza: you shouldn't replace the zImage at all Aug 23 12:39:41 also, what linux tree are you using? Aug 23 12:40:19 am335x-bone-common.dtsi Aug 23 12:40:26 This is the file I modified Aug 23 12:40:35 for the pin mux and recompiles Aug 23 12:41:24 "recompiled" Aug 23 12:41:47 well no quotes there since you apparently replaced the kernel image Aug 23 12:41:56 even though there's no reason to do that Aug 23 12:43:00 note that most commonly people don't change the main dtb but instead use overlays or other kinds of runtime reconfiguration, since this is typically easier Aug 23 12:43:02 Hmm. Ok. then what steps should I take now Aug 23 12:43:42 depends a bit on which filesystem image you are using Aug 23 12:44:08 I am using YOCTO build Aug 23 12:44:35 that also gave me error Aug 23 12:44:57 ok, that I don't know much about. it may still be easier to first use overlays until you're sure you have the right config and then make your own dts file Aug 23 12:45:34 this does require that overlays are enabled in the kernel config however (CONFIG_OF_DYNAMIC, CONFIG_OF_OVERLAY, CONFIG_OF_CONFIGFS) Aug 23 12:45:54 ok Aug 23 12:47:08 if they aren't enabled by default in the yocto build then I don't know whether it's easier to enable those or to customize the dtb, I don't have any experience with yocto Aug 23 12:48:04 sure Aug 23 12:48:34 anyhow, but you seem to be saying that replacing the kernel image is giving me troubles Aug 23 12:48:44 like bad magic or bad ZImage Aug 23 12:49:04 "Bad Linux ARM zImage magic" means you replaced the kernel by a file that u-boot doesn't even recognize Aug 23 12:51:16 try using the "file" utility on your zImage Aug 23 21:56:24 Hi Aug 23 21:58:13 I have this gpios in a device (no beaglebone :( ) http://dpaste.com/0PJDDVR How acces gpios in the led group or remove the led group?¿ Aug 23 21:59:31 http://dpaste.com/0R8MRGH this is the Gpio that I have acces now Aug 23 21:59:40 i need 22,23,24,26 Aug 23 22:00:00 because the shift register i need to drive is attached to this pins Aug 23 22:00:22 this is an ipcamera hacked with LEDE firmware Aug 23 22:01:02 the shif register drives a darlington array uln2803 Aug 23 22:01:09 and a pair of steppers Aug 23 22:01:51 th shift register is an hc259 Aug 23 23:27:38 hi - is there anyone here who has experience using ti-rtos on the beaglebone black? **** ENDING LOGGING AT Wed Aug 24 02:59:58 2016