Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

[William Hermans]

Just a note, all workshops already sold out.

On Mon, Oct 16, 2017 at 2:47 PM, Robert Nelson 
wrote:

> On Mon, Oct 16, 2017 at 4:30 PM, CJA  wrote:
> > Hi Drew,
> > Awesome, I just received my PocketBeagle today from arrow.com.  Is this
> > going to be a full day workshop ? And are there any prerequisites, in
> terms
> > of getting acquainted to certain topic's before attending the workshop..
> > Thanks for the help - Carmelito
>
> What would you like us to talk about? ;)
>
> aka, i'm still writing everything up..  Definitely be going over
> u-boot, kernel, u-boot overlays, config-pin, adafruit-io... ;)
>
> 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/CAOCHtYh9XY%2B5WPhyhjAHquzjqs8N200v%
> 2BR30ORNe3QzCBdGtng%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/CALHSORr4LhecHbngkQ2db2o3hQ6zDQ2t5Ci8%3DkjbeFMDYGUP1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

[Robert Nelson]

On Mon, Oct 16, 2017 at 4:30 PM, CJA  wrote:
> Hi Drew,
> Awesome, I just received my PocketBeagle today from arrow.com.  Is this
> going to be a full day workshop ? And are there any prerequisites, in terms
> of getting acquainted to certain topic's before attending the workshop..
> Thanks for the help - Carmelito

What would you like us to talk about? ;)

aka, i'm still writing everything up..  Definitely be going over
u-boot, kernel, u-boot overlays, config-pin, adafruit-io... ;)

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

Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

[Drew Fustini]

Robert Nelson is running the workshop so hopefully he can elaborate on
those details.

On Oct 16, 2017 4:30 PM, "CJA"  wrote:

> Hi Drew,
> Awesome, I just received my PocketBeagle today from arrow.com.  Is this
> going to be a full day workshop ? And are there any prerequisites, in terms
> of getting acquainted to certain topic's before attending the workshop..
> Thanks for the help - Carmelito
>
>
> On Monday, October 2, 2017 at 11:31:07 AM UTC-7, Drew Fustini wrote:
>>
>> FYI - workshop at the Hackaday Superconference on weekend of November
>> 11th:
>>
>> "Rapid Prototyping & Linux Kernel Development with the PocketBeagle
>> Platform"
>>
>> http://mailchi.mp/hackaday/hackaday-superconference-workshop
>> -tickets-now-available?e=a6dd9d4b3b
>>
>> thanks,
>> drew
>>
> --
> 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/2261ba7d-ffc1-45a3-93d1-a5b2dbcaf870%40googlegroups.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/CAEf4M_BDoJzAbf3CuhnYhGtzxa57m5ZhPE0qi5ZrooVd_OzT2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

[CJA]

Hi Drew,
Awesome, I just received my PocketBeagle today from arrow.com.  Is this 
going to be a full day workshop ? And are there any prerequisites, in terms 
of getting acquainted to certain topic's before attending the workshop..
Thanks for the help - Carmelito


On Monday, October 2, 2017 at 11:31:07 AM UTC-7, Drew Fustini wrote:
>
> FYI - workshop at the Hackaday Superconference on weekend of November 
> 11th: 
>
> "Rapid Prototyping & Linux Kernel Development with the PocketBeagle 
> Platform" 
>
>
> http://mailchi.mp/hackaday/hackaday-superconference-workshop-tickets-now-available?e=a6dd9d4b3b
>  
>
> thanks, 
> drew 
>

-- 
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/2261ba7d-ffc1-45a3-93d1-a5b2dbcaf870%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How quick from power-on to PWM signals?

[Clyde McQueen]

Graham, thanks for the reply.

On Sunday, October 15, 2017 at 6:29:34 AM UTC-7, Graham wrote:
>
>
> Depending on which Beagle distribution, and what things you have 
> ripped out of them, they can take anywhere from 12 seconds to multiple 
> minutes to boot.
> So, either you need to create a very special custom uBoot to initialize 
> your ESC's, or add a power switch, that is under user software control, 
> that is not turned on until after the system has booted, and you can then 
> initialize the ESC's within your alloted time, after turning on the power 
> switch.
>
> --- 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/7c049b2a-35a1-4373-9677-28d8be7fc43f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Boot is extremely slow/hangs

[Alexander Rössler]

The boot hangs at a different position when I enable eMMC flashing:

[17:19:14:140] [ 4.730493] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware 
> Version = 0x192␍␊
>
> [17:19:14:197] Loading, please wait...␍␊
>
> [17:19:14:301] starting version 232␍␊
>
> [17:19:14:309] [ 4.908472] random: systemd-udevd: uninitialized urandom 
> read (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:337] [ 4.932103] random: systemd-udevd: uninitialized urandom 
> read (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:358] [ 4.937269] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:373] [ 4.937739] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:392] [ 4.942139] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:414] [ 4.943209] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:425] [ 4.943971] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:442] [ 4.944667] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:464] [ 4.945336] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:19:14:484] [ 4.950296] random: udevadm: uninitialized urandom read 
> (16 bytes read, 3 bits of entropy available)␍␊
>
> [17:21:07:358] Begin: Loading essential drivers ... done.␍␊
>
> [17:21:07:364] Begin: Running /scripts/init-premount ... done.␍␊
>
> [17:21:07:367] Begin: Mounting root file system ... Begin: Running 
> /scripts/local-top ... done.␍␊
>
> [17:21:07:390] Begin: Running /scripts/local-premount ... done.␍␊
>
> [17:21:07:462] Begin: Will now check root file system ... fsck from 
> util-linux 2.29.2␍␊
>
> [17:21:07:566] [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 
> /dev/mmcblk0p1 ␍␊
>
> [17:21:07:589] rootfs: recovering journal␍␊
>
> [17:21:07:909] rootfs: clean, 59570/217728 files, 479942/869376 blocks␍␊
>
> [17:21:07:927] done.␍␊
>
> [17:21:07:955] [ 118.559094] EXT4-fs (mmcblk0p1): mounted filesystem with 
> ordered data mode. Opts: (null)␍␊
>

I'm still unsure whats causing the problems. 

Am Montag, 16. Oktober 2017 14:23:46 UTC+2 schrieb Alexander Rössler:
>
> I figured out that is caused by the RT_PREEMPT kernel. However, I still 
> have no clue why this happens.
>
> Am Mittwoch, 13. September 2017 11:52:21 UTC+2 schrieb Alexander Rössler:
>>
>> After disabling the video, audio and wireless overlays in my uEnv.txt the 
>> boot starts to get extremely slow.
>>
>> The serial console output looks as follows:
>>
>> [11:41:14:515] ␍␊
>>
>> [11:41:14:519] U-Boot SPL 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:
>> 08)␍␊
>>
>> [11:41:14:576] Trying to boot from MMC2␍␊
>>
>> [11:41:14:678] ␍␊
>>
>> [11:41:14:681] ␍␊
>>
>> [11:41:14:681] U-Boot 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:08 -
>> 0500), Build: jenkins-github_Bootloader-Builder-591␍␊
>>
>> [11:41:14:690] ␍␊
>>
>> [11:41:14:690] CPU  : AM335X-GP rev 2.1␍␊
>>
>> [11:41:14:692] I2C:   ready␍␊
>>
>> [11:41:14:744] DRAM:  512 MiB␍␊
>>
>> [11:41:14:793] No match for driver 'omap_hsmmc'␍␊
>>
>> [11:41:14:798] No match for driver 'omap_hsmmc'␍␊
>>
>> [11:41:14:801] Some drivers were not found␍␊
>>
>> [11:41:14:803] Reset Source: Power-on reset has occurred.␍␊
>>
>> [11:41:14:808] MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1␍␊
>>
>> [11:41:14:812] Using default environment␍␊
>>
>> [11:41:14:812] ␍␊
>>
>> [11:41:14:874] Board: BeagleBone Black␍␊
>>
>> [11:41:14:878]  not set. Validating first E-fuse MAC␍␊
>>
>> [11:41:14:934] BeagleBone Black:␍␊
>>
>> [11:41:14:938] BeagleBone: cape eeprom: i2c_probe: 0x54:␍␊
>>
>> [11:41:14:943] BeagleBone: cape eeprom: i2c_probe: 0x55:␍␊
>>
>> [11:41:14:947] BeagleBone: cape eeprom: i2c_probe: 0x56:␍␊
>>
>> [11:41:14:952] BeagleBone: cape eeprom: i2c_probe: 0x57:␍␊
>>
>> [11:41:14:955] Net:   eth0: MII MODE␍␊
>>
>> [11:41:14:961] cpsw␍␊
>>
>> [11:41:14:964] Press SPACE to abort autoboot in 2 seconds␍␊
>>
>> [11:41:16:964] board_name=[A335BNLT] ...␍␊
>>
>> [11:41:16:970] board_rev=[00C0] ...␍␊
>>
>> [11:41:17:309] switch to partitions #0, OK␍␊
>>
>> [11:41:17:309] mmc0 is current device␍␊
>>
>> [11:41:17:385] SD/MMC found on device 0␍␊
>>
>> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>>
>> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>>
>> [11:41:17:454] switch to partitions #0, OK␍␊
>>
>> [11:41:17:457] mmc0 is current device␍␊
>>
>> [11:41:17:548] Scanning mmc 0:1...␍␊
>>
>> [11:41:17:960] gpio: pin 56 (gpio 56) value is 0␍␊
>>
>> [11:41:17:965] gpio: pin 55 (gpio 55) value is 0␍␊
>>
>> [11:41:17:966] gpio: pin 54 (gpio 54) value is 0␍␊
>>
>> [11:41:17:971] gpio: pin 53 (gpio 53) value is 1␍␊
>>
>> [11:41:18:042] switch to partitions #0, OK␍␊
>>
>> [11:41:18:046] mmc0 is current device␍␊
>>
>> [11:41:18:115] 

Re: [beagleboard] Network does not reconnect after temporarily removing Ethernet cable?

[Tom Hammond]

Hi Robert,

Thanks for the tip!  I'll check the OS version when I return home from work.

Tom


On Mon, Oct 16, 2017 at 10:16 AM, Robert Nelson 
wrote:

> On Mon, Oct 16, 2017 at 9:12 AM, Tom Hammond  wrote:
> >
> > Hello everyone,
> >
> >
> > I am using a Beagle Bone Black with a RGB123 cape to drive pixels. With
> the
> > BBB running Falcon Player (latest version, 1.9.xxx), if I unplug the
> network
> > cable and reconnect it, the BBB becomes unresponsive to a ping (it
> doesn't
> > recover from the temporary disconnect). I have to hard reset the BBB to
> get
> > it communicating again.
> >
> >
> > On my RPi running an older version of Falcon Player (v1.8.xxx), I can
> unplug
> > and replug the network cable and it recovers just fine.
> >
> >
> > Any idea why the BBB is temperamental with the network connection? The IP
> > address is statically assigned on the BBB. Any idea to help it auto
> recover
> > from a temporary network disconnect?
>
> Well it was an issue in the past with 3.8.13/wheezy...
>
> 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/CAFNahc%2BO2hgvM_CxpQFkP9XxLjhWwZW-k%3DfT3aH13Uy%3Dhm3f1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Network does not reconnect after temporarily removing Ethernet cable?

[Robert Nelson]

On Mon, Oct 16, 2017 at 9:12 AM, Tom Hammond  wrote:
>
> Hello everyone,
>
>
> I am using a Beagle Bone Black with a RGB123 cape to drive pixels. With the
> BBB running Falcon Player (latest version, 1.9.xxx), if I unplug the network
> cable and reconnect it, the BBB becomes unresponsive to a ping (it doesn't
> recover from the temporary disconnect). I have to hard reset the BBB to get
> it communicating again.
>
>
> On my RPi running an older version of Falcon Player (v1.8.xxx), I can unplug
> and replug the network cable and it recovers just fine.
>
>
> Any idea why the BBB is temperamental with the network connection? The IP
> address is statically assigned on the BBB. Any idea to help it auto recover
> from a temporary network disconnect?

Well it was an issue in the past with 3.8.13/wheezy...

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/CAOCHtYhQw0wMyqywkg-C7S2rDpCOdDL05-L0g%3D9gxoYH%3D6vTMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Network does not reconnect after temporarily removing Ethernet cable?

[Tom Hammond]

Hello everyone,


I am using a Beagle Bone Black with a RGB123 cape to drive pixels. With the 
BBB running Falcon Player (latest version, 1.9.xxx), if I unplug the 
network cable and reconnect it, the BBB becomes unresponsive to a ping (it 
doesn't recover from the temporary disconnect). I have to hard reset the 
BBB to get it communicating again.


On my RPi running an older version of Falcon Player (v1.8.xxx), I can 
unplug and replug the network cable and it recovers just fine.


Any idea why the BBB is temperamental with the network connection? The IP 
address is statically assigned on the BBB. Any idea to help it auto recover 
from a temporary network disconnect?


Thanks!
Tom

-- 
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/eded4a56-d389-4ff3-983f-9af5a301d4e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Boot is extremely slow/hangs

[Alexander Rössler]

I figured out that is caused by the RT_PREEMPT kernel. However, I still 
have no clue why this happens.

Am Mittwoch, 13. September 2017 11:52:21 UTC+2 schrieb Alexander Rössler:
>
> After disabling the video, audio and wireless overlays in my uEnv.txt the 
> boot starts to get extremely slow.
>
> The serial console output looks as follows:
>
> [11:41:14:515] ␍␊
>
> [11:41:14:519] U-Boot SPL 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:
> 08)␍␊
>
> [11:41:14:576] Trying to boot from MMC2␍␊
>
> [11:41:14:678] ␍␊
>
> [11:41:14:681] ␍␊
>
> [11:41:14:681] U-Boot 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:08 -
> 0500), Build: jenkins-github_Bootloader-Builder-591␍␊
>
> [11:41:14:690] ␍␊
>
> [11:41:14:690] CPU  : AM335X-GP rev 2.1␍␊
>
> [11:41:14:692] I2C:   ready␍␊
>
> [11:41:14:744] DRAM:  512 MiB␍␊
>
> [11:41:14:793] No match for driver 'omap_hsmmc'␍␊
>
> [11:41:14:798] No match for driver 'omap_hsmmc'␍␊
>
> [11:41:14:801] Some drivers were not found␍␊
>
> [11:41:14:803] Reset Source: Power-on reset has occurred.␍␊
>
> [11:41:14:808] MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1␍␊
>
> [11:41:14:812] Using default environment␍␊
>
> [11:41:14:812] ␍␊
>
> [11:41:14:874] Board: BeagleBone Black␍␊
>
> [11:41:14:878]  not set. Validating first E-fuse MAC␍␊
>
> [11:41:14:934] BeagleBone Black:␍␊
>
> [11:41:14:938] BeagleBone: cape eeprom: i2c_probe: 0x54:␍␊
>
> [11:41:14:943] BeagleBone: cape eeprom: i2c_probe: 0x55:␍␊
>
> [11:41:14:947] BeagleBone: cape eeprom: i2c_probe: 0x56:␍␊
>
> [11:41:14:952] BeagleBone: cape eeprom: i2c_probe: 0x57:␍␊
>
> [11:41:14:955] Net:   eth0: MII MODE␍␊
>
> [11:41:14:961] cpsw␍␊
>
> [11:41:14:964] Press SPACE to abort autoboot in 2 seconds␍␊
>
> [11:41:16:964] board_name=[A335BNLT] ...␍␊
>
> [11:41:16:970] board_rev=[00C0] ...␍␊
>
> [11:41:17:309] switch to partitions #0, OK␍␊
>
> [11:41:17:309] mmc0 is current device␍␊
>
> [11:41:17:385] SD/MMC found on device 0␍␊
>
> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>
> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>
> [11:41:17:454] switch to partitions #0, OK␍␊
>
> [11:41:17:457] mmc0 is current device␍␊
>
> [11:41:17:548] Scanning mmc 0:1...␍␊
>
> [11:41:17:960] gpio: pin 56 (gpio 56) value is 0␍␊
>
> [11:41:17:965] gpio: pin 55 (gpio 55) value is 0␍␊
>
> [11:41:17:966] gpio: pin 54 (gpio 54) value is 0␍␊
>
> [11:41:17:971] gpio: pin 53 (gpio 53) value is 1␍␊
>
> [11:41:18:042] switch to partitions #0, OK␍␊
>
> [11:41:18:046] mmc0 is current device␍␊
>
> [11:41:18:115] gpio: pin 54 (gpio 54) value is 1␍␊
>
> [11:41:18:333] Checking for: /uEnv.txt ...␍␊
>
> [11:41:18:369] Checking for: /boot.scr ...␍␊
>
> [11:41:18:404] Checking for: /boot/boot.scr ...␍␊
>
> [11:41:18:464] Checking for: /boot/uEnv.txt ...␍␊
>
> [11:41:18:520] gpio: pin 55 (gpio 55) value is 1␍␊
>
> [11:41:18:576] 2141 bytes read in 49 ms (42 KiB/s)␍␊
>
> [11:41:18:581] Loaded environment from /boot/uEnv.txt␍␊
>
> [11:41:18:586] Checking if uname_r is set in /boot/uEnv.txt...␍␊
>
> [11:41:18:590] gpio: pin 56 (gpio 56) value is 1␍␊
>
> [11:41:18:594] Running uname_boot ...␍␊
>
> [11:41:18:653] loading /boot/vmlinuz-4.4.87-ti-rt-r121 ...␍␊
>
> [11:41:19:263] 8725520 bytes read in 602 ms (13.8 MiB/s)␍␊
>
> [11:41:19:269] uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] 
> ...␍␊
>
> [11:41:19:360] uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb 
> ...␍␊
>
> [11:41:19:451] loading /boot/dtbs/4.4.87-ti-rt-r121/am335x-boneblack-uboot
> .dtb ...␍␊
>
> [11:41:19:547] 53128 bytes read in 86 ms (602.5 KiB/s)␍␊
>
> [11:41:19:553] uboot_overlays: [fdt_buffer=0x6] ...␍␊
>
> [11:41:19:800] uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo 
> ...␍␊
>
> [11:41:20:048] 378 bytes read in 238 ms (1000 Bytes/s)␍␊
>
> [11:41:20:289] uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-
> 00A0.dtbo ...␍␊
>
> [11:41:20:525] 1105 bytes read in 226 ms (3.9 KiB/s)␍␊
>
> [11:41:20:536] uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-
> TDA998x-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_video
> =1]...␍␊
>
> [11:41:20:611] uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo 
> ...␍␊
>
> [11:41:20:679] 695 bytes read in 58 ms (10.7 KiB/s)␍␊
>
> [11:41:20:962] uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-
> 00A0.dtbo ...␍␊
>
> [11:41:21:241] 853 bytes read in 269 ms (2.9 KiB/s)␍␊
>
> [11:41:21:294] uboot_overlays: loading /lib/firmware/univ-bbb-Exx-
> 00A0.dtbo ...␍␊
>
> [11:41:21:347] 92817 bytes read in 43 ms (2.1 MiB/s)␍␊
>
> [11:41:22:542] loading /boot/initrd.img-4.4.87-ti-rt-r121 ...␍␊
>
> [11:41:22:977] 5921265 bytes read in 426 ms (13.3 MiB/s)␍␊
>
> [11:41:22:985] debug: [console=ttyO0,115200n8 bone_capemgr.
> uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait 
> coherent_pool=1M net.ifnames=0 quiet init=/lib/systemd/systemd 
> cape_universal=enable] ...␍␊
>
> [11:41:23:004] debug: [bootz 0x8200 0x8808:5a59f1 8800] ...␍␊
>
> [11:41:23:011] ## Flattened Device Tree blob at 

[beagleboard] is it possible to managing pru chip using bonescript?

[구종회]

I`m newbie to BBB. I want to know managing pru chip using bonescript. I 
just know to way managing pru chip using C/C++.
is there any way not use C/C++?  or using addon is solution?



I`m not used to English. if u talk to me about wrong sentence or wrong 
expression, thank u for that.

-- 
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/f1edef5e-8a15-4737-9fe3-056cba438dec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB Rev C in I2C Multi Master Mode

[sajeevan k]

Hi all,

Sorry for conveying my confusion.
No need of using Multi Master mode or slave mode for communicating with a 
Microcontroller through I2C.
BBB may be put in Master mode only.

Thanks & Regards,
Sajeevan.K


On Saturday, October 14, 2017 at 4:48:02 PM UTC+5:30, sajeevan k wrote:
>
> Hi all,
>
>
> I have already done interfacing BBB with slave devices such as RTC with a 
> finite slave address. Now I am in need of communicating BBB
> with a Micro Controller through I2C interface. The way in the RTC is 
> interfaced is not working in this case. In this case, BBB need to be either 
> in Multi Master mode or slave mode.
>
> Is it possible to make BBB working in I2C Multi Master mode or slave mode. 
> Is Mutli Master/Slave mode supported by kernel?  Drivers available?
> Is there any sample .dts file for configuring i2c in Multi Master/Slave 
> Mode.
>
>
> Thanks & Regards,
> Sajeevan.K
>

-- 
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/595efc55-0080-4124-89a0-4fc866079418%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.