Re: [beagleboard] Re: PocketBeagles are Unstable
On Sunday, December 3, 2017 at 4:21:33 PM UTC+1, Graham wrote: > > The PocketBeagle, when powered only by the Vin input (P1-pin1) is > unstable. > This is the power supply input, normally assigned to the barrel jack in > the BBB, or the AC adapter input in the TI docs. > > Not to be confused with the Vi input (P1-pin7) which is connected to Vusb0 > and Vusb1 on the PocketBeagle. > I'm not quite sure but isn't P1/7 the same as VDD on the BBB? In this case you definitely shouldn't use P1/1 for powering the board... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9de62b40-9e5c-459f-b258-8e500aa43a31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Free StarterWare replacement with support for PocketBeagle
If somebody is interested: TI has stopped further development of their bare metal support package "StarterWare" but there is a compatible and community-driven replacement available at https://sourceforge.net/projects/starterwarefree/ now. This project seem to contains a bunch of bug fixes the original StarterWare never got and even has support for the new PocketBeagle. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/d0539627-ad8f-4d5f-9f94-4e964fe9f5a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: DDR initialisation on PocketBeagle
Finally I could solve the problem: the guys from https://sourceforge.net/projects/starterwarefree/ have implemented support for PocketBeagle in their MLO. Not sure what the difference is to my code but theirs is working smoothly, now my application starts as expected. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6090c723-6aae-43b4-9350-ee4e4c2c92d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] prussdrv_open() on new debian kernel
On Sun, Dec 3, 2017 at 9:42 PM, Joseph Foster wrote: > [sudo] password for debian: > git:/opt/scripts/:[e5c23dc2a45f5c9ace291dd32e7c3d79edc1932d] > eeprom:[A335BNLTGW1ABBGW17052298] > model:[TI_AM335x_BeagleBone_Green_Wireless] > dogtag:[BeagleBoard.org Debian Image 2017-11-26] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2017.11-2-g7b415acfc1] > kernel:[4.14.3-bone5] > nodejs:[v6.12.0] > device-tree-override:[uboot_overlay_addr0=/lib/firmware/am335x-boneblack-nhdmi-overlay.dtb] > uboot_overlay_options:[enable_uboot_overlays=1] > uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/am335x-boneblack-nhdmi-overlay.dtb] There's your issue ^^ remove that option.. it's block the cape-universal overlay. With U-Boot overlays, you need to disable the onboard hardware like so: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjHBV9_eEy8-BJTm0pAv%3D7_wKjBsV%2BjpLx0RxFQHOQUEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] prussdrv_open() on new debian kernel
[sudo] password for debian: git:/opt/scripts/:[e5c23dc2a45f5c9ace291dd32e7c3d79edc1932d] eeprom:[A335BNLTGW1ABBGW17052298] model:[TI_AM335x_BeagleBone_Green_Wireless] dogtag:[BeagleBoard.org Debian Image 2017-11-26] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.11-2-g7b415acfc1] kernel:[4.14.3-bone5] nodejs:[v6.12.0] device-tree-override:[uboot_overlay_addr0=/lib/firmware/am335x-boneblack-nhdmi-overlay.dtb] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/am335x-boneblack-nhdmi-overlay.dtb] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] uboot_overlay_options:[enable_uboot_cape_universal=1] pkg:[bb-cape-overlays]:[4.4.20171120.0-0rcnee1~stretch+20171120] pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829] pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830] On Saturday, December 2, 2017 at 2:14:58 PM UTC-6, RobertCNelson wrote: > > On Sat, Dec 2, 2017 at 2:20 AM, Joseph Foster > > wrote: > > When setting config-pin P8.11 pruout, I get bash: > > /sys/devices/platform/ocp/ocp*P8_11_pinmux/state: No such file or > directory > > . Is there a specific overlay I need to use, my custom ones don't seem > to > > work and the cape-universal-00A0.dtbo overlay locks my beagle into a > boot > > loop. > > P8_11 should be auto loaded, lets' check out your: > > sudo /opt/scripts/tools/version.sh > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7f3bd6de-abfb-4cd4-bdb3-9115d40900bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] systemd-timesyncd question
In previous OS releases, such as Debian 8.8, systemd-timesyncd was used as the network time synchronization. It did an initial sync, then as it determined the time base correction necessary, corrected for the frequency error in the BBB's main clock, and kept increasing the time between network time syncs, until it was running/syncing about once every thirty minutes. You saw a bunch of line items in the syslogs that looked like the following Dec 3 13:34:50 BBG4 systemd-timesyncd[209]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.053s/0.011s/-72ppm Dec 3 14:08:58 BBG4 systemd-timesyncd[209]: interval/delta/delay/jitter/drift 2048s/+0.002s/0.055s/0.012s/-71ppm Now, in Debian 9.2, systemd-timesyncd is used for network time synchronization. But in the syslogs, you only see a single report of time sync at the first boot, and nothing further. Is systemd-timesyncd still doing a network sync every 30 minutes and just not logging it to syslog, or is it doing it less frequently? If it is doing it less frequently, what is the easiest way to get back to the 30 minute re-sync cycle with the clock correction? --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7b79b9fa-12a1-4a0a-a157-5e356cdcb810%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to use PocketBeagle analog inputs 5-7?
I can read analog inputs 0-4 from /sys/bus/iio/devices/iio:device0/in_voltage*N*_raw but I can't get analog inputs 5-7 to work. Inputs 5 and 6 don't have analog as a choice in config-pin: $ config-pin -l P1_2 default gpio gpio_pu gpio_pd pruout pruin Analog input 7 (P2_36) doesn't have any other function, but it ignores any analog input voltage. Is there a trick to using inputs 5-7 or is support under development? Ken -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a4d0f097-6383-4981-9ba6-e059fb0979f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] mikrobus fm click
Has anyone had any success with the mikrobus fm(SI4703) module? I cannot get the module to show on i2c-2 0x10 address. i have the weather click showing up on i2c-2 0x76. any insight would be appreciated. thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/843da2b0-243a-4685-9620-01241a633924%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: PocketBeagles are Unstable
I'll try again. The PocketBeagle, when powered only by the Vin input (P1-pin1) is unstable. This is the power supply input, normally assigned to the barrel jack in the BBB, or the AC adapter input in the TI docs. Not to be confused with the Vi input (P1-pin7) which is connected to Vusb0 and Vusb1 on the PocketBeagle. I have found that when running with Vin and Vi inputs strapped together, the problem does not occur. I will try a run with the power on Vi only and see what happens. During both test runs, there was a USB2-to-Ethernet adapter on USB1, but to make sure that the Ethernet driver is not the problem, I have run a PocketBeagle, powered from Vin with nothing else connected than a serial cable on UART0 console, and the unit still behaves the same. My opinion is that it is either a hardware or configuration problem with the PMIC. Stability Test Run - DEC 02 Both PocketBeagles are powered from the same lab-bench supply, via Vin. Good regulation at 5.00 Volts and plenty of current available from the lab-bench supply. === Time is UTC, defined as the time that systemd-timesyncd resyncs during the reboot. PocketBeagle-2 Linux beaglebone 4.9.61-ti-r76 #1 SMP PREEMPT Mon Nov 13 20:24:26 UTC 2017 armv7l GNU/Linux Start of test/manual reboot at Dec 2 21:52:18 UTC Autonomous reboots Dec 3 04:42:20 Dec 3 04:53:18 Dec 3 06:01:06 Dec 3 06:03:45 Dec 3 12:18:47 Dec 3 12:30:04 End of test: Sun Dec 3 13:47:05 UTC 2017 PocketBeagle-1 Linux PB1 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux Start of test/manual reboot at Dec 2 21:52:37 UTC Autonomous reboots at Dec 3 02:24:55 UTC End of Test: System had crashed, no lights, No Ethernet connectivity, had to reboot to recover syslogs Dec 3 13:50:34 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c7c27fa0-917e-4e96-a2f3-19feb5f65ef3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Problems setting up cape manager device tree overlay
I have previously set up the device tree overlay for UART with no problems using Debian Version 7x. In short, I compiled a device tree source file into a .dtbo file, and then loaded the overlay .dtbo file using the following: echo BB-UART2 > /sys/devices/bone_capemgr.*/slots // this works for debian version 7x and earlier It appears Debian version 8x has changed this location slightly and now is /sys/devices/platform/bone_capemgr/slots. when I compile the device tree source file and attempt to load using: echo BB-UART2 > /sys/devices/platform/bone_capemgr/slots I get the following response: -bash: echo: write error: File exists And the UART2 does not work I would like to know what I should be doing in Debian 8x to get this working. Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5d5a5812-36c3-49ca-a0c4-201dc18679f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] problem loading cape overlay with Debian 8.2
I am able to add a UART2 cape over lay in Debian 7.x but when I try with Debian 8.x I am not having much luck. For example, if I type: echo BB-UART2 > /sys/devices/platform/bone_capemgr/slots I get error: echo: write error: File exists Any suggestions. I can't figure this out. Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/fee20d6c-df75-4a54-90d6-b8d0ab48c981%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
