[beagleboard] Re: pru support for 4.4.84-ti-r120

2017-09-06 Thread Kasimir
Hi Robert, this is my current status ( hop I follow your advice correctly ): /opt/scripts/tools/version.sh git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f] eeprom:[A335BNLT000C1914BBBK0031] dogtag:[BeagleBoard.org Debian Image 2017-08-31] bootloader:[microSD-(push-button)]:[/dev/mmcblk0

[beagleboard] Re: DDR3 Timings for BBG Wireless

2017-09-06 Thread 'Ryan' via BeagleBoard
Hi Robert, >From my understanding, We need to input the timings to a Tool provided by TI and then it generates the values for each chip. This is different for different chips as timings are different. I wanted to find out these timings. Also, I did not see anywhere AM335x will auto calibrate t

[beagleboard] Re: pru support for 4.4.84-ti-r120

2017-09-06 Thread Kasimir
Hi, attached is my simple testcase. puls_gen.c is the loader, pru.c is the program for pru1. It's very simple. First I write some known values in shared memory. Then I load pru progam and activate it. pru1 is moving 2 values ( just to see that it works ) and at the end it should toggle P8_45 (Pi

Re: [beagleboard] Re: Change PySerial or other module similar

2017-09-06 Thread daniel . diaz . benito
If you just have to send bytes, you can find useful to use a bytearray. *[Python 3]* serial.write(bytearray([255])) serial.write(bytearray([2, 75, 250])) The struct module is still useful to send C style values, but I suggest you make explicit whether you are using little or big-endian to avoid c

[beagleboard] Sharing a bit more on Kali Linux with users of beagleboard.net

2017-09-06 Thread Adriana Guevara
Hi , I noticed you wrote about Kali Linux on your site, here: beagleboard.net/project It is great to have you helping users get to know Kali. Mr Ghaznavi-Zadeh published a chapter from his book "Kali Linux - A guide to Ethical hacking" and it is available for free here:

Re: [beagleboard] UART PWM Interference

2017-09-06 Thread ojc234
Thank you thank you thank You! You are right. There are 8 ground terminals on the GPIO - they seem to be there for a reason - when I plug the xbee GND directly into one of those (make the path to the BBB short) I get ~zero errors in communication. When I create a secondary Ground reference plane

Re: [beagleboard] Re: pru support for 4.4.84-ti-r120

2017-09-06 Thread Robert Nelson
On Wed, Sep 6, 2017 at 3:57 AM, Kasimir wrote: > Hi Robert, > this is my current status ( hop I follow your advice correctly ): > /opt/scripts/tools/version.sh > git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f] > eeprom:[A335BNLT000C1914BBBK0031] > dogtag:[BeagleBoard.org Debian Image

Re: [beagleboard] Issues loading capes

2017-09-06 Thread Tarmo Kuuse
On Wednesday, September 6, 2017 at 3:51:46 AM UTC+3, RobertCNelson wrote: > > > > On Sep 5, 2017 5:07 PM, "Peter Lawler" > > wrote: > > Thanks, I'll check them out. > > Just glancing at the doc now, I'm not immediately seeing to how to load > while.runing a kernel, unload then reload an newer

[beagleboard] Re: Beaglebone Black - Power supply and shutdown process.

2017-09-06 Thread Tarmo Kuuse
On Tuesday, September 5, 2017 at 3:12:44 AM UTC+3, michael.ja...@gmail.com wrote: > > I am attempting to design a power backup for the beaglebone to ensure > corruption does not occur when power is lost. I understand this can happen. > Apparently it has happened with this product. > My experien

[beagleboard] Re: how to get read-only files system these days?

2017-09-06 Thread Tarmo Kuuse
On Tuesday, September 5, 2017 at 1:45:05 AM UTC+3, Britton Kerin wrote: > > Any help modifying the above recipe or pointer to how to do it these > days would be appreciated. > I just declare the root file system as read-only in fstab and create some ramdisks for stuff that needs to be writable.

[beagleboard] Re: pru support for 4.4.84-ti-r120

2017-09-06 Thread Kasimir
Hello, based on this description I have the following now, think the device tree should work. Interesting is, I have to send echo RoboticsCape > /sys/devices/platform/bone_capemgr/slots & in background, otherwise the prompt is gone. But system is still working. cat /sys/devices/platform/bone_cap

Re: [beagleboard] Failed to enable UART1, Ubuntu 16.04

2017-09-06 Thread daniel . diaz . benito
Thanks Robert, you saved my day. I lost a couple of days with UART not working after upgrading to Debian 9. Finally after having a look at the posts in the mailing list I found this and figured out 'cape_enable=bone_capemgr.enable_partno=BB-UART1' is not enough anymore. It is perhaps worthed to i

[beagleboard] USB peripheral mode failure

2017-09-06 Thread conanwhf
Hi all, I'm working on a device designed base on BeagleBoneBlack, but there is something wrong in OTG mode. First of all, the hardware is modified for ID pin and I also can get the right state in both host & peripheral mode. I modify the dts file in kernel/arch/arm/boot/dts/, and re-define t

[beagleboard] MQTT WebRTC STUN TURN ICE

2017-09-06 Thread Richard
I have a nice BBB Node Red application that runs on my LAN quite nicely. Now, I'd like to be able to transport it and access it remotely. I see two problems with this. 1) To use it on a new system, I have to get through its router. This usually entails forwarding port 1880 to the BBB, but it wou

Re: [beagleboard] Re: DDR3 Timings for BBG Wireless

2017-09-06 Thread Jason Kridner
On Wed, Sep 6, 2017 at 6:05 AM 'Ryan' via BeagleBoard < beagleboard@googlegroups.com> wrote: > Hi Robert, > > From my understanding, We need to input the timings to a Tool provided by > TI and then it generates the values for each chip. This is different for > different chips as timings are differ