Re: [beagleboard] Using GPMC to interface with FPGA (SRAM interface)

['Mark Lazarewicz' via BeagleBoard]

GPMC to FPGA  has been discussed many times in here try Google and a 
comprehensive understanding of muxing the pins and their possible functions as 
described in TRM 

Sent from Yahoo Mail on Android 
 
  On Tue, May 31, 2016 at 9:50 PM, 
cmajor.merch...@gmail.com wrote:   I wan't to use 
the GPMC interface on the BeagleBone back to interface with a FPGA exposed as 
SRAM. The FPGA is being used as an audio codec and I wan't to use DMA transfers 
to take data from the FPGA and put it into main memory. I'm not necessarily 
asking about the DMA stuff (though I wouldn't mind help). I'm asking how to I 
configure the hardware to do this? I've heard about device tree overlays but 
I'm not exactly sure how to use them. I also have read that using GPMC renders 
the flash unusable, however, could I configure uboot to boot from the sd card 
easily? BTW I'm implementing the software as a out of tree module.

-- 
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/0726d8da-50f9-41e5-95c4-bad1643ae3a2%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/1451534006.2679536.1464752504201.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Reboot hangs with custom Image 4.4

[Virendra]

Hi,

The reboot command hangs in custom Image 4.4 after displaying 
"systemd-shutdown[1]: Rebooting." whereas using 4.1 custom Image using 
Robert Nelson the system reboots successfully. I am using Debian 8.4. Could 
you let me know what could be the issue. 

Following command are tried for rebooting:( both the below 2 commands fails 
in custom image 4.4)
sudo reboot

systemctl reboot --force



Log Display:
[   45.605663] systemd-shutdown[1]: Rebooting.   *<--- Hangs here in 4.4 
Image* 
[   45.611504] musb-hdrc musb-hdrc.1.auto: remove, state 
1
[   45.616909] usb usb1: USB disconnect, device number 
1  
[   45.622008] usb 1-1: USB disconnect, device number 
2   
[   45.632657] musb-hdrc musb-hdrc.1.auto: USB bus 1 
deregistered 
[   45.644024] reboot: Restarting system  *<-- In 4.1 Image the log is 
displayed till here and reboots successfully*
---


Thanks,
Veera

-- 
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/68fbf8b7-a705-4267-a2e6-5693043b8cdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using GPMC to interface with FPGA (SRAM interface)

[cmajor . merchant]

I wan't to use the GPMC interface on the BeagleBone back to interface with 
a FPGA exposed as SRAM. The FPGA is being used as an audio codec and I 
wan't to use DMA transfers to take data from the FPGA and put it into main 
memory. I'm not necessarily asking about the DMA stuff (though I wouldn't 
mind help). I'm asking how to I configure the hardware to do this? I've 
heard about device tree overlays but I'm not exactly sure how to use them. 
I also have read that using GPMC renders the flash unusable, however, could 
I configure uboot to boot from the sd card easily? BTW I'm implementing the 
software as a out of tree module.

-- 
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/0726d8da-50f9-41e5-95c4-bad1643ae3a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Not getting output on the PWM

[ide . neil . s]

Hi Everyone,

I'm trying to get the PWM outputs up and rugging with this python script:

>import time

>import Adafruit_BBIO.PWM as PWM

>myPWM="P9_14"

>PWM.start(myPWM, 100, 1)
>#for i in range(0,5):
>#DC=input("What Duty Cycle Would You Like (0-100)? ")
>#PWM.set_duty_cycle(myPWM, DC)

>time.sleep(10.0)

>PWM.stop(myPWM)
>PWM.cleanup()

The script runs but I get no physical out output.  Any ideas whats going on?

-- 
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/ec83d12e-5cc8-4a97-9e1b-09a672b10f30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Error setting system time with real-time clock

[Kirk]

I have a DS3231 real-time clock connected to my Beagelbone Black.

I have these lines in /etc/rc.local to initialize the system time from the 
RTC:

echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
sleep 5
/sbin/hwclock -s -f /dev/rtc1
/sbin/hwclock -w


It almost always works correctly however:
Infrequently at boot up the hwclock commands fail and then the rest of 
rc.local doesn't run.
Here's the error output I captured from rc.local:

hwclock: Timed out waiting for time change.
hwclock: The Hardware Clock does not contain a valid time, so we cannot set 
the System Time from it.
Unable to set system clock.

Any idea on what could cause this error?

Thanks,
Kirk

-- 
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/7a54fcaa-2181-415e-8abd-9feb29dcc914%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Matt99eo]

Ok did that and still having there same error. Validated network connection 
and reran script. Below is the output of creating the image and then what I 
am getting when trying to use the image:

Creating uSD:
root@arm:/opt/scripts/tools/eMMC# 
./beaglebone-black-make-microSD-flasher-from-eMMC.sh 

Unmounting Partitions
-
 [3;J
-
Version: [1.20160322: upgrade backup u-boot: v2016.03-r6...]
-
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:801M  1 disk 
mmcblk0boot1 179:16   01M  1 disk 
mmcblk0  179:00  3.7G  0 disk 
└─mmcblk0p1  179:10  3.7G  0 part /
mmcblk1  179:24   0  3.7G  0 disk 
└─mmcblk1p1  179:25   0  3.7G  0 part 
-
df -h | grep rootfs:
-
update-initramfs: Generating /boot/initrd.img-4.1.21-bone-rt-r20
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 10.8226 s, 10.5 MB/s
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 5.8479 s, 19.4 MB/s
Erasing: /dev/mmcblk1 complete
-
Writing bootloader to [/dev/mmcblk1]
dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
-
0+1 records in
0+1 records out
65708 bytes (66 kB) copied, 0.0937003 s, 701 kB/s
-
dd if=/opt/backup/uboot/u-boot.img of=/dev/mmcblk1 count=2 seek=1 bs=384k
-
0+1 records in
0+1 records out
350020 bytes (350 kB) copied, 0.104779 s, 3.3 MB/s
-
Formatting: /dev/mmcblk1
sfdisk: [sfdisk from util-linux 2.25.2]
sfdisk: [sfdisk --force --Linux --in-order --unit M /dev/mmcblk1]
sfdisk: [1,,L,*]
sfdisk: Checking that no-one is using this disk right now ...
sfdisk: OK

Disk /dev/mmcblk1: 121472 cylinders, 4 heads, 16 sectors/track
sfdisk:  /dev/mmcblk1: unrecognized partition table type
Old situation:
sfdisk: No partitions found
New situation:
Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   EndMiB#blocks   Id  System
/dev/mmcblk1p1   * 1   3795   37953886080   83  Linux
/dev/mmcblk1p2 0  -  0  00  Empty
/dev/mmcblk1p3 0  -  0  00  Empty
/dev/mmcblk1p4 0  -  0  00  Empty
Successfully wrote the new partition table

Re-reading the partition table ...

sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use 
dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
mkfs.ext4 /dev/mmcblk1p1 -L BEAGLEBONE
-
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: done
Creating filesystem with 971520 4k blocks and 242880 inodes
Filesystem UUID: 11b1347f-86bb-46e0-8779-764f298bcd3e
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

-
Formatting: /dev/mmcblk1 complete
-
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1
rsync: / -> /tmp/rootfs/
rsync: note the % column is useless...
691.19M  99%4.05MB/s0:02:42 (xfr#25078, to-chk=0/31857)   
Copying: Kernel modules
rsync: /lib/modules/4.1.21-bone-rt-r20/ -> 
/tmp/rootfs/lib/modules/4.1.21-bone-rt-r20/
rsync: note the % column is useless...
 55.61M  99%4.04MB/s0:00:13 (xfr#2266, to-chk=0/2652)   
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 complete
-
Final System Tweaks:
UUID=11b1347f-86bb-46e0-8779-764f298bcd3e
Generating: /etc/fstab
# /etc/fstab: static file system information.
#
UUID=11b1347f-86bb-46e0-8779-764f298bcd3e  /  ext4  
noatime,errors=remount-ro  0  1
debugfs  /sys/kernel/debug  debugfs  defaults  0  0
/boot/uEnv.txt: enabling eMMC flasher script
uname_r=4.1.21-bone-rt-r20
#uuid=81b9a3e8-1ff6-4797-b2eb-f4517ab96628
cape_enable=bone_capemgr.enable_partno=BB-APA-01
uuid=11b1347f-86bb-46e0-8779-764f298bcd3e
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
-
Syncing: /dev/mmcblk1
./beaglebone-black-make-microSD-flasher-from-eMMC.sh: line 309:  6860 
Terminated  cylon_leds
10+0 records in
10+0 records out
5120 bytes (51 MB) copied, 2.56244 s, 20.0 MB/s
Syncing: /dev/mmcblk1 complete
-
umount: /tmp: not mounted
umount: /tmp: not mounted



And here is the serial output when tyring to use the uSD:

U-Boot SPL 2016.03-dirty (Apr 19 2016 - 15:43:26)
Trying to boot from MMC
bad magic


U-Boot 2016.03-dirty (Apr 19 2016 - 15:43:26 -0700)

   Watchdog enabled

[beagleboard] Re: Using Beaglebone Black to monitor smoker temperature

[Greg]

>
> I thought of something immediately when I read your post.  There is an 
> extensive article in February 2016 #262 Linux Journal which uses the BBB 
> for beer brewing.  There is a temperature control requirement for the 
> brewing process.
>

This might be a good illustration of how as similar problem is solved. 
 Even if the content of the article does not apply to the smoker, you will 
need to construct the  (Beagle Bone Black Brewery) to complement the 
output of your smoker project.

 https://lj.mybigcommerce.com/linux-journal-february-2016-262/

The article is 23 pages long and has lots of code.

Good luck with your project!
Greg

-- 
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/e8757b18-ab1a-4004-a8b8-cb684bcbca17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Robert Nelson]

On Tue, May 31, 2016 at 4:32 PM, Matt Maher Peterson <
matt.maherpeter...@hydro-care.com> wrote:

> Sorry about that.
>
> So am I interpreting your response right that I need to go back to 4.1.21
> that I am trying to clone, connect it to the network and run the make uSD
> from emmc again to create a new image?
>

rerun:

beaglebone-black-make-microSD-flasher-from-eMMC.sh

making sure you have the network connected and access enabled..

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

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Matt Maher Peterson]

Sorry about that.  

So am I interpreting your response right that I need to go back to 4.1.21 
that I am trying to clone, connect it to the network and run the make uSD 
from emmc again to create a new image?

On Tuesday, May 31, 2016 at 9:06:49 AM UTC-7, RobertCNelson wrote:
>
>
>
> On Tue, May 31, 2016 at 11:00 AM, Matt99eo  > wrote:
>
>> Bump.
>>
>>
>> Still trying to solve this.  Any help appreciated.
>>
>> Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?
>>
>
> Well this had already been answered:
>
> https://groups.google.com/forum/#!category-topic/beagleboard/UIXhMlNXgh0
>
> but then you changed the message "topic" after google groups had already 
> sent the emails out..
>
> Thus losing the reply...
>
> 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/6c2ffa6f-dc6d-4085-8b96-a7203c4cafeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BB-SPIDEV0 is automagically configured

[Andrey Somov]

Well, I still do not get how BB-SPIDEV0 is configured:

root@beaglebone:~# cat /proc/cmdline
console=ttyO0,115200n8 root=UUID=6ba432c0-fb8d-4d56-862d-bb29f5c790d3 ro 
rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd

I searched the whole file system and could not find a text file with 
BB-SPIDEV0.

Can it be a compiled library which was installed ?

Cheers,
Andrey


-- 
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/61da8aa2-68fa-4fe8-a754-5c25d46a5e53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Set default GPIO pin state while in sleep mode

[William Hermans]

Yes. You can initially use universal IO to configure the pin(s), and then
when it is time to sleep, use config-pin to change the pins direction, and
/ of value. There is also the /sys/class/gpio/* sysfs set of sub
directories, but I'm unsure how one would use /sys/class/gpio/export, etc
if the pin it already configured via a deice tree file. Perhaps the device
tree file could take care of the mux mode only, and the sysfs gpio sub
system could configure the rest ?

On Tue, May 31, 2016 at 10:33 AM, E Mag  wrote:

> Hi,
>
> Is there a way to set the GPIO pins into a specific state before entering
> sleep mode on the BBB? I know you can set their configuration in the device
> tree e.g.:
>
>  wlan_pins_sleep: pinmux_wlan_pins_sleep {
> pinctrl-single,pins = <
> 0x28 (PIN_OUTPUT_PULLUP | MUX_MODE7)/*
> gpmc_ad10.gpio0_26 WL_EN*/
> 0x2C (PIN_INPUT_PULLUP | MUX_MODE7) /*
> gpmc_ad11.gpio0_27 WL_IRQ*/
> 0x7C (PIN_OUTPUT_PULLDOWN | MUX_MODE0)  /*
> gpmc_csn0.gpio1_29 BF_EN*/
> >;
> };
>
> But is there a way to set a default output state for certain pins upon
> entering sleep mode without involving the PRU?
>
> Thank you,
>
> -Eric
>
> --
> 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/edf610d9-3468-4ac0-abfe-4df1f8ccef0b%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/CALHSORoYWp1t2D_eVx3MSJAeKfTpk_-jX7SU-6qNg8xZLKEEOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Set default GPIO pin state while in sleep mode

[E Mag]

Hi,

Is there a way to set the GPIO pins into a specific state before entering 
sleep mode on the BBB? I know you can set their configuration in the device 
tree e.g.:

 wlan_pins_sleep: pinmux_wlan_pins_sleep {
pinctrl-single,pins = <
0x28 (PIN_OUTPUT_PULLUP | MUX_MODE7)/* 
gpmc_ad10.gpio0_26 WL_EN*/
0x2C (PIN_INPUT_PULLUP | MUX_MODE7) /* 
gpmc_ad11.gpio0_27 WL_IRQ*/
0x7C (PIN_OUTPUT_PULLDOWN | MUX_MODE0)  /* 
gpmc_csn0.gpio1_29 BF_EN*/
>;
};

But is there a way to set a default output state for certain pins upon 
entering sleep mode without involving the PRU?

Thank you,

-Eric 

-- 
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/edf610d9-3468-4ac0-abfe-4df1f8ccef0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Disable or Rotate the log in the Debian root file system

[Robert Nelson]

On Tue, May 31, 2016 at 8:24 AM,  wrote:

>
> Hi,
>
> I am using the custom image 4.4 with Debian 8.4 root file system. I see a
> log being printed continuously. Could you let me know how to disable the
> log or rotate the log so that it doesn't gets filled up.
>

/etc/systemd/journald.conf

https://www.freedesktop.org/software/systemd/man/journald.conf.html

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

Re: [beagleboard] Problem with a short power loss running from LIPO battery

[William Hermans]

On the software side of things. The Debian package "acpi" is mostly
responsible for this immediate shutdown. How exactly, I'm still not 100%
sure. However . . .

william@beaglebone:~$ cat /proc/interrupts
. . .
*189*:  0  INTC   7 Level tps65217
. . .

william@beaglebone:~$ cat /proc/irq/*189*/spurious
count 0
unhandled 0
last_unhandled 0 ms

This seems to be the file from which userspace can watch for pgood signal
interrupts from the PMIC. I've briefly tested pushing the button, *and*
removing input power, and this file tracks interrupts from both in this
file. That is, the PMIC sends this interrupt, through an NMI pin.

So, you could get your hands on the acpi package source code, and rewrite
is so a power "blip" does not necessarily power down the board. *Or*, you
can uninstall acpi, and write your own code to watch this file, and behave
according to how you feel it needs to behave. Personally, I've been
seriously considering the latter, but I have not gotten to writing said
code for our ow project yet.

On Tue, May 31, 2016 at 5:27 AM, evilwulfie  wrote:

> smart watchdog that cycles the battery via a ssr.
>
>
>
> On 5/31/2016 4:32 AM, benjgrib...@gmail.com wrote:
>
> Hi all,
>
> We've got a real problem with a BeagleBone Black running Debian Jessie
> connected to a LIPO battery through pins TP5-8. The system will  be
> connected to a power supply that can be turned on or off without notice, so
> we added the battery to enable a soft power down and prevent system damage.
>
> Normally this works brilliantly, but if the power only goes off for a
> couple of seconds then the beaglebone is still powering down when the power
> is re-applied then the "PWR" LED comes on, but none of the user LEDs light
> up and the system won't work. While it's in this state powering off and on
> again makes no difference, it just stays like this until the battery runs
> out or until the reset button is pressed.
>
> Has anybody got any ideas?
>
> Thanks,
>
> Brn.
>
>
>
> --
> 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/03ff547f-8cf3-4379-8a69-a9fa2e08c6e6%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/35e08046-62ef-d800-40e8-b3443ea62e01%40gmail.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/CALHSORoXo06sT0bqaCV%3DDP-BneTuEjvuKuNRXw8rkX%3DRZO6TkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Robert Nelson]

On Tue, May 31, 2016 at 11:00 AM, Matt99eo 
wrote:

> Bump.
>
>
> Still trying to solve this.  Any help appreciated.
>
> Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?
>

Well this had already been answered:

https://groups.google.com/forum/#!category-topic/beagleboard/UIXhMlNXgh0

but then you changed the message "topic" after google groups had already
sent the emails out..

Thus losing the reply...

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/CAOCHtYgJ7Q4FL%3Dq9J-nvCVCh-40T%3DUHmXMP_V9m5F4TuHL47PA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Matt99eo]

Bump.


Still trying to solve this.  Any help appreciated.

Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?

On Wednesday, May 25, 2016 at 5:51:56 PM UTC-7, Matt99eo wrote:
>
> Trying to clone a Debian Jesse distro (4.1.21)
> I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh
>
> What am I missing here?
>
> When I insert this into another BBB it crashes before flashing 
> completion.  Here is what I see when a serial debug cable is connected:
>
>
> Starting eMMC Flasher from microSD media
> Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...]
> -
> Checking for Valid bbb-eeprom header
> Valid bbb-eeprom header found [335]
> -
> copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
> lsblk:
> NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> mmcblk1boot0 179:16   01M  1 disk 
> mmcblk1boot1 179:24   01M  1 disk 
> mmcblk0  179:00  3.7G  0 disk 
> `-mmcblk0p1  179:10  3.7G  0 part /
> mmcblk1  179:80  3.7G  0 disk 
> -
> df -h | grep rootfs:
> -
> Erasing: /dev/mmcblk1
> 108+0 records in
> 108+0 records out
> 113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s
> [   31.654940] random: nonblocking pool is initialized
> 108+0 records in
> 108+0 records out
> 113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s
> Erasing: /dev/mmcblk1 complete
> -
> Writing bootloader to [/dev/mmcblk1]
> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k
> -
> dd: failed to open '': No such file or directory[   33.281227] Kernel 
> panic - not syncing: Attempted to kill init! exitcode=0x0100
> [   33.281227] 
> [   33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 
> 4.1.21-bone-rt-r20 #1
> [   33.302856] Hardware name: Generic AM33XX (Flattened Device Tree)
> [   33.309018] [] (unwind_backtrace) from [] 
> (show_stack+0x11/0x14)
> [   33.316808] [] (show_stack) from [] 
> (panic+0x6d/0x188)
> [   33.323719] [] (panic) from [] 
> (complete_and_exit+0x1/0x18)
> [   33.331063] [] (complete_and_exit) from [] 
> (sigprocmask+0x59/0x88)
> [   33.339019] [] (sigprocmask) from [<0001>] (0x1)
> [   33.344883] ---[ end Kernel panic - not syncing: Attempted to kill 
> init! exitcode=0x0100
> [   33.344883] 
>

-- 
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/9270cbfe-e1b2-454d-aaec-2848577d3f19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Disable or Rotate the log in the Debian root file system

[rafiardneriv]

Hi,

I am using the custom image 4.4 with Debian 8.4 root file system. I see a 
log being printed continuously. Could you let me know how to disable the 
log or rotate the log so that it doesn't gets filled up.

Thanks,
Veera

-- 
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/05584f84-a09a-4d8a-bfa4-f735b4c6870d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problem with a short power loss running from LIPO battery

[evilwulfie]

smart watchdog that cycles the battery via a ssr.


On 5/31/2016 4:32 AM, benjgrib...@gmail.com wrote:
> Hi all,
>
> We've got a real problem with a BeagleBone Black running Debian Jessie
> connected to a LIPO battery through pins TP5-8. The system will  be
> connected to a power supply that can be turned on or off without
> notice, so we added the battery to enable a soft power down and
> prevent system damage. 
>
> Normally this works brilliantly, but if the power only goes off for a
> couple of seconds then the beaglebone is still powering down when the
> power is re-applied then the "PWR" LED comes on, but none of the user
> LEDs light up and the system won't work. While it's in this state
> powering off and on again makes no difference, it just stays like this
> until the battery runs out or until the reset button is pressed.
>
> Has anybody got any ideas?
>
> Thanks,
>
> Brn.
>
>
>
> -- 
> 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/03ff547f-8cf3-4379-8a69-a9fa2e08c6e6%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/35e08046-62ef-d800-40e8-b3443ea62e01%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Problem with a short power loss running from LIPO battery

[benjgribble]

Hi all,

We've got a real problem with a BeagleBone Black running Debian Jessie 
connected to a LIPO battery through pins TP5-8. The system will  be 
connected to a power supply that can be turned on or off without notice, so 
we added the battery to enable a soft power down and prevent system damage. 

Normally this works brilliantly, but if the power only goes off for a 
couple of seconds then the beaglebone is still powering down when the power 
is re-applied then the "PWR" LED comes on, but none of the user LEDs light 
up and the system won't work. While it's in this state powering off and on 
again makes no difference, it just stays like this until the battery runs 
out or until the reset button is pressed.

Has anybody got any ideas?

Thanks,

Brn.



-- 
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/03ff547f-8cf3-4379-8a69-a9fa2e08c6e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to boot, "external abort on non-linefetch", "internal error ... SMP THUMB2"

[daneduplooy]

Hi!

I am having trouble getting one of our BBB to boot, and I am curious to 
understand the problem. After much Google-ing with no success I have 
decided to resort to bothering somebody else by asking about the problem.

Please see below log from the serial port, the problem to me seems to be on 
the lines:
*[1.039071] Unhandled fault: external abort on non-linefetch (0x1008) 
at 0xe089c000*
*[1.047198] Internal error: : 1008 [#1] SMP THUMB2*

I have no idea where to even start with understanding why these errors 
would occur :-).

Many thanks for your valuable time!
Dane


U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)


U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build: 
jenkins-github_Bootloader-Builder-105

   Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:not set. Validating first E-fuse MAC
Phy 0 not found
cpsw
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
reading uEnv.txt
933 bytes read in 6 ms (151.4 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
776 bytes read in 89 ms (7.8 KiB/s)
5617184 bytes read in 486 ms (11 MiB/s)
2867606 bytes read in 290 ms (9.4 MiB/s)
26098 bytes read in 123 ms (207 KiB/s)
Kernel image @ 0x8200 [ 0x00 - 0x55b620 ]
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Using Device Tree in place at 8800, end 880095f1

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[0.373013] omap2_mbox_probe: platform not supported
[0.527930] tps65217-bl tps65217-bl: no platform data provided
[0.591166] bone-capemgr bone_capemgr.9: slot #0: No cape found
[0.628275] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.665383] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.702492] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.718308] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)
[0.727901] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[0.734644] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 
BB-BONELT-HDMIN:00A0 (prio 2)
[0.751035] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
failed
[0.814111] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.825789] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
-22
[0.833060] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
*[1.039071] Unhandled fault: external abort on non-linefetch (0x1008) 
at 0xe089c000*
*[1.047198] Internal error: : 1008 [#1] SMP THUMB2*
[1.052265] Modules linked in:
[1.055503] CPU: 0Not tainted  (3.8.13-bone70 #1)
[1.060854] PC is at cpsw_probe+0x348/0x960
[1.065291] LR is at ioremap_page_range+0x95/0xf8
[1.070266] pc : []lr : []psr: a033
[1.070266] sp : df071e18  ip :   fp : df0d3400
[1.082402] r10: c0837c18  r9 : de102000  r8 : de102590
[1.087934] r7 : de102000  r6 : de102540  r5 :   r4 : e089c000
[1.094830] r3 : 8000  r2 :   r1 : e089d000  r0 : e089c000
[1.101731] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb 
 Segment kernel
[1.109637] Control: 50c5387d  Table: 9e280019  DAC: 0015
[1.115703] Process swapper/0 (pid: 1, stack limit = 0xdf070240)
[1.122047] Stack: (0xdf071e18 to 0xdf072000)
[1.126645] 1e00:   
 c00b6a89
[1.135287] 1e20: c0883bb8 c0883bb8 de102540 de102298 df0d3410 de5fcac8 
 df071e90
[1.143912] 1e40: df071e90 c00ff1b3    c0883bb8 
de5fcac8 de23d9c0
[1.152545] 1e60: de5fcac8 c00ff0ef de5fcac8  df071e90 de5fcb48 
df0d5c48 c00ff967
[1.161191] 1e80: df0494b8 c0049697  df0d3444 0020 0008 
df0d3410 c0932e2c
[1.169831] 1ea0: df0d3410 c08a2c40  c081a039 0100 c0837c18 
 c02c8279
[1.178468] 1ec0: c02c8269 c02c771b  df0d3410 c08a2c40 df0d3444 
 c02c787b
[1.187097] 1ee0: c08a2c40 c02c7831  c02c684f df049478 df0c4180 
c08a2c40 c0898090
[1.195735] 1f00: de23d9c0 c02c720f c07460fc c08a2c40 c08a2c40 df07 
c08c3980 
[1.204373] 1f20: c081a039 c02c7b7d  c0824838 df07 c08c3980 
 c081a039
[1.213014] 1f40: 0100 c000867f 0007 0007 c087bc98 c0824834 
c0824838 0007
[1.224272] 1f60: c0824818 c08c3980 c07fe1c9 c0837c18  c07fe6a3 
0007 0007
[1.235517] 1f80: c07fe1c9 c0d50fc0  c04c77c9   
 
[1.246750] 

Re: [beagleboard] BeagleBone Black Kernel Main Differences

[yolcopc]

Thanks all!!

I'm looking for a kernel that allow me to control a screen with touchpanel 
and a integrated speaker (I have published a concrete thread for this 
without any response yet), so understansing the differences between kernels 
could help me to know which is the best for my application, or at least, 
how I can proceed to solve the issues I have now.

The application needs to control some peripherals more than the screen, and 
this is why I'm asking about 'rt' versions too.

-- 
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/9f4510be-ed3f-4f19-9fd1-f83fb078d2cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: USB boot of BeagleBoneBlack

[Venky Venkatesh]

Hi andrey somov,
Thanks for responding to my question, actually my question is, i
wanted to boot my beagle bone black board from USB, not from eMMC or
SD card, for that i connected my board to the ubuntu 14.04. And i did
my USB stick into two partitions, one is for boot, another partition
is for root file system. And i copied my compiled images MLO,
u-boot.img, zImage, am335x-boneblack.dtb file to the /boot partition
and root file system to ext4 partition.
And my bbb is already having the u-boot, so it is booting and stuck in
u-boot command prompt, there i have used the usb commands and tried to
load the first partition, i.e usb part 0, but i got error message as
"Unknown partition table"
Can you suggest me the better way to boot my bealge bone black using USB

Thanks & Regards
Venkatesh

On Tue, May 31, 2016 at 2:42 PM, Andrey Somov  wrote:
> Dear Venky,
> your question is very unclear and incomplete.
> I do not get what it mean "to boot from USB".
>
> Can you connect your board with the computer ? Is it Unix ?
> Do you see anything if you ssh to 192.168.7.2 ?
>
> Cheers,
> Andrey
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/R_KPVujN5XM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/2635c012-e161-4f1e-bfc7-32673959fa3c%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/CAONbAMtegQ-hUjq6MHLBGSA%2B1bA-ZVQKjpNhnkUj%3DFGadutgeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: RFID CR95HF with Beaglebone black

[Andrey Somov]

Is this what you are looking for:

http://www.st.com/content/st_com/en/products/embedded-software/st25-nfc-rfid-software/stsw-95hf004.html

Cheers,
Andrey


On Tuesday, May 31, 2016 at 6:25:58 AM UTC+2, nguyen cao wrote:
>
> Hi All,
> I wirte code for CR95HF with beaglebone black,but I not find library of 
> CR95HF for beaglebone black,
> If all you wirte code CR95HF with beaglebone black using library of CR95HF 
> ,pls help.
> Thanks very much.
>

-- 
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/e8d2d8a8-6092-4a38-8afd-20ecadec6b81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: USB boot of BeagleBoneBlack

[Andrey Somov]

Dear Venky,
your question is very unclear and incomplete.
I do not get what it mean "to boot from USB".

Can you connect your board with the computer ? Is it Unix ?
Do you see anything if you ssh to 192.168.7.2 ?

Cheers,
Andrey

-- 
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/2635c012-e161-4f1e-bfc7-32673959fa3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Memory for PRU size and allocation (external, SDRAM, SD card)

[William Hermans]

>
> *However, this limit of 0xBC5799 is always changing (increasing or
> decreasing) when I reboot my board.*
> *Did someone have an idea on the exact amount of this limit ?*
> *Rq : I didn't succeed to find it in the TRM(Technical reference manual)*
>

This is not something that would be in the TRM. This is related to the uio
driver, and perhaps the uio_pruss driver is limiting the amount of ram used
somehow. Or perhaps it's a uio driver limitation ? Pagefile size ? This
would require some looking into.


>
> * My other question is :Is there a way that I can save the data from PRU
> directly into the SDRAM of 512MB or on the SD card, or is it impossible ?If
> so what are the corresponding addresses or methods to use them ?*
>

You're already storing data into 12M of the 512M DDR RAM. Nothing is
impossible in this context, and all is possible. There are also multiple
ways, but probably the easiest way will involve using POSIX IPC from
userspace. Or you could even write a kernel module, if that's not much of a
problem for you.

Something you may want to keep in mind however. 12M is pushing the
performance boundaries of just about any beaglebone media *except* memory.
Meaning, no matter where where you plan on storing that data outside of
DDR, it's going to take a considerable amount of time( figuratively
speaking ) to move that data around. The onboard Ethernet for instance is
only capable of around ~11.5M / second transfers. The sdcard interface is
not much better, nor is the eMMC.

On Tue, May 31, 2016 at 12:15 AM, Vincent lc 
wrote:

> Hi,
>
> I'm currently trying to save data into the memory from a PRU application.
>
> Currently I can store data up to ~12.3 MB :
>
> I can change it with
> modprobe uio_pruss extram_pool_sz=0xBC5798
>
> This command works but for 0xBC5799 it doesn't.
> I figured this idea out from this post
> https://groups.google.com/forum/#!searchin/beagleboard/extram_pool_sz/beagleboard/Gb6xL7V7Z00/GtEy703CursJ
> and also from the eRam part on this page
> http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_memory.html
> In addition, I also assumed that the difference between 0x80 and
> 0xBC5799 is link to the fact that I'm using a more recent version of the
> Board (beagle Bone black ) or to the kernel
> 4.1.21-bone-rt-r20.
>
> However, this limit of 0xBC5799 is always changing (increasing or
> decreasing) when I reboot my board.
> Did someone have an idea on the exact amount of this limit ?
> Rq : I didn't succeed to find it in the TRM(Technical reference manual)
>
> My other question is :
> Is there a way that I can save the data from PRU directly into the SDRAM
> of 512MB or on the SD card, or is it impossible ?
> If so what are the corresponding addresses or methods to use them ?
>
> Thanks by advance
> Regards
>
> Vincent
> "Enjoy life no matter what !"
>
> --
> 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/dcc91fda-ce7d-4718-967e-ff8799d51f1f%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/CALHSORrFQKsAomAeD3fxFtgYmOE7k6o8N27XKkbTmGyLb3B6QA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Memory for PRU size and allocation (external, SDRAM, SD card)

[Vincent lc]

Hi,

I'm currently trying to save data into the memory from a PRU application.

Currently I can store data up to ~12.3 MB :

I can change it with
modprobe uio_pruss extram_pool_sz=0xBC5798

This command works but for 0xBC5799 it doesn't. 
I figured this idea out from this post 
https://groups.google.com/forum/#!searchin/beagleboard/extram_pool_sz/beagleboard/Gb6xL7V7Z00/GtEy703CursJ
and also from the eRam part on this page 
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_memory.html
In addition, I also assumed that the difference between 0x80 and 
0xBC5799 is link to the fact that I'm using a more recent version of the 
Board (beagle Bone black ) or to the kernel 
4.1.21-bone-rt-r20.

However, this limit of 0xBC5799 is always changing (increasing or 
decreasing) when I reboot my board.
Did someone have an idea on the exact amount of this limit ?
Rq : I didn't succeed to find it in the TRM(Technical reference manual)

My other question is :
Is there a way that I can save the data from PRU directly into the SDRAM of 
512MB or on the SD card, or is it impossible ? 
If so what are the corresponding addresses or methods to use them ?

Thanks by advance 
Regards

Vincent
"Enjoy life no matter what !"

-- 
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/dcc91fda-ce7d-4718-967e-ff8799d51f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Using Beaglebone Black to monitor smoker temperature

[Robert Budde]

Hi Alex,

I adopted the Raspberry PI "PicoReflow" project to the beaglebone: 
https://github.com/robert-budde/picoReflow . Using K-Type thermocouples and 
being able to control a vent and a "heater" should give you a fast start. 
Temp profile etc is all there.

BR
Robert

-- 
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/9e54701a-d252-45cb-8ae7-b430600937f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: USB boot of BeagleBoneBlack

[Venky Venkatesh]

Any one help out me please.

On Tuesday, 31 May 2016 10:56:13 UTC+5:30, Venky Venkatesh wrote:
>
> Hi, I wanted to boot my Beagle Bone Black through USB, i tried to boot 
> from USB by pressing the switch, but i didn't get anything in terminal, and 
> i don't know how it works.
> Any help could be appreciate.
>

-- 
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/36a04c0a-27ba-48af-b2a8-60ac640bda0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.