**** BEGIN LOGGING AT Thu Sep 10 02:59:58 2015 Sep 10 05:44:22 hi Sep 10 05:44:48 will any one tell me where do i get code for 1)LED 2)Playing with GPIO 3)Alphanumeric LCD, Dot matrix LCD and Graphical LCD 4)I2C 5)SPI 6)UART 7)USART 8)USB host and USB OTG(Device) 9)Ethernet 10)SD card 11)Bluetooth 12)WiFi 13)Different Sensors like IR, RF, Proximity etc 14)ADC 15)DAC 16)EEPROM 17)Android porting(Material) Sep 10 05:45:07 for the board beaglebone black Sep 10 06:09:17 Hi, does anyone can tell me why i've P9_12, P9_15, P9_17, P9_18 raising up when I press the reset button on the board ? and P9_12 and P9_15 stay on until kernel boot Sep 10 06:33:36 that's their reset state Sep 10 06:34:08 see my spreadsheet for lots of information about all pins, including their reset state: https://docs.google.com/spreadsheets/d/1CK5c-Cs8G1RtzGo-J3VJsD9m5K-fp06AncgeYWsdjSU/edit Sep 10 06:34:50 specifically the BBB tab (which is based on the Pinmux tab, but specialized for the beaglebone black) Sep 10 06:35:15 you can sort by expansion header pin using menu "Data -> Filter views -> By connection (BBB)" Sep 10 06:42:21 just noticed the filter views were broken (happens occasionally due to editing)... Sep 10 06:42:42 fixed them now Sep 10 06:43:52 that is a nice sheet thanks :O Sep 10 06:44:40 thanks :) Sep 10 06:45:56 Thanks, but how can I change there default reset state ? and the mux during bootloader ? Sep 10 06:46:31 you can't change the reset state, other than by overriding the weak internal pulls by sufficiently strong external pulls Sep 10 06:47:22 hello Sep 10 06:47:23 for example pins 0-7 (eMMC) will be high during reset, even though the reset state indicates weak pull-down, since those are overriden by external pull-ups Sep 10 06:47:43 that's indicated in the "pull" column on the left Sep 10 06:47:52 i want to load windows embedded on BBB Sep 10 06:48:10 (Hb means pull-up to the vdd_3v3b supply) Sep 10 06:49:14 i want to load windows embedded on BBB. i have licence os of winCE7. how can i install it on BBB?? Sep 10 06:49:21 please rep me Sep 10 06:49:34 Ok thanks zmatt, so no way to pull down those pin by software ... need to do it by hardware Sep 10 06:49:38 reply me Sep 10 06:50:09 priyanka_: I don't think anyone here has ever run windows CE/EC on a BBB, so you're not going to find any help here... but last time someone asked I did a quick google and found multiple websites related to it Sep 10 06:50:28 e.g. https://beaglebonebsp.codeplex.com/ Sep 10 06:51:34 zmaat on beaglebonebsp.codeplex just show to run winCE from SDcard. but i want to flash it on BBB. not to ruyn by sdCard Sep 10 06:53:01 Gwak: if you absolutely need them to be low during reset, then yes. beware however that P9.17 and P9.18 are muxed as outputs if they are configured for SPI Sep 10 06:53:16 Gwak: this happens for example when the ROM bootloader attempts SPI boot Sep 10 06:54:19 if the SD-boot button is pressed, the boot order is: SPI, μSD, USB, UART .. in that order Sep 10 06:54:28 But for me P9_17 and 18 are high just while pressing reset and goes down when releasing the button Sep 10 06:54:35 this doesn't correspond with your sheet Sep 10 06:54:48 P9_17 : reset : Z and post reset H Sep 10 06:54:56 most likely they are remuxed by the bootloader Sep 10 06:54:58 Z mean high impedance I suppose Sep 10 06:55:00 yes Sep 10 06:55:31 but I can't rebuild u-boot and change the pinmuxing ? (I've tried but without success) Sep 10 06:55:47 btw "reset" there actually means power-on-reset Sep 10 06:55:50 afaik Sep 10 06:56:20 not 100% sure, the datasheet is slightly vague about that Sep 10 06:57:04 I know u-boot does some bogus pinmux, lemme check if that might be the cause Sep 10 06:57:58 I've tried to modify ./u-boot/board/ti/am335x/mux.c but no success .. maybe I did it wrong but I've seen no change Sep 10 06:58:45 pinmux is being done in more than one place I think, but I'm not sure Sep 10 06:58:52 Same P9_15 is marked Low on reset and post reset but this one stay high before kernel start and load device tree. Sep 10 06:58:53 in any case, as soon as the kernel loads, device tree takes over Sep 10 06:59:06 P9.15 is actually ambiguous Sep 10 06:59:34 it's connected to two cpu pins (16 and 34) Sep 10 06:59:44 Yep this work great for the DT, but I need to be sure that my embedded device plugged in those gpio doesn't tare any current on boot Sep 10 06:59:49 at reset, one has pull-down and one has pull-up Sep 10 07:00:07 (this I consider to be a hardware screw-up) Sep 10 07:00:31 Hum on my schematics P9_15 is connected to sheet 3 i.e processor I see only one connection Sep 10 07:03:29 * priyanka slaps priyanka around a bit with a large fishbot Sep 10 07:03:54 it connects to the net GPIO1_16 which connects via R160 (0Ω) to cpu ball R13 and via R161 (0Ω) to cpu ball T13 Sep 10 07:04:16 my bad you'r right Sep 10 07:05:11 so I seriously recommend putting an external pull on that one anyhow Sep 10 07:05:19 since right now it'll probably hover somewhere in between Sep 10 07:05:32 depending on the relative strength of the weak internal pulls Sep 10 07:06:45 priyanka_: there shouldn't be any significant difference between eMMC and SD Sep 10 07:07:28 priyanka_: they're basically just two mmc/sd slots as far as hardware is concerned (except eMMC supports 8-bit data width and doesn't have card-detect obviously) Sep 10 07:07:48 priyanka_: but I know absolutely nothing on winEC, so... Sep 10 07:09:25 Thanks for your time zmatt ;) Sep 10 07:09:33 Gwak: still checking u-boot pinmux Sep 10 07:09:37 had trouble for a moment with serial cable Sep 10 07:10:07 hi guys . Is 4d system 4.3CAPe compatible with beagle bone green Sep 10 07:12:55 Thanks tell me if you find something usefull in uboot pinmuxing, I'm not sure where we can setup stage 1 and stage2 pinmux, i've just found the mux.c file releated to the am335x board Sep 10 07:14:10 it muxes P9.{17,18} to I²C 1 Sep 10 07:14:23 which is pretty bogus Sep 10 07:15:33 sry don't undestand "bogus" ^^ Sep 10 07:16:04 zmatt i have developed application on WinCE so i want to load that application on Beaglebone black. thats the only reasone i want winCE on BBB. Sep 10 07:16:06 eh, hard to translate in general but in this case i mean stupid/inappropriate or something like that Sep 10 07:17:11 Ye that's was I saw digging into mux.c and didn't undestand why the board was doing this Sep 10 07:17:17 priyanka_: explaining your motivation will not magically give me or anyone else knowledge or insight related to running WinEC on a BBB Sep 10 07:21:14 priyanka_: I've never seen anyone talking about WinEC on this channel (other than the very rare person seeking help with it), so most likely noone here has experience with it Sep 10 07:21:48 Gwak: partly because they're using the same bootloader for a variety of boards Sep 10 07:22:00 which isn't a good excuse in my opinion Sep 10 07:24:57 Gwak: the mistake looks easily fixable though Sep 10 07:28:14 How ? i've tried to modify the mux.c without success Sep 10 07:30:47 I would say: http://gerbil.xs4all.nl/uboot-i2c1.patch Sep 10 07:30:50 haven't tested it yet Sep 10 07:31:06 return 403 forbidden ^ Sep 10 07:31:20 hmz Sep 10 07:31:33 fixed Sep 10 07:31:47 Thanks a lot ! Sep 10 07:32:28 You tested it ? Sep 10 07:32:32 09:30 < zmatt> haven't tested it yet Sep 10 07:32:43 i've removed the line I2C too but this didn't changed anything Sep 10 07:33:07 did you remove it from the if (board_is_bone_lt(header)) case ? Sep 10 07:33:20 no Sep 10 07:33:35 board_is_bone() means the beaglebone white Sep 10 07:33:42 oh >< Sep 10 07:33:56 (not entirely obvious) Sep 10 07:34:03 i'm going to try that so and come back to tell you Sep 10 07:36:59 Hum and maybe a stupid question but is there a way to update uboot ? I'm actually creating a flasher SD to do it but I'm sure there is a simpler way to do it.. (TFTP ?) I'm not able to see the MLO and u-boot.img file in /boot directory on the eMMC Sep 10 07:37:35 it's written to a region outside the partition Sep 10 07:37:41 hold on, got the offsets somewhere Sep 10 07:38:07 ye I now but no way to mount this part or this rewrite it from uboot ? Sep 10 07:38:07 they get written to the FAT partition Sep 10 07:38:25 tbr: on uSD yes Sep 10 07:39:05 that works for eMMC too, but current eMMC images don't use a FAT boot partition Sep 10 07:39:14 should work on emmc too. ofc you can play the offset game, but unless you use the primary offset it's very finnicky Sep 10 07:39:31 *nod* Sep 10 07:40:18 Gwak: you need to be able to access the eMMC as raw block device (e.g. when booted from SD, or using the "ums" command of u-boot) Sep 10 07:40:28 and then dd to the right offset Sep 10 07:40:49 I've tried but reached a data abort, probably because of a wrong offset Sep 10 07:40:50 the SPL is located at byte-offset 0x20200 Sep 10 07:41:05 main u-boot at byte offset 0x60000 Sep 10 07:41:13 thanks Sep 10 07:42:14 the 512-byte sector at offset 0x20000 contains a magic header that is recognized by ROM (and it expects SPL immediately after that) Sep 10 07:42:30 offset 0x60000 is probably hardcoded in SPL Sep 10 07:43:02 (ROM looks for the magic header at offsets 0, 0x20000, 0x40000, and 0x60000, in that order) Sep 10 08:13:15 nice, master branch of u-boot with am335x_boneblack_defconfig produces an MLO that doesn't fit in SRAM at offset they request Sep 10 08:14:28 bloatware -.- Sep 10 08:18:18 no wait, argh, it puts a TOC in front of it Sep 10 08:18:32 * zmatt curses Sep 10 08:18:52 The only way i've find to update uboot is using the flasher script from eewiki with an SDcard... quite long but this work it's actually flashing the board Sep 10 08:18:58 found* Sep 10 08:19:30 I'm testing with u-boot on SD first rather than clobbering my eMMC Sep 10 08:20:18 ye not stupid ... don't know why I didn't do that Sep 10 08:20:20 but it turns out the "MLO" produced by u-boot isn't an MLO file but rather a concatenation of aforementioned 512-byte sector with the actual MLO Sep 10 08:20:55 so you need to write it to offset 0x20000 Sep 10 08:21:03 ehh Sep 10 08:21:07 0x20000 Sep 10 08:21:14 wait that's the same Sep 10 08:21:25 sorry, got lost counting the number of zeros somewhere :P Sep 10 08:21:36 (I typed it right both times at least) Sep 10 08:21:40 ^^ Sep 10 08:22:14 but to get an actual MLO you can put on an SD card you need to strip off that 512-byte header Sep 10 08:25:03 ah, and my SD partition wasn't marked bootable Sep 10 08:25:10 yay, it boots Sep 10 08:26:46 Same it boots but no change for the pinmux Sep 10 08:27:11 Well i've a change, I2C pin P9_17 and 18 stay on during the all uboot process Sep 10 08:27:16 it worked here Sep 10 08:27:30 Hum I've probably done something wrong so ^^ Sep 10 08:27:30 or, well, it configured them to spi Sep 10 08:27:42 but that's because I booted from SD Sep 10 08:28:18 (as mentioned, booting with SD-button pressed actually puts SPI boot first in the boot order, uSD is second) Sep 10 08:29:52 Ye, but normaly no way that those pin goes UP according to SRM when you don't use the sd button Sep 10 08:30:43 actually booting from eMMC so no button press, the problem is now worst P9_12 P9_15 p9_17 p9_18 up during the all bootloader Sep 10 08:30:54 still sounds like spi mux Sep 10 08:31:02 do you have P9_12 P9_15 up too during SD boot ? Sep 10 08:31:29 those are reset defaults Sep 10 08:32:15 you could add some code to mux.c to change them during early boot, only an external pull-down resistor can change them during reset Sep 10 08:32:50 For P9_12 yes but not for P9_15 .. according to your google file Sep 10 08:33:37 again, P9.15 is pin with conflicting pulls Sep 10 08:33:45 P9.15 16 fast rx down [7] gpio 1.16 Sep 10 08:33:45 P9.15 34 fast rx up [7] gpio 2.00 Sep 10 08:33:47 Oh well yes >< Sep 10 08:35:15 ok so i'm going to use a HW solution so.. :/ but this is clearly really really awkward for an embedded board purpose ... this is clearly an error of conception .. In my opinion Sep 10 08:35:51 Or i don't undestand the aim of that setup ... Sep 10 08:36:14 I'm measuring about 1.58 V on P9.15 Sep 10 08:37:19 well the default pulls *are* documented, and usually it doesn't matter anyhow Sep 10 08:38:17 connecting two cpu pins to a single expansion header pin was intended to allow more choices of functionality, though connecting two pins with opposing pulls wasn't a good idea and probably an oversight Sep 10 08:40:17 (note that in theory you can remove one of the two 0Ω resistors to disconnect P9.15 from one of the two cpu pins, but you need good SMD soldering skills for that) Sep 10 08:41:33 ok, the default u-boot env is clearly bogus Sep 10 08:42:11 I guess whatever rcn is using isn't mainlined Sep 10 08:47:03 xD not a bad idea to remove the resistor but this will be quite tricky, i've already changed the side of the serial port Sep 10 08:47:47 well it's not really necessary either: including an external pull-down is probably easier Sep 10 08:47:51 I'm going to use an HW solution, quite disapointing to not be able to fix this by SW, but anyway this will work just need to change the mainboard routing Sep 10 08:48:04 ye sure this will be easier Sep 10 08:48:31 interfacing external hardware to a beaglebone has lots of little details to mind anyway Sep 10 08:49:21 Anyway thanks a lot for your time ;) Sep 10 12:16:50 can some1 help me please top understand how to install new images to my bbb rev c? Sep 10 12:16:57 to* Sep 10 12:18:14 the images and the explenations in "getting started" are too old and they are not helpfull at all Sep 10 14:00:32 I'm a bit confused, looking for driver 4 analog output with a char device using SPI1 and the DAC124S085 chip, I'm actually looking at a driver leds-dac124S085, "static int dac124s085_probe(struct spi_device *spi)" How the kernel choose the SPI device used to communicate at probe call ? is there anything to set in the device tree ? Sep 10 16:21:04 hello Sep 10 17:08:57 can some1 help me please to upload teh newesrt image to my bbb rev 3? Sep 10 17:09:05 the newest* Sep 10 17:10:06 can some1 help me to install / update the newest image to my bbb rev c please? its important Sep 10 17:10:43 the explenation in the website are too old and a lot different than what is realy happen Sep 10 17:43:09 Nitay, the directions are the same, only the name/date has changed.. Sep 10 22:33:58 I miss simple Xlib based programs Sep 11 01:32:41 Hi! I can't install latest image on BBB. Help me. Sep 11 01:33:48 Is there anyone? TT Sep 11 01:40:55 hi Sep 11 01:41:44 hi Sep 11 02:09:29 hi **** ENDING LOGGING AT Fri Sep 11 02:59:58 2015