[beagleboard] Live stream of talk at Maker Faire New York

2017-09-14 Thread Jason Kridner
Electromaker.io (@ElectromakerIO)
9/11/17, 5:50 AM
Wanna know the latest news from #Beagleboard? Tune into our FB live stream 23rd 
Sept 12:30 PM (ET) to find out! goo.gl/s5vafg pic.twitter.com/3drZeljA6Z

Download the Twitter app

-- 
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/0CD627D6-E01F-4D21-93C0-81F1AFE0ADE7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: GPS, GPS, GPS and More!

2017-09-14 Thread Mala Dies
Hello,

I am having complications with import. See here: *ImportError: No module 
named pyupm_grovegprs*. Is there a way to import this module? If there is a 
way to import this module, where should I file it?

Seth




On Thursday, September 14, 2017 at 7:47:49 PM UTC-5, Mala Dies wrote:
>
> Hello,
>
> Seth here. I am currently dealing with the software mentioned above for 
> the Grove GPS module. I am not getting any reads from the software just 
> yet. I am sure I am way off but I have an empty prompt after running the 
> file. It does not give any readings from the print functions and I do not 
> get any info. on what should happen next.
>
> For now, the software runs (supposedly) and no errors are returned.
>
> Seth
>
> P.S. Are you messing with the Grove GPS module too? If so, can you give 
> any ideas or recommendations on this specific module?
>
> On Wednesday, September 13, 2017 at 8:30:20 PM UTC-5, Dennis Lee Bieber 
> wrote:
>>
>> On Wed, 13 Sep 2017 16:44:42 -0700 (PDT), Mala Dies 
>>  declaimed the following: 
>>
>> >Hello, 
>> > 
>> >I received a message from the U-Blox people and on the U-Blox site. They 
>> >said something about Wine. I looked into it. It is only for 32 bit 
>> >architecture and not for ARM. 
>> > 
>>
>> The BBB IS a 32-bit architecture (the RPi-3 is actually 64-bit -- 
>> but 
>> as the RPi foundation is only releasing 32-bit OS, a lot of that 
>> capability 
>> is lost).. 
>>
>> What the BBB is NOT is /Intel/ architecture. This is needed as 
>> WINE is 
>> just a system call interface translating win32 system calls to the 
>> nearest 
>> equivalent Linux functions. 
>> -- 
>> Wulfraed Dennis Lee Bieber AF6VN 
>> wlf...@ix.netcom.comHTTP://wlfraed.home.netcom.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/38bf023e-3d8d-4629-8aee-34111386937b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: GPS, GPS, GPS and More!

2017-09-14 Thread Mala Dies
Hello,

Seth here. I am currently dealing with the software mentioned above for the 
Grove GPS module. I am not getting any reads from the software just yet. I 
am sure I am way off but I have an empty prompt after running the file. It 
does not give any readings from the print functions and I do not get any 
info. on what should happen next.

For now, the software runs (supposedly) and no errors are returned.

Seth

P.S. Are you messing with the Grove GPS module too? If so, can you give any 
ideas or recommendations on this specific module?

On Wednesday, September 13, 2017 at 8:30:20 PM UTC-5, Dennis Lee Bieber 
wrote:
>
> On Wed, 13 Sep 2017 16:44:42 -0700 (PDT), Mala Dies 
>  declaimed the following: 
>
> >Hello, 
> > 
> >I received a message from the U-Blox people and on the U-Blox site. They 
> >said something about Wine. I looked into it. It is only for 32 bit 
> >architecture and not for ARM. 
> > 
>
> The BBB IS a 32-bit architecture (the RPi-3 is actually 64-bit -- 
> but 
> as the RPi foundation is only releasing 32-bit OS, a lot of that 
> capability 
> is lost).. 
>
> What the BBB is NOT is /Intel/ architecture. This is needed as 
> WINE is 
> just a system call interface translating win32 system calls to the nearest 
> equivalent Linux functions. 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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/c7ecb9f1-1276-4e03-86ba-fd491fe5ca6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: ADC reading by PRU

