**** BEGIN LOGGING AT Mon Mar 23 02:59:58 2020 Mar 23 10:10:36 Hi I bought new PB board after burning previous. This time I want to be 100% sure in powering circle. Mar 23 10:10:38 https://pastebin.com/raw/SR2An2fV Mar 23 10:11:48 *powering circuit Mar 23 11:00:34 Siegurd: since you're using it as a host port, usb1 id (P1.13) should be connected to ground Mar 23 11:05:18 I have a beaglebone black and 4.3 inch lcd display cape. I would like to connect my lcd to beaglebone. Can anyone help me in connecting it?? Mar 23 11:20:52 Siegurd: officially the vbus should be provided via a usb power switch. you may get away with omitting that, but in that case I'd strongly suggest using the PocketBeagle's 5V output (P1.24) to provide power instead of using your supply directly. I've sketched both options here: https://photos.app.goo.gl/e1663vMMDnEmGZaR6 Mar 23 11:21:27 vardhan: if it's a standard lcd cape it *should* just work plug & play Mar 23 11:23:23 I am getting a plain white screen when connected Mar 23 11:25:30 Siegurd: the issue with using the 5V supply directly for the modem is that its VBUS would be present (causing it to pull up the D+ line) even if the pocketbeagle isn't (properly) powered up yet. Technically such a situation might violate the absolute maximum ratings, although I'm uncertain how likely it is to cause problems in practice, especially if the pocketbeagle is normally never shut down while ... Mar 23 11:25:36 ...the 5V power supply is present Mar 23 11:26:49 vardhan: can you log in via ssh, run sudo /opt/scripts/tools/version.sh and share the output via a paste service like pastebin.com Mar 23 11:28:10 Yeah definitely, please give me 2 minutes Mar 23 11:31:41 Thanks, I will try power circuit on right-hand photo and reply. Mar 23 11:35:01 Siegurd: you may need to add some capacitance on VBUS at least, especially if the device is hotplugged or has bursts of high power consumption Mar 23 11:35:26 2A max Mar 23 11:35:43 peak or average? Mar 23 11:35:51 peak Mar 23 11:36:08 itn sim7600E-h HAT Mar 23 11:36:14 *its Mar 23 11:36:26 oof, then you'll definitely need to add a large amount of capacitance and I don't know if that'll suffice Mar 23 11:36:52 like 100 uF or so Mar 23 11:37:39 you can't expect to draw 2A from the pocketbeagle 5V output Mar 23 11:39:44 so that'll need to be smoothed externally, or use your own 5V supply directly instead of the pocketbeagle 5V out, but doing so without the usb power switch would make me uncomfortable (though that doesn't mean it'll cause problems in practice, especially if you never shut down the pocketbeagle while keeping the 5V supply present) Mar 23 11:41:26 any design without the usb power switch is technically out of spec anyway... (and in older days it used to confuse the musb kernel driver iirc, though it seems nowadays it is able to cope with it) Mar 23 12:06:18 This is the output I got afyter typing sudo /opt/scripts//tools/version./tools/vegit:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5]eeprom:[A335BNLT00C02315BBBK414F]model:[TI_AM335x_BeagleBone_Black]dogtag:[BeagleBoard.org Debian Image 2019-08-03]bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot Mar 23 12:06:19 2019.04-00002-gbb4af0f50f]:[location: dd MBR]bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.01-00001-gb2412df]:[location: dd Mar 23 12:06:19 MBR]kernel:[4.14.108-ti-r113]nodejs:[v6.17.0]uboot_overlay_options:[enable_uboot_overlays=1]uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]uboot_overlay_options:[enable_uboot_cape_universal=1]pkg check: to individually upgrade run: [sudo apt install --only-upgrade Mar 23 12:06:20 ]pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801]pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]pkg:[kmod]:[23-2rcnee1~stretch+20171005]pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]groups:[debian : debian adm kmem Mar 23 12:06:20 dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide]cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]dmesg Mar 23 12:06:21 | grep remote[ 1.256841] remoteproc remoteproc0: wkup_m3 is available[ 1.469115] remoteproc remoteproc0: powering up wkup_m3[ 1.469229] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168[ 1.473472] remoteproc remoteproc0: remote processor wkup_m3 is now up[ 12.453143] remoteproc remoteproc1: 4a334000.pru is Mar 23 12:06:21 available[ 12.467586] remoteproc remoteproc2: 4a338000.pru is availabledmesg | grep pru[ 12.409454] pruss 4a300000.pruss: creating PRU cores and other child platform devices[ 12.453143] remoteproc remoteproc1: 4a334000.pru is available[ 12.453261] pru-rproc 4a334000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed Mar 23 12:06:22 successfully[ 12.467586] remoteproc remoteproc2: 4a338000.pru is available[ 12.467713] pru-rproc 4a338000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfullydmesg | grep pinctrl-single[ 0.942092] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568dmesg | grep gpio-of-helper[ 0.954129] Mar 23 12:06:22 gpio-of-helper ocp:cape-universal: readylsusbBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubEND Mar 23 12:06:26 sorry Mar 23 12:06:31 vardhan: >:( Mar 23 12:06:51 never ever paste multiline output into chat Mar 23 12:06:55 git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5]eeprom:[A335BNLT00C02315BBBK414F]model:[TI_AM335x_BeagleBone_Black]dogtag:[BeagleBoard.org Debian Image 2019-08-03]bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-gbb4af0f50f]:[location: dd MBR]bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot Mar 23 12:06:56 2015.01-00001-gb2412df]:[location: dd MBR]kernel:[4.14.108-ti-r113]nodejs:[v6.17.0]uboot_overlay_options:[enable_uboot_overlays=1]uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]uboot_overlay_options:[enable_uboot_cape_universal=1]pkg check: to individually upgrade run: [sudo apt install --only-upgrade Mar 23 12:06:56 ]pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801]pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]pkg:[kmod]:[23-2rcnee1~stretch+20171005]pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]groups:[debian : debian adm kmem Mar 23 12:06:57 dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide]cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]dmesg Mar 23 12:06:57 | grep remote[ 1.256841] remoteproc remoteproc0: wkup_m3 is available[ 1.469115] remoteproc remoteproc0: powering up wkup_m3[ 1.469229] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168[ 1.473472] remoteproc remoteproc0: remote processor wkup_m3 is now up[ 12.453143] remoteproc remoteproc1: 4a334000.pru is Mar 23 12:06:58 available[ 12.467586] remoteproc remoteproc2: 4a338000.pru is availabledmesg | grep pru[ 12.409454] pruss 4a300000.pruss: creating PRU cores and other child platform devices[ 12.453143] remoteproc remoteproc1: 4a334000.pru is available[ 12.453261] pru-rproc 4a334000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed Mar 23 12:06:58 successfully[ 12.467586] remoteproc remoteproc2: 4a338000.pru is available[ 12.467713] pru-rproc 4a338000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfullydmesg | grep pinctrl-single[ 0.942092] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568dmesg | grep gpio-of-helper[ 0.954129] Mar 23 12:06:59 gpio-of-helper ocp:cape-universal: readylsusbBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubEND Mar 23 12:07:40 putting +5V in parallel to P1.01 and P1.05 is a bed idea? Mar 23 12:08:21 Siegurd: P1.05 always needs to connect to the vbus pin of the host port, regardless of how it is powered Mar 23 12:08:51 (it's a 5V-tolerant analog input that the usb controller uses to monitor the vbus voltage) Mar 23 12:09:54 whoops Mar 23 12:10:21 why am I not seeing mode changes.... I must have some ignore rule that's too aggressive Mar 23 12:14:15 vardhan96: share multiline output via a paste service like pastebin.com, never paste multiline output into chat Mar 23 12:15:03 git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5] Mar 23 12:15:03 2015.01-00001-gb2412df]:[location: dd MBR] Mar 23 12:15:38 vardhan96: share multiline output via a paste service like pastebin.com, never paste multiline output into chat Mar 23 12:15:41 vardhan96: share multiline output via a paste service like pastebin.com, never paste multiline output into chat Mar 23 12:15:49 :( Mar 23 12:16:37 not reading instructions is a great way to get people to not be in the mood to help you Mar 23 12:17:02 oh he's gone Mar 23 12:18:23 I wish irssi had an easy way to hide join/quit spam except for people who have recently spoken in chat Mar 23 12:25:22 @zmatt: what max current the P1.24 can give and what happens if overload? Will this lead to overheating (or/and damaging) the board or will it simply limit the output current to the maximum and continue to work regardless what current modem needs? Mar 23 12:25:54 Siegurd: it'll most likely cause the pocketbeagle to instantly power off Mar 23 12:27:25 so its safe to try? Mar 23 12:28:13 I think so Mar 23 12:28:28 but it can definitely not supply 2A Mar 23 12:30:19 if I felt a need to test a dubious setup with bursts of large power draw I'd at least hook up a scope to see what it's doing to the supply rails :P Mar 23 12:33:29 Mabe I'm wrong with peak 2 Amps of sim7600. its designed for Pi board and computers with USB interface. It works with USB3.0 in my notebook. So i think its all about 600-700 mA current consumption. Mar 23 12:33:54 a (proper) usb host port has a decent amount of capacitance though Mar 23 12:34:11 like I said I'd at least add a 100 uF cap Mar 23 19:40:58 I was interested in getting an LCD cape Mar 23 19:41:12 I just realized I have beagle bone green Mar 23 19:41:53 by SEEED, it is based off of the black. do you think I could get away with getting a cape designed for the black Mar 23 19:43:50 iirc the green is fully compatible with the black. the green-wireless however is not, avoid that one Mar 23 20:07:59 As a safe measure check the header pin outs... Mar 23 20:08:20 they have the same expansion header pinout Mar 23 20:09:00 BBB and BBB Enhanced has some header pin changes Mar 23 20:09:58 the BBE has the same P9/P8 expansion header pinout as the BBB, except that one should mind the fact that the spi flash (if present) is attached to spi0 cs0 Mar 23 20:10:59 I will investigate WHAT I was reading again. Mar 23 20:11:26 the green-wireless again uses the same expansion headers but a whole bunch of pins are in use by the wifi/bt chipset (pointlessly so) Mar 23 20:11:54 pointlessly so ?? Mar 23 20:13:44 yeah like the black-wireless they removed ethernet and replaced it with wifi/bt, but whereas the black-wireless reused the pins that were previously used for ethernet (which have everything you need for the wifi/bt chip on alternate pinmux), the green-wireless left those pins unused while sacrificing P9/P8 expansion header pins for the wifi/bt chip Mar 23 20:21:04 ah I knew I had a comparison... https://pastebin.com/Fi8Vh0n5 Mar 23 20:21:17 it doesn't include the BBBW for comparison though, just BBB vs BBGW Mar 23 20:27:33 Here is BBB & BBB Enhanced. You are correct minor change in name but function the same Mar 23 20:27:33 https://www.google.com/search?q=beaglebone+enhanced+pinout&client=firefox-b-1-d&biw=1280&bih=594&sxsrf=ALeKk003VhTDfzHo-xV-y7D2QvbewFgYaA:1584994742448&tbm=isch&source=iu&ictx=1&fir=khtMprSXptDN-M%253A%252CIBpEu8okEV--2M%252C_&vet=1&usg=AI4_-kRP91g0HPB7tOllv9lT4QfAwq_jSA&sa=X&ved=2ahUKEwikpuDEtbHoAhUPn-AKHSimBOcQ9QEwAXoECAkQFg#imgrc=joO9smQm2eSP8M Mar 23 20:34:53 Also the BBB and BBBE played with location of power jack Mar 23 20:53:23 yeah other stuff may be different, e.g. the BBBW has micro-usb instead of mini-usb, but that's not particularly relevant for the original topic of attaching a cape :) Mar 23 20:59:46 Yep Mar 24 00:06:54 hmm the next BB would be tough. You have the legacy pin out (which in the pocket beagle is different). The AM3558 has the OSD3558 to make it MUCH easier to make boards (curse the complex power scheme on the AM3558?) Mar 24 00:07:35 The AI seems to keep the legacy connector would be nice to use more of the IO (honestly). Mar 24 00:24:21 actually I ment have more io. Mar 24 00:28:52 well you do have more IO on the AI since its built-in features (like eMMC and HDMI) do not conflict with any expansion header pins, plus many pins are connected to two SoC pins for greater diversity in pinmux options Mar 24 00:29:07 if you want more I/O of the AM572x, there's the bbx15 Mar 24 00:30:01 and the power scheme of the AM335x is really not complex at all, it's among the simplest of the SoCs I'm familiar with Mar 24 00:30:15 or possibly just the simplest. Mar 24 00:31:05 really? it is simplier then the davinci? Mar 24 00:31:40 which "davinci" are you referring? (it's about as specific as calling the am335x "the sitara") Mar 24 00:31:54 any of them Mar 24 00:32:03 as a family Mar 24 00:32:20 they're not a family, they're a marketing name, just like sitara Mar 24 00:32:40 really? Mar 24 00:32:46 in fact some dies get either marketed as Sitara or as Davinci depending on efuse bits Mar 24 00:32:55 they are the SoCs I am the last familiar with Mar 24 00:34:27 let's say... the older DM6446 Mar 24 00:34:31 (e.g. the centaurus die is the Davinci DM814x but also the Sitara AM387x Mar 24 00:34:33 ) Mar 24 00:34:47 but yeah I'm not familiar at all with TI's older SoCs Mar 24 00:34:58 'k nevermind then Mar 24 00:35:05 at least not to the extent that I know their power supply requirements Mar 24 00:38:34 but yeah I should have said modern SoCs... I didn't have ARM9 stuff in mind :P Mar 24 00:39:00 i group MMU enabled ARMs together Mar 24 00:40:20 regardless, I did say "of the SoCs I'm familiar with" :P Mar 24 00:41:02 GenTooMan: what part of the AM335x power scheme do you consider to be complex enough to curse? Mar 24 00:41:31 it mostly just has some basic power sequencing requirements that the pmic takes care of Mar 24 00:53:41 the simplest power-up scheme for the am335x seems to be: https://pastebin.com/uXdFDhdz Mar 24 00:54:01 which really doesn't seem very burdensome to me Mar 24 00:55:23 2 op-amps and 2 fet switches to implement that? Mar 24 00:56:39 well typicaly a pmic is less hassle, especially since if you want to use higher OPPs (e.g. 1 GHz operation) you need the MPU supply voltage to be configurable Mar 24 00:56:53 (under software control) Mar 24 00:56:59 *nod* Mar 24 00:57:27 but it would be a simplier setup then the Octavo stuff Mar 24 00:57:35 ? Mar 24 00:58:08 what do you mean? the osd335x already includes the pmic Mar 24 00:58:34 I guess the next pain point for a simple system is the DDR Mar 24 00:58:49 which the osd335x also includes :P Mar 24 00:58:53 I am thinking how much simplier can I get it for say... a dead bug system Mar 24 00:59:26 https://twitter.com/pdp7/status/1100349116515827712 Mar 24 00:59:39 so far other then the Octavo stuff, the Pic32 is the only other simple system Mar 24 01:00:00 i don't like the way Octavo have hard coded some of their stuff Mar 24 01:00:18 pic32 are MCUs, not SoCs... there are plenty of simple microcontrollers Mar 24 01:00:50 zmatt: I think mine predatesthat - http://www.hy-research.com/CardVKS/ Mar 24 01:01:01 well at least in the osd335x-sm they fixed some grievances of the original osd335x Mar 24 01:01:08 zmatt: pic32 has a SoC offering that runs full Linux Mar 24 01:01:24 Z8, Z80, stamp Mar 24 01:02:44 ds2: even pic calls it an MCU though :P Mar 24 01:03:45 Gee, are the stamps still made? Mar 24 01:05:06 zmatt, is there a way to tell what wifi chip drivers are loaded on the BBB? Mar 24 01:05:28 kenunix they are basic ... :D Mar 24 01:05:29 zmatt: so this is an MCU despite what they label it? https://www.microchip.com/design-centers/32-bit/pic-32-bit-mcus/pic32mz-da-family Mar 24 01:06:30 gentooman, basic? Mar 24 01:06:45 yes, even in the url. 200 MHz mips32, supports up to 32 MB DDR2-400 ... I'm sure linux will run great on that :P Mar 24 01:08:30 of course the line between big mcu and small SoC can be vague (well, technically it just depends on whether it has internal non-volatile storage or not, but intuitively there tend to be more noticable differences) Mar 24 01:11:02 ah that one is even bigger than the one I found googling Mar 24 01:16:10 nxp nowadays also has MCUs with a Cortex-A5 that can run linux (MAC57D5xx) Mar 24 01:17:05 GenTooMan: what were you referring to with "curse the complex power scheme on the AM3558?" ? Mar 24 01:34:38 Anyboy running Windows 10? Mar 24 01:35:06 Anybody running Windows 10? **** ENDING LOGGING AT Tue Mar 24 02:59:57 2020