Re: [beagleboard] How to restore BeagleBoard-X15 to its default image?

2019-05-17 Thread Robert Nelson 
On Fri, May 17, 2019 at 7:36 AM Felicity Lv  wrote:
>
> Hello,
>
> I recently flashed a new eMMC image to the BeagleBoard-x15, later found out 
> that it's not an image I want. How do I restore the BeagleBoard-X15 to its 
> original eMMC image?


>From my old notes, this might be the default image:

https://rcn-ee.net/rootfs/bb.org/testing/2017-07-02/stretch-lxqt/

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/CAOCHtYg3F9YEuP%2Bn14pxZpjqaXr7-0TcCy8%3DAURhOsZtHuGJ8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to restore BeagleBoard-X15 to its default image?

2019-05-17 Thread Charles Steinkuehler 
On 5/17/2019 6:14 AM, Felicity Lv wrote:
> Hello,
> 
> I recently flashed a new eMMC image to the BeagleBoard-x15, later found out 
> that it's not an image I want. How do I restore the BeagleBoard-X15 to its 
> original eMMC image?

You can get the official images here:

http://beagleboard.org/latest-images

Note if you want to flash your eMMC (vs. just run off the uSD card)
you will need to edit uEnv.txt as described in the text.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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/33ba1c6b-df1e-e25d-b3e7-0cda5d581240%40steinkuehler.net.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to restore BeagleBoard-X15 to its default image?

2019-05-17 Thread Andy Laberge 
With out a copy of your original eMMC image, I believe you're out of luck.
If you have it you're good to go.

Because of the limitation size of eMMC (4Gb) on the BBX15, I have learned
to develop on the SD card.
I have 3 different SD images at the moment. I have been finding lib's  that
coexist on my Desktop (x86) will not
on my BBX15 (Arm). May be because of DSP, PRU support on the BBX15.

Andy






On Fri, May 17, 2019 at 5:36 AM Felicity Lv  wrote:

> Hello,
>
> I recently flashed a new eMMC image to the BeagleBoard-x15, later found
> out that it's not an image I want. How do I restore the BeagleBoard-X15 to
> its original eMMC image?
>
> Kind regard,
> Felicity
>
> --
> 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/177f592c-3431-4e5c-8826-622f7d6bb302%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/CAEqAPB80eDcK3oBkRoNrEuG5qkpUdYGM7B6VJXBb7Mk_zezCjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: remoteproc not detecting PRUs under 4.14, am I missing something?

2019-05-17 Thread Hugh Frater 
Our application is node.js for the easy stuff with all the heavy lifting 
done in the PRU... if you want to code in C, it's worth looking at the MRAA 
libraries from Intel https://github.com/intel-iot-devkit/mraa

On Friday, 17 May 2019 14:20:34 UTC+1, Walter Cromer wrote:
>
> I plan to write the code in C since I'm most familiar with it (although 
> very rusty, but it's coming back) and I have considered learning Python and 
> using it.
>
> By the way, thanks to all for your patience with me on this!  It has been 
> a long time since I worked in this space and a lot has changed and improved!
>
> On Friday, May 17, 2019 at 9:17:24 AM UTC-4, Hugh Frater wrote:
>>
>> If you can live with using the universal-cape and just configuring the 
>> pins once booted using the config-pin utility, that's a good way to go. 
>> What programming language are you wanting to use to write your temperature 
>> sensor software? If you are doing it from the PRU then you can just code up 
>> your own i2c read function and access the registers directly though the 
>> memory map, just like any standard MCU. 
>>
>> On Thursday, 16 May 2019 20:34:58 UTC+1, Walter Cromer wrote:
>>>
>>> Hugh - I'll dig around in the UBoot section.  Thanks for suggesting 
>>> that.  I'm such a newbie on here!
>>>
>>> As for how I compiled the custom device tree overlay, I followed the 
>>> instructions posted at this location and it worked fine - no errors after I 
>>> corrected the typos, etc. that were posted in the comments.
>>>
>>>
>>> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>>>
>>> I'd really like to get this temperature sensor working but all the 
>>> instructions are pre-Uboot.   I can make a lot of progress with my 
>>> prototype once I get this working but liquid temperature is a critical 
>>> input so without it I can't move forward!
>>>
>>>
>>>
>>> On Thursday, May 16, 2019 at 5:53:38 AM UTC-4, Hugh Frater wrote:

 Hi Walter, I'm afraid I can't help with your custom device overlay 
 issue, it us really a topic for a new thread in the uBoot section I would 
 have thought?

 I would be interested in hearing how you compiled a custom device tree 
 overlay though. We have our BBB on a custom card that uses a bunch of 
 gpio, 
 an eqep module, a bunch of uarts and some pru_ecap pwm - it's a lot of 
 work 
 for config-pin to setup at boot time and I'd like to trim this 13 seconds 
 of work out of my bootup if possible. Perhaps you could make a post in the 
 uBoot section?

 Hugh

 On Thursday, 16 May 2019 01:27:36 UTC+1, Walter Cromer wrote:
>
> Hugh - I'm a real newbie.  I compiled a device tree overlay with not 
> errors and have a dtbo file now.  I just don't know how to get it into 
> the 
> boot process.  Where do I put it, do I need to change a file like env.txt 
> somewhere to get it to load and if so what syntax do i use?  Where did 
> you 
> find these instructions?  I'm so lost and need to keep moving forward.  
> it 
> was going so well...
>
> I'm on 4.4.14 
>
> On Thursday, May 9, 2019 at 7:31:27 AM UTC-4, Hugh Frater wrote:
>>
>> I have the same problem as this user: 
>> https://groups.google.com/forum/#!category-topic/beagleboard/pru/g2NcW2sUX-4
>>  
>> in that remoteproc only detects the wkup_m3 coprocessor (whatever that 
>> is) 
>> and doesn't seem to detect the PRUs on boot.
>>
>> This is a fresh install of Sretch IOT from beagleboard.org, with the 
>> kernel and cape-overlays updated through the tools/scripts...
>>
>> version.sh shows:
>>
>> git:/opt/scripts/:[c2a5ae96746d10d711c60bc84ba244f4cd7b75c3]
>> eeprom:[A335BNLT00C03816BBBK190D]
>> model:[TI_AM335x_BeagleBone_Black]
>> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
>> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
>> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>> kernel:[4.14.108-ti-r104]
>> nodejs:[v6.14.4]
>> uboot_overlay_options:[enable_uboot_overlays=1]
>> uboot_overlay_options:[disable_uboot_overlay_emmc=1]
>> uboot_overlay_options:[disable_uboot_overlay_video=1]
>> uboot_overlay_options:[disable_uboot_overlay_audio=1]
>> uboot_overlay_options:[disable_uboot_overlay_wireless=1]
>> uboot_overlay_options:[disable_uboot_overlay_adc=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 ]
>> pkg:[bb-cape-overlays]:[4.4.20190429.0-0rcnee0~stretch+20190429]
>> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
>> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
>> pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
>>

[beagleboard] Re: remoteproc not detecting PRUs under 4.14, am I missing something?

2019-05-17 Thread Hugh Frater 
If you can live with using the universal-cape and just configuring the pins 
once booted using the config-pin utility, that's a good way to go. What 
programming language are you wanting to use to write your temperature 
sensor software? If you are doing it from the PRU then you can just code up 
your own i2c read function and access the registers directly though the 
memory map, just like any standard MCU. 

On Thursday, 16 May 2019 20:34:58 UTC+1, Walter Cromer wrote:
>
> Hugh - I'll dig around in the UBoot section.  Thanks for suggesting that.  
> I'm such a newbie on here!
>
> As for how I compiled the custom device tree overlay, I followed the 
> instructions posted at this location and it worked fine - no errors after I 
> corrected the typos, etc. that were posted in the comments.
>
>
> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>
> I'd really like to get this temperature sensor working but all the 
> instructions are pre-Uboot.   I can make a lot of progress with my 
> prototype once I get this working but liquid temperature is a critical 
> input so without it I can't move forward!
>
>
>
> On Thursday, May 16, 2019 at 5:53:38 AM UTC-4, Hugh Frater wrote:
>>
>> Hi Walter, I'm afraid I can't help with your custom device overlay issue, 
>> it us really a topic for a new thread in the uBoot section I would have 
>> thought?
>>
>> I would be interested in hearing how you compiled a custom device tree 
>> overlay though. We have our BBB on a custom card that uses a bunch of gpio, 
>> an eqep module, a bunch of uarts and some pru_ecap pwm - it's a lot of work 
>> for config-pin to setup at boot time and I'd like to trim this 13 seconds 
>> of work out of my bootup if possible. Perhaps you could make a post in the 
>> uBoot section?
>>
>> Hugh
>>
>> On Thursday, 16 May 2019 01:27:36 UTC+1, Walter Cromer wrote:
>>>
>>> Hugh - I'm a real newbie.  I compiled a device tree overlay with not 
>>> errors and have a dtbo file now.  I just don't know how to get it into the 
>>> boot process.  Where do I put it, do I need to change a file like env.txt 
>>> somewhere to get it to load and if so what syntax do i use?  Where did you 
>>> find these instructions?  I'm so lost and need to keep moving forward.  it 
>>> was going so well...
>>>
>>> I'm on 4.4.14 
>>>
>>> On Thursday, May 9, 2019 at 7:31:27 AM UTC-4, Hugh Frater wrote:

 I have the same problem as this user: 
 https://groups.google.com/forum/#!category-topic/beagleboard/pru/g2NcW2sUX-4
  
 in that remoteproc only detects the wkup_m3 coprocessor (whatever that is) 
 and doesn't seem to detect the PRUs on boot.

 This is a fresh install of Sretch IOT from beagleboard.org, with the 
 kernel and cape-overlays updated through the tools/scripts...

 version.sh shows:

 git:/opt/scripts/:[c2a5ae96746d10d711c60bc84ba244f4cd7b75c3]
 eeprom:[A335BNLT00C03816BBBK190D]
 model:[TI_AM335x_BeagleBone_Black]
 dogtag:[BeagleBoard.org Debian Image 2018-10-07]
 bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
 2018.09-2-g0b54a51eee]:[location: dd MBR]
 kernel:[4.14.108-ti-r104]
 nodejs:[v6.14.4]
 uboot_overlay_options:[enable_uboot_overlays=1]
 uboot_overlay_options:[disable_uboot_overlay_emmc=1]
 uboot_overlay_options:[disable_uboot_overlay_video=1]
 uboot_overlay_options:[disable_uboot_overlay_audio=1]
 uboot_overlay_options:[disable_uboot_overlay_wireless=1]
 uboot_overlay_options:[disable_uboot_overlay_adc=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 ]
 pkg:[bb-cape-overlays]:[4.4.20190429.0-0rcnee0~stretch+20190429]
 pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
 pkg:[kmod]:[23-2rcnee1~stretch+20171005]
 pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
 pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
 groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
 plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
 admin spi tisdk weston-launch xenomai]
 cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
 net.ifnames=0 quiet]
 dmesg | grep remote
 [1.302485] remoteproc remoteproc0: wkup_m3 is available
 [1.389525] remoteproc remoteproc0: powering up wkup_m3
 [1.389661] remoteproc remoteproc0: Booting fw image 
 am335x-pm-firmware.elf, size 217168
 [1.393097] remoteproc remoteproc0: remote processor wkup_m3 is now 
 up
 dmesg | grep pru
 dmesg | grep pinctrl-single
 [0.971911] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800

[beagleboard] Re: remoteproc not detecting PRUs under 4.14, am I missing something?

2019-05-17 Thread Walter Cromer 
I plan to write the code in C since I'm most familiar with it (although 
very rusty, but it's coming back) and I have considered learning Python and 
using it.

By the way, thanks to all for your patience with me on this!  It has been a 
long time since I worked in this space and a lot has changed and improved!

On Friday, May 17, 2019 at 9:17:24 AM UTC-4, Hugh Frater wrote:
>
> If you can live with using the universal-cape and just configuring the 
> pins once booted using the config-pin utility, that's a good way to go. 
> What programming language are you wanting to use to write your temperature 
> sensor software? If you are doing it from the PRU then you can just code up 
> your own i2c read function and access the registers directly though the 
> memory map, just like any standard MCU. 
>
> On Thursday, 16 May 2019 20:34:58 UTC+1, Walter Cromer wrote:
>>
>> Hugh - I'll dig around in the UBoot section.  Thanks for suggesting 
>> that.  I'm such a newbie on here!
>>
>> As for how I compiled the custom device tree overlay, I followed the 
>> instructions posted at this location and it worked fine - no errors after I 
>> corrected the typos, etc. that were posted in the comments.
>>
>>
>> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>>
>> I'd really like to get this temperature sensor working but all the 
>> instructions are pre-Uboot.   I can make a lot of progress with my 
>> prototype once I get this working but liquid temperature is a critical 
>> input so without it I can't move forward!
>>
>>
>>
>> On Thursday, May 16, 2019 at 5:53:38 AM UTC-4, Hugh Frater wrote:
>>>
>>> Hi Walter, I'm afraid I can't help with your custom device overlay 
>>> issue, it us really a topic for a new thread in the uBoot section I would 
>>> have thought?
>>>
>>> I would be interested in hearing how you compiled a custom device tree 
>>> overlay though. We have our BBB on a custom card that uses a bunch of gpio, 
>>> an eqep module, a bunch of uarts and some pru_ecap pwm - it's a lot of work 
>>> for config-pin to setup at boot time and I'd like to trim this 13 seconds 
>>> of work out of my bootup if possible. Perhaps you could make a post in the 
>>> uBoot section?
>>>
>>> Hugh
>>>
>>> On Thursday, 16 May 2019 01:27:36 UTC+1, Walter Cromer wrote:

 Hugh - I'm a real newbie.  I compiled a device tree overlay with not 
 errors and have a dtbo file now.  I just don't know how to get it into the 
 boot process.  Where do I put it, do I need to change a file like env.txt 
 somewhere to get it to load and if so what syntax do i use?  Where did you 
 find these instructions?  I'm so lost and need to keep moving forward.  it 
 was going so well...

 I'm on 4.4.14 

 On Thursday, May 9, 2019 at 7:31:27 AM UTC-4, Hugh Frater wrote:
>
> I have the same problem as this user: 
> https://groups.google.com/forum/#!category-topic/beagleboard/pru/g2NcW2sUX-4
>  
> in that remoteproc only detects the wkup_m3 coprocessor (whatever that 
> is) 
> and doesn't seem to detect the PRUs on boot.
>
> This is a fresh install of Sretch IOT from beagleboard.org, with the 
> kernel and cape-overlays updated through the tools/scripts...
>
> version.sh shows:
>
> git:/opt/scripts/:[c2a5ae96746d10d711c60bc84ba244f4cd7b75c3]
> eeprom:[A335BNLT00C03816BBBK190D]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> kernel:[4.14.108-ti-r104]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[disable_uboot_overlay_emmc=1]
> uboot_overlay_options:[disable_uboot_overlay_video=1]
> uboot_overlay_options:[disable_uboot_overlay_audio=1]
> uboot_overlay_options:[disable_uboot_overlay_wireless=1]
> uboot_overlay_options:[disable_uboot_overlay_adc=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 ]
> pkg:[bb-cape-overlays]:[4.4.20190429.0-0rcnee0~stretch+20190429]
> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm 
> eqep 
> admin spi tisdk weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
>

[beagleboard] Re: remoteproc not detecting PRUs under 4.14, am I missing something?

2019-05-17 Thread Hugh Frater 
An update - tried switching my 8.9/4.4.54-ti-r93 setup (that we have 
working with kernel overlays) over to uBoot overlays - all good...

[   37.211677]  remoteproc1: powering up 4a338000.pru1
[   37.212435]  remoteproc1: Booting fw image am335x-pru1-fw, size 129436
[   37.240836] ti-pruss 4a30.pruss: configured system_events = 
0x000c intr_channels = 0x000a host_intr = 0x000a
[   37.246313]  remoteproc1: remote processor 4a338000.pru1 is now up
[   37.261296] virtio_rpmsg_bus virtio0: rpmsg host is online
[   37.261377] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr 
0x1f
[   38.227474] rpmsg_pru rpmsg0: new rpmsg_pru device: /dev/rpmsg_pru31

No idea why the PRUSS driver doesn't power up the PRU under 
Stretch/4.14.whatver

Now to see if I can get overlayroot working on 8.9/4.4 and sort out the 
read-only filesystem




On Thursday, 9 May 2019 12:31:27 UTC+1, Hugh Frater wrote:
>
> I have the same problem as this user: 
> https://groups.google.com/forum/#!category-topic/beagleboard/pru/g2NcW2sUX-4 
> in that remoteproc only detects the wkup_m3 coprocessor (whatever that is) 
> and doesn't seem to detect the PRUs on boot.
>
> This is a fresh install of Sretch IOT from beagleboard.org, with the 
> kernel and cape-overlays updated through the tools/scripts...
>
> version.sh shows:
>
> git:/opt/scripts/:[c2a5ae96746d10d711c60bc84ba244f4cd7b75c3]
> eeprom:[A335BNLT00C03816BBBK190D]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> kernel:[4.14.108-ti-r104]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[disable_uboot_overlay_emmc=1]
> uboot_overlay_options:[disable_uboot_overlay_video=1]
> uboot_overlay_options:[disable_uboot_overlay_audio=1]
> uboot_overlay_options:[disable_uboot_overlay_wireless=1]
> uboot_overlay_options:[disable_uboot_overlay_adc=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 
> ]
> pkg:[bb-cape-overlays]:[4.4.20190429.0-0rcnee0~stretch+20190429]
> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
> admin spi tisdk weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0 quiet]
> dmesg | grep remote
> [1.302485] remoteproc remoteproc0: wkup_m3 is available
> [1.389525] remoteproc remoteproc0: powering up wkup_m3
> [1.389661] remoteproc remoteproc0: Booting fw image 
> am335x-pm-firmware.elf, size 217168
> [1.393097] remoteproc remoteproc0: remote processor wkup_m3 is now up
> dmesg | grep pru
> dmesg | grep pinctrl-single
> [0.971911] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 
> size 568
> dmesg | grep gpio-of-helper
> [0.984114] gpio-of-helper ocp:cape-universal: ready
> lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> END
>
> What am I doing wrong here? Surely PRU support is one of those things that 
> should be working out of the box with the correct u-boot overlay applied?
>
>
>
>
>
>

-- 
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/8dc31247-c629-4782-9b2a-f5802e696634%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to Write Device Trees?

2019-05-17 Thread Walter Cromer 
I would really appreciate this information too.  I see examples of device 
trees online and in books but nothing so far explains what any of the 
syntax really means and without understanding that I'm just copying 
something without learning anything.  I could really use some help here, 
please!

On Thursday, May 16, 2019 at 9:52:16 PM UTC-4, sacan...@gmail.com wrote:
>
>
> Could anyone point me to some resources that explain how to write device 
> tree files for the BBB?
>
> To clarify, the OS running on my BeagleBone is a custom Linux distro (not 
> one of the more common Debian or Angstrom ones). The current configuration 
> only enables one of the SPI ports and none of the PWM pins. I want to 
> modify the .dts file used in building the OS so that it correctly enables 
> and muxes the SPI and PWM pins that I select. I also want to avoid using 
> device tree overlays, so I'm dealing with just the device trees. Any help 
> 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/08afc945-a72c-4c0b-b867-e26644f5f85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to restore BeagleBoard-X15 to its default image?

2019-05-17 Thread Felicity Lv 
Hello,

I recently flashed a new eMMC image to the BeagleBoard-x15, later found out 
that it's not an image I want. How do I restore the BeagleBoard-X15 to its 
original eMMC image?

Kind regard,
Felicity

-- 
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/177f592c-3431-4e5c-8826-622f7d6bb302%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone rc_startup_routine[1278]: timeout reached while waiting for pwm driver

2019-05-17 Thread rgovostes 
I've filed this on GitHub 
at https://github.com/StrawsonDesign/librobotcontrol/issues/162. If anyone 
has found a conclusive explanation and solution for the failure, please 
post it there. Thanks!

On Thursday, May 9, 2019 at 4:29:34 AM UTC-4, n ithinu wrote:
>
> I do not have the link anymore. Anyway, it said to get the last version of 
> the system on an sd card, but it is not enough as the old bootloader from 
> the eMMc would still be used. So it said to desactivate the bootloader
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k
>
> Possibly it loses the contents of all partitions on the eMMC, I do not 
> know.
>
> If you need the EEPROM and do not want to use the sd card, you should 
> instead update the eMMC. I guess you will find links for that.
>
> On Wednesday, May 8, 2019 at 3:27:00 AM UTC+2, layt...@gmail.com wrote:
>>
>> Thank you! If possible, could you please give me more detailed 
>> instruction on how to solve this? Maybe some links would be very helpful!
>>
>> On Monday, May 6, 2019 at 5:09:27 AM UTC-7, ithinu wrote:
>>>
>>> It was something like new OS on an sd card, but something outdated in 
>>> the booting sequence on the EEPROM and I needed to fill the latter with 
>>> zeros... something strange like that if I remember well.
>>>
>>> On Monday, May 6, 2019 at 1:58:10 PM UTC+2, layt...@gmail.com wrote:

 Hello, I have the same problem here so I cannot run on boot either. 
 Have you solved this problem? 
 I'm looking forward to hearing from you, thank you!

 On Monday, January 14, 2019 at 5:21:43 AM UTC-8, ith...@gmail.com 
 wrote:
>
> I use 
> http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
>  
> from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
> flashed it into the built-in eMMc as the page told that it is better so.
>
> Then I configured librobotcontrol to use rc_balance as told here 
> http://strawsondesign.com/#!edumip-software, which gave an error:
>
> $ systemctl status robotcontrol.service
> ● robotcontrol.service - robotcontrol
>Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
> vendor preset: enabled)
>Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 
> UTC; 13s ago
>   Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
> status=255)
>
> Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached 
> while waiting for pwm driver
> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
> process exited, code=exited status=255
> Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit 
> entered failed state.
> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed 
> with result 'exit-code'.
>
> $ uname -a
> Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 
> 2018 armv7l GNU/Linux
>
> I guess the hardware is ok, as I previously used some old image from 
> https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.
>
>

-- 
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/5692e812-5a97-4b56-ad8e-87fd020713fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.