2017-09-14 Thread zlw8844

I agree, and I found the same data repeat problem using the continuous 
code, it does not look like a data loss. I do a 3.6 kHz sampling rate and 
observed that every 7 samples, I can see the value of two adjacent samples 
are very close to each other (see the figure below). Anyway, would you mind 
sharing your code with us to solve the problem? Thanks very much in advance.





On Tuesday, May 26, 2015 at 9:39:38 AM UTC-4, marcelo...@gmail.com wrote:
>
> I was wrong about the number 1, actually after some experiments I noticed 
> that I'm still losing samples, even after setting the ACK_CLKDIV to 
> something that divides the 24MHz by 3. Anyway it is useful to know that you 
> can obtain higher sample rates by setting a lower value to that register. 
>
> I'd also like to add that the continuous mode that you set on the step 
> config seems not good. I noticed it after sampling higher frequency waves, 
> however even on low frequency ones there's a noticeable step on the 
> sampling: every 14-15 samples had approximately the same value... I solved 
> that by setting STEPCONFIG it to the default one-shot mode and then the PRU 
> request a sample when it thinks it's time to. To request a sample, re-set 
> the bit on the STEPENABLE register. 
>
> My last step is to discover how to solve the lost samples problem... 
> When I'm sampling at 300kSps I noticed I lose 358 samples every 5005 
> samples. At 30kSps the proportion was 5 to 500.

-- 
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/75de1e0b-a477-46dc-b47f-addba90f3f5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: beaglebone auto loading handled by U-Boot

2017-09-14 Thread francois . heremans
Did you find a solution to your problem? I am facing the same issue...

Le mercredi 14 juin 2017 17:30:16 UTC+2, daniel.er...@gmail.com a écrit :
>
>
> I have two beaglebone boards...both SanCloud
>
> I am trying to use /boot/uEnv.txt to load cape overlays...
>
> One board the cape loads, the other board the cape does not...
>
> dmesg showing board #1 below the cape loads @ 2.526116...
>
> [2.368226] bone_capemgr bone_capemgr: Baseboard: 
> 'A335BNLT,SE0A,0617BBEF49D3'
> [2.368259] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black - #slots=4
> [2.406037] bone_capemgr bone_capemgr: slot #0: No cape found
> [2.446033] bone_capemgr bone_capemgr: slot #1: No cape found
> [2.486034] bone_capemgr bone_capemgr: slot #2: No cape found
> [2.526036] bone_capemgr bone_capemgr: slot #3: No cape found
> [2.526074] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPI1-01' VER 'N/A' PR '0'
> [2.526085] bone_capemgr bone_capemgr: slot #4: override
> [2.526100] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 4
> [2.526116] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> Name,00A0,Override Manuf,BB-SPI1-01'
>
>
>
> vs. this board #2 below that doesn't work shows "auto loading handled by 
> U-Boot" @ 2.373229
>
> [2.373029] bone_capemgr bone_capemgr: Baseboard: 
> 'A335BNLT,SE0A,0617BBEF494F'
> [2.373063] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black - #slots=4
> [2.373098] bone_capemgr bone_capemgr: slot #0: auto loading handled by 
> U-Boot
> [2.373120] bone_capemgr bone_capemgr: slot #1: auto loading handled by 
> U-Boot
> [2.373159] bone_capemgr bone_capemgr: slot #2: auto loading handled by 
> U-Boot
> [2.373181] bone_capemgr bone_capemgr: slot #3: auto loading handled by 
> U-Boot
> [2.373205] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPI1-01' VER 'N/A' PR '0'
> [2.373216] bone_capemgr bone_capemgr: slot #4: override
> [2.373229] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
> U-Boot
>
>
> Both have the same uboot version string 
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2017.05-2-gc0970ed183]
>
> cape overlay files are present on both boards @ /lib/firmware
>
> When I update initramfs I see this...
> update-initramfs: Generating /boot/initrd.img-4.4.62-ti-r105
>
>
> My /boot/uEnv.txt looks like this on both boards...
>
> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>
> uname_r=4.4.62-ti-r105
> #uuid=
> #dtb=
>
>
> ###U-Boot Overlays###
> ###Documentation: 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
> ###Master Enable
> enable_uboot_overlays=1
> ###
> ###Overide capes with eeprom
> #uboot_overlay_addr0=/lib/firmware/.dtbo
> #uboot_overlay_addr1=/lib/firmware/.dtbo
> #uboot_overlay_addr2=/lib/firmware/.dtbo
> #uboot_overlay_addr3=/lib/firmware/.dtbo
> ###
> ###Additional custom capes
> #uboot_overlay_addr4=/lib/firmware/.dtbo
> #uboot_overlay_addr5=/lib/firmware/.dtbo
> #uboot_overlay_addr6=/lib/firmware/.dtbo
> #uboot_overlay_addr7=/lib/firmware/.dtbo
> ###
> ###Custom Cape
> #dtb_overlay=/lib/firmware/.dtbo
> ###
> ###Disable auto loading of virtual capes (emmc/video/wireless/adc)
> #disable_uboot_overlay_emmc=1
> #disable_uboot_overlay_video=1
> #disable_uboot_overlay_audio=1
> #disable_uboot_overlay_wireless=1
> #disable_uboot_overlay_adc=1
> ###
> ###PRUSS OPTIONS
> ###pru_rproc (4.4.x-ti kernel)
> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
> ###pru_uio (mainline kernel)
> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
> ###
> ###Cape Universal Enable
> #enable_uboot_cape_universal=1
> ###
> ###Debug: disable uboot autoload of Cape
> #disable_uboot_overlay_addr0=1
> #disable_uboot_overlay_addr1=1
> #disable_uboot_overlay_addr2=1
> #disable_uboot_overlay_addr3=1
> ###
> ###U-Boot fdt tweaks...
> #uboot_fdt_buffer=0x6
> ###U-Boot Overlays###
>
> cmdline=coherent_pool=1M net.ifnames=0 quiet
>
> #In the event of edid real failures, uncomment this next line:
> #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e
>
> ##Example v3.8.x
> #cape_disable=capemgr.disable_partno=
> #cape_enable=capemgr.enable_partno=
>
> ##Example v4.1.x
> cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> cape_enable=bone_capemgr.enable_partno=BB-SPI1-01
> ##enable Generic eMMC Flasher:
> ##make sure, these tools are installed: dosfstools rsync
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>
> I presently don't have access to boot console traffic.
>
> Why does one board report auto loading handled by U-Boot, while the other 
> board does not (and seems to load overlays and work properly)?
>

-- 
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 

[beagleboard] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

2017-09-14 Thread sami kamal
YouTube videos of



 U.S. Congress money laundering hearing


of

Saudi Billionaire  " Maan  Al sanea"

 with *bank of America*


and  The  owner of Saad Hospital and  Schools

 in the Eastern Province in *Saudi Arabia*



and the Chairman of the Board of Directors of Awal Bank  in *Bahrain*


With Arabic Subtitles





*موقع اليوتيوب الذي عرض جلسة استماع الكونجرس الأمريكي *

* لمتابعة نشاطات غسل الأموال ونشاطات*



*السعودي معن عبدالواحد الصانع*



*مالك مستشفى  وشركة سعد  ومدارس سعد بالمنطقة الشرقية بالسعودية   ورئيس مجلس
ادارة بنك اوال البحريني*



*مترجم باللغة العربية*



http://www.youtube.com/watch?v=mIBNnQvhU8s

-- 
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/CAH%3DZeA4A_u9yD%2BhazV%3DF-u%3DujN_oFgSkc1-F2xqm2Ht0P-pH3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 1:26 PM, Todd Woolums  wrote:
> No worries at all considering how fast you looked and saw the problem :)
>
> Sorry I'm a newbie when it comes to this after builds are done how can I
> pull that down on a fresh load of the BBB 9.1 image?

Well till the builds finish:

wget http://rcn-ee.online/builds/linux-image-4.9.50-ti-r59.1_1cross_armhf.deb
sudo dpkg -i linux-image-4.9.50-ti-r59.1_1cross_armhf.deb
sudo reboot

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/CAOCHtYjw8Lh76%3DhFNM7y6sUEhC-xe1s3%3DdkBOBkd%3DSkHLzT2Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] RTC reset after Beaglebone boot

2017-09-14 Thread William Hermans
You could also set time on the second rtc during setup after updating the
time via nap date then just run a script at boot, and occasionally  (once a
day?) Using a system timer.

With the new fix Robert implemented.  .
Probably more hassle than it's worth , but it's  not that difficult, and it
works.

On Sep 14, 2017 10:03 AM, "Robert Nelson"  wrote:

> On Thu, Sep 14, 2017 at 11:50 AM, Robert Nelson 
> wrote:
> > On Thu, Sep 14, 2017 at 12:59 AM,   wrote:
> >> Hello,
> >> I have intefaced RTC DS1307 with Beaglbone. However, after the
> beaglebone
> >> boots up, its time is reset and RTC takes this reset time. Use of NTP
> would
> >> not be feasible since Beaglebone would be used in a remote location
> with no
> >> internet connection. What would be the solution to this issue ?
> >
> > As of this week, we have an easy solution. (using u-boot overlays of
> > course), the trick is the rtc "aliases", so that the ds1307 gets rtc0
> >
> > Seee either :
> >
> > https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-I2C1-MCP7940X-00A0.dts
> >
> > or:
> >
> > https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-I2C2-PCF8523-00A0.dts
>
> and here's it working: (eth is disconnected)
>
> debian@beaglebone:~$ dmesg | grep rtc
> [1.594096] omap_rtc 44e3e000.rtc: already running
> [1.594335] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as
> rtc1
> [1.776976] rtc-ds1307 1-0068: registered as rtc0
> [1.795900] rtc-ds1307 1-0068: setting system clock to 2017-09-14
> 17:01:12 UTC (1505408472)
>
> 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/CAOCHtYjZ3hbMsv7QUYw0A3TtKYr-
> dmEGENJa5U9kDzYomr4QBQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALHSORoB%3DGXS37v06fspJTfJvpuWhG7nixNcnMVM_FCNNTUXOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Todd Woolums
No worries at all considering how fast you looked and saw the problem :)

Sorry I'm a newbie when it comes to this after builds are done how can I 
pull that down on a fresh load of the BBB 9.1 image?



On Thursday, September 14, 2017 at 12:06:26 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Sep 14, 2017 at 11:45 AM, Todd Woolums  > wrote: 
> > Awesome, I assume at some point I can do a git pull at some time?  Sorry 
> I 
> > dont know how the changes make their way into the mix. 
>
> Yeah, sadly, i tagged and pushed out 4.9.50-ti-r59 earlier this 
> morning, so you'll have to use the repo here: 
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev 
>
> once all the builds get built and pushed out (another day or so) i can 
> tag and push a new build with that change.. 
>
> 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/24d07e2b-6e03-4da8-bb37-92acc95f453d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 11:45 AM, Todd Woolums  wrote:
> Awesome, I assume at some point I can do a git pull at some time?  Sorry I
> dont know how the changes make their way into the mix.

Yeah, sadly, i tagged and pushed out 4.9.50-ti-r59 earlier this
morning, so you'll have to use the repo here:

https://github.com/RobertCNelson/ti-linux-kernel-dev

once all the builds get built and pushed out (another day or so) i can
tag and push a new build with that change..

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/CAOCHtYjT8QzKHAa9q4%2B%2B3nW%2BxJYrYtKooSbCzcTXw%2BszCEKwjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] RTC reset after Beaglebone boot

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 11:50 AM, Robert Nelson  wrote:
> On Thu, Sep 14, 2017 at 12:59 AM,   wrote:
>> Hello,
>> I have intefaced RTC DS1307 with Beaglbone. However, after the beaglebone
>> boots up, its time is reset and RTC takes this reset time. Use of NTP would
>> not be feasible since Beaglebone would be used in a remote location with no
>> internet connection. What would be the solution to this issue ?
>
> As of this week, we have an easy solution. (using u-boot overlays of
> course), the trick is the rtc "aliases", so that the ds1307 gets rtc0
>
> Seee either :
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C1-MCP7940X-00A0.dts
>
> or:
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-PCF8523-00A0.dts

and here's it working: (eth is disconnected)

debian@beaglebone:~$ dmesg | grep rtc
[1.594096] omap_rtc 44e3e000.rtc: already running
[1.594335] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc1
[1.776976] rtc-ds1307 1-0068: registered as rtc0
[1.795900] rtc-ds1307 1-0068: setting system clock to 2017-09-14
17:01:12 UTC (1505408472)

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/CAOCHtYjZ3hbMsv7QUYw0A3TtKYr-dmEGENJa5U9kDzYomr4QBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] RTC reset after Beaglebone boot

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 12:59 AM,   wrote:
> Hello,
> I have intefaced RTC DS1307 with Beaglbone. However, after the beaglebone
> boots up, its time is reset and RTC takes this reset time. Use of NTP would
> not be feasible since Beaglebone would be used in a remote location with no
> internet connection. What would be the solution to this issue ?

As of this week, we have an easy solution. (using u-boot overlays of
course), the trick is the rtc "aliases", so that the ds1307 gets rtc0

Seee either :

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C1-MCP7940X-00A0.dts

or:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-PCF8523-00A0.dts

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/CAOCHtYisyM2Js-UJSoDrn%3DA4Lpwj1x1jxs1zwJ4ZvGNGwrZJWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Todd Woolums
Awesome, I assume at some point I can do a git pull at some time?  Sorry I 
dont know how the changes make their way into the mix.

--Todd

On Thursday, September 14, 2017 at 11:33:09 AM UTC-5, RobertCNelson wrote:
>
> and staged up: 
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/9813530fb39046d8a6533ad1268d31bd4387c261
>  
>
> 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/351eb128-a893-4ce2-84f9-3470adfe1b87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: RTC reset after Beaglebone boot

2017-09-14 Thread Tarmo Kuuse
On Thursday, 14 September 2017 17:25:09 UTC+3, Ritisha Shettigar wrote:
>
> I have intefaced RTC DS1307 with Beaglbone. However, after the beaglebone 
> boots up, its time is reset and RTC takes this reset time. Use of NTP would 
> not be feasible since Beaglebone would be used in a remote location with no 
> internet connection. What would be the solution to this issue ?
>

There's a reasonably easy hack:
https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time
 

A proper solution would probably involve a kernel change to replace the 
default RTC device (which is currently the chip's nearly useless internal 
one at /dev/rtc0). I'd love to figure out how that works, as I need to do 
the same thing.

--
Kind regards,
Tarmo Kuuse

-- 
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/b98c9c08-c8e1-4383-be4c-da4ac80366ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
and staged up:

https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/9813530fb39046d8a6533ad1268d31bd4387c261

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/CAOCHtYhVeQCMnvoB7C-ZQNi%3DAYV3ukAap0K8JgUARDVSJu7%3DbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
Okay got it, it's actually the same bug we saw in v4.4.x-ti:

hidden ssid breaks the wifi scan:

Just need to forward port this patch:

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.4.y/patches/drivers/wireless/0001-net-wireless-SanCloud-wifi-issue-when-associating-wi.patch

(Just tested it with v4.9.x-ti and wifi is working)

(and i need to rename it this time so don't drop it)

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/CAOCHtYg-Dw_wQOfwVenHpaudh3v6KXKsgebaxx36GQ57Ej9N9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 10:33 AM, Todd Woolums  wrote:
> This is the adapter
> https://www.amazon.com/gp/product/B00H95C0A2/ref=oh_aui_detailpage_o00_s00?ie=UTF8=1

Yeah, i have that adapter here..

Definitely a regression in v4.9.x, use v4.4.x till we figure out what broke..

I just ran:

cd /opt/scripts/tools/
sudo ./update_kernel.sh --ti-channel --lts-4_4
sudo reboot

Scan completed for wifi
connmanctl> services
*AO Wiredethernet_985dad87dfb2_cable
BeagleBone-ABCDEF
wifi_00e180405864_426561676c65426f6e652d414243444546_managed_psk
DKE_Employee
wifi_00e180405864_444b455f456d706c6f796565_managed_ieee8021x
 wifi_00e180405864_hidden_managed_psk
DKE_Guestwifi_00e180405864_444b455f4775657374_managed_psk
CloudGate-X13M
wifi_00e180405864_436c6f7564476174652d5831334d_managed_psk
connmanctl> quit

debian@beaglebone:~$ uname -r
4.4.87-ti-r121
debian@beaglebone:~$ lsusb
Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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/CAOCHtYjReEakY_W77T%3DH1NT5hbYdFaJ1JkRWxqOD%2B5ArSE5r8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Todd Woolums
This is the adapter
https://www.amazon.com/gp/product/B00H95C0A2/ref=oh_aui_detailpage_o00_s00?ie=UTF8=1



On Thursday, September 14, 2017 at 10:28:57 AM UTC-5, RobertCNelson wrote:
>
> On Thu, Sep 14, 2017 at 10:18 AM, Todd Woolums  > wrote: 
> > I can't get wifi to work with a RT5370 adapter in the latest BBB image 
> for 
> > Debian 9.1.  This adapter works in older versions so I'm unsure what 
> else to 
> > look at.  Any pointers/help would be appreciated. 
>
> What manufacture/model/revision? Do you have an amazon part link? 
>
> You can downgrade to v4.4.x-ti: 
>
> cd /opt/scripts/tools/ 
>
> sudo ./update_kernel.sh --ti-channel --lts-4_4 
>
> 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/9e918496-c12f-49c1-a43d-3f76a1c3ad04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Robert Nelson
On Thu, Sep 14, 2017 at 10:18 AM, Todd Woolums  wrote:
> I can't get wifi to work with a RT5370 adapter in the latest BBB image for
> Debian 9.1.  This adapter works in older versions so I'm unsure what else to
> look at.  Any pointers/help would be appreciated.

What manufacture/model/revision? Do you have an amazon part link?

You can downgrade to v4.4.x-ti:

cd /opt/scripts/tools/

sudo ./update_kernel.sh --ti-channel --lts-4_4

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/CAOCHtYiJ9QGoF0SvC_KTNyojjgr80zu%3Dt7Uk7ydZXpxDtovfOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Wifi RT5370 Debian 9.1

2017-09-14 Thread Todd Woolums
 

I can't get wifi to work with a RT5370 adapter in the latest BBB image for 
Debian 9.1.  This adapter works in older versions so I'm unsure what else 
to look at.  Any pointers/help would be appreciated.


Thanks


*debian@beaglebone*:*~*$ connmanctl

Error getting VPN connections: The name net.connman.vpn was not provided by 
any connmanctl> enable wifi

Error wifi: Already enabled

connmanctl> scan wifi

Scan completed for wifi

connmanctl> services


connmanctl> 

*debian@beaglebone*:*~*$ uname -a

Linux beaglebone 4.9.45-ti-r57 #1 SMP PREEMPT Fri Aug 25 22:58:38 UTC 2017 
armv7l GNU/Linux

*debian@beaglebone*:*~*$ lsusb

Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless 
Adapter

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


*debian@beaglebone*:*~*$ lsusb -t

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M

|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=rt2800usb, 
480M


*debian@beaglebone*:*~*$ lsmod

Module  Size  Used by

snd_soc_simple_card 7959  0

snd_soc_simple_card_utils 6408  1 snd_soc_simple_card

omap_aes_driver24392  0

omap_sham  27230  0

crypto_engine   7219  1 omap_aes_driver

pruss_soc_bus   4788  0

omap_rng5864  0

rng_core9161  1 omap_rng

c_can_platform  7825  0

c_can  12883  1 c_can_platform

can_dev14919  1 c_can

arc42403  2

rt2800usb  19345  0

rt2800lib  84293  1 rt2800usb

rt2x00usb  13438  1 rt2800usb

rt2x00lib  50688  3 rt2800lib,rt2800usb,rt2x00usb

mac80211  690472  3 rt2800lib,rt2x00lib,rt2x00usb

cfg80211  589989  2 rt2x00lib,mac80211

rfkill 21767  3 cfg80211

snd_soc_davinci_mcasp21479  2

snd_soc_omap4317  1 snd_soc_davinci_mcasp

snd_soc_edma1546  1 snd_soc_davinci_mcasp

spi_omap2_mcspi13352  0

snd_soc_hdmi_codec  7631  1

snd_soc_core  198579  6 
snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_omap,snd_soc_simple_card

snd_pcm_dmaengine   6214  2 snd_soc_omap,snd_soc_core

evdev  13811  2

snd_pcm   105795  5 
snd_soc_davinci_mcasp,snd_pcm_dmaengine,snd_soc_hdmi_codec,snd_soc_omap,snd_soc_core

tps65217_charger5491  0

ti_am335x_adc   8160  0

snd_timer  24435  1 snd_pcm

kfifo_buf   4052  1 ti_am335x_adc

snd74026  3 snd_timer,snd_soc_core,snd_pcm

industrialio   65843  2 ti_am335x_adc,kfifo_buf

soundcore   8755  1 snd

uio_pdrv_genirq 4205  0

uio11036  1 uio_pdrv_genirq

usb_f_mass_storage 51414  2

usb_f_acm   8610  2

u_serial   13482  3 usb_f_acm

usb_f_ecm  11619  2

usb_f_rndis26880  2

u_ether13962  2 usb_f_ecm,usb_f_rndis

libcomposite   55392  16 
usb_f_ecm,usb_f_acm,usb_f_mass_storage,usb_f_rndis

iptable_nat 2512  0

nf_conntrack_ipv4  12035  1

nf_defrag_ipv4  2016  1 nf_conntrack_ipv4

nf_nat_ipv4 6857  1 iptable_nat

nf_nat 20785  1 nf_nat_ipv4

nf_conntrack  117614  3 nf_conntrack_ipv4,nf_nat_ipv4,nf_nat

iptable_mangle  2303  0

iptable_filter  2453  0

spidev  9322  0

pru_rproc  14966  0

pruss_intc  9092  1 pru_rproc

pruss  10889  1 pru_rproc

tieqep  9111  0

ip_tables  14529  3 iptable_mangle,iptable_filter,iptable_nat

x_tables   22165  3 iptable_mangle,ip_tables,iptable_filter


*debian@beaglebone*:*~*$ iwconfig

eth0  no wireless extensions.


usb0  no wireless extensions.


usb1  no wireless extensions.


wlan0 IEEE 802.11  ESSID:off/any  

  Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   

  Retry short limit:7   RTS thr:off   Fragment thr:off

  Power Management:off

  

lono wireless extensions.


can0  no wireless extensions.


can1  no wireless extensions.


*debian@beaglebone*:*~*$ ifconfig

eth0: flags=-28669  mtu 1500

ether 54:4a:16:e7:11:ef  txqueuelen 1000  (Ethernet)

RX packets 0  bytes 0 (0.0 B)

RX errors 0  dropped 0  overruns 0  frame 0

TX packets 0  bytes 0 (0.0 B)

TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

device interrupt 189  


lo: flags=73  mtu 65536

inet 127.0.0.1  netmask 255.0.0.0

inet6 ::1  prefixlen 128  scopeid 0x10

loop  txqueuelen 1  (Local Loopback)

RX packets 1280  bytes 88000 (85.9 KiB)

RX errors 0  dropped 0  overruns 0  frame 0

TX packets 1280  bytes 88000 

[beagleboard] ROSMIP

2017-09-14 Thread poinix
Hello World

I have made a ROS enabled version of EDUMIP. It is currently able to 
navigate using movebase. The code is here: https://github.com/poine/rosmip 
. Documentation might come at a later point.

Best Regards

Poine 

-- 
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/e90682ba-4171-4946-8b8d-8806b6ddeca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] RTC reset after Beaglebone boot

2017-09-14 Thread ritishashettigar28
Hello,
I have intefaced RTC DS1307 with Beaglbone. However, after the beaglebone 
boots up, its time is reset and RTC takes this reset time. Use of NTP would 
not be feasible since Beaglebone would be used in a remote location with no 
internet connection. What would be the solution to this issue ?

Ritisha

-- 
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/4eb7d40f-e48a-48c4-9037-65d43a48f159%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2017-09-14 Thread Kasimir
I still have the problem with pru1.
-Generated firmwares are : gen/puls_gen.out gen/decay95.out
root@beaglebone-ln:/media/SD32/home/ln/Programme/Puls_neu/source#* 
config-pin overlay cape-universala*
root@beaglebone-ln:/media/SD32/home/ln/Programme/Puls_neu/source# *config-pin 
p8.45 pruout*
root@beaglebone-ln:/media/SD32/home/ln/Programme/Puls_neu/source# *config-pin 
-q p8.45*
*P8_45 Mode: pruout*
root@beaglebone-ln:/media/SD32/home/ln/Programme/Puls_neu/source# make run
-copying firmware file gen/puls_gen.out to /lib/firmware/am335x-pru1-fw
*/bin/sh: 1: cannot create /sys/bus/platform/drivers/pru-**rproc/unbind: 
Permission denied*
*/bin/sh: 1: cannot create /sys/bus/platform/drivers/pru-**rproc/bind: 
Permission denied*

It's really confusing and time consuming without any result. Think the 
hardware is very useful and interesting,
but it's not an easy task to make it work.  

Am Dienstag, 5. September 2017 18:55:37 UTC+2 schrieb Kasimir:
>
> I want to use the HDMI outputs to drive external circuit. Required toggle 
> rate is between 1MHz and 10MHz.
> Have BB black.
> uname -a
> Linux beaglebone 4.4.84-ti-r120 #1 SMP Sun Aug 27 03:11:07 UTC 2017 
> armv7l GNU/Linux
> cat /etc/debian_version 
> 9.1
> So I have to use the PRU unit.
> I was searching example to have a starting point.
> But it sucks already with the first step.
>
> ll /sys/devices/bone_capemgr*
> ls: cannot access '/sys/devices/bone_capemgr*': No such file or directory
>
> I load the image from here: 
> http://debian.beagleboard.org/images/bone-debian-9.1-iot-armhf-2017-08-31-4gb.img.xz
>
> What is my mistake?
> Device tree compiler is up to date
> device-tree-compiler is already the newest version (1.4.4-0rcnee3~stretch+
> 20170719).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> Found a lot of hints to use the 3.8 kernel. Think that one is already some 
> years old, can't be true.
>
> Question: How to create the required device tree overlay, because /sys/
> devices/bone_capemgr* is not existing?
>
> Thanks for help
>
>
>
>
>

-- 
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/d5581556-33b9-4762-b336-393958db93c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.