Re: [beagleboard] Desired existing open source cape recommendation

2017-02-08 Thread Graham
Looks like Andice Labs has two capes of interest.

If you want to run from a single cell lithium, then their "Power Cape" 
looks interesting.
http://andicelabs.com/beaglebone-powercape/

If you want to run from and maintain a 12V Lead-acid battery, then their 
"Solar Power Cape" looks interesting.
http://andicelabs.com/beaglebone-solar-cape/

--- Graham

==

On Wednesday, February 8, 2017 at 6:40:04 PM UTC-6, William Hermans wrote:
>
> If someone here is really good at PCB / electronics design, I can verbally 
> explain exactly what needs doing, Also, while I personally do prefer an 
> external style UPS( wide input voltage ). There is probably something to be 
> said for a cape that has an power management micro controller, plus lets 
> say an 18650 LiPo battery holder, etc. I really think having hte ability to 
> use 18650 style batteries would be an awesome feature. 
>
> On Wed, Feb 8, 2017 at 7:31 AM, Jason Kridner  > wrote:
>
>> Is the Andice cape readily available already? Is it good for the UPS 
>> function?
>>
>> On Wed, Feb 8, 2017 at 9:26 AM Graham > > wrote:
>>
>>> I would like to support William's recommendation for a UPS type cape.
>>>
>>> Something that would allow the BBB to operate directly from ~11V to ~21V
>>> Instantly switch to an optional +12V battery if present, upon primary 
>>> power loss.
>>> Recharge and float the optional +12V battery, if present, after any use.
>>> A couple of status outputs.
>>>
>>> Intended for use in server or remote applications of the BBB.
>>> Could also be used as a wide range power supply input without the 
>>> optional UPS battery.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>>
>>> On Tuesday, February 7, 2017 at 2:17:55 PM UTC-6, William Hermans wrote:
>>>
 I'd recommend just about any decent UPS type cape with good power 
 management features. e.g. Features that addressed the Beaglebone's 
 inability to function remotely( well ).

>>> On Tue, Feb 7, 2017 at 1:00 PM, Jason Kridner  wrote:

>>> Anyone want to nominate an open source cape to go into production via a 
> group buy?
>
> If I don't get suggestions, I'll recommend: 
> http://elinux.org/BeagleBone_Black_RFID_Adaptor_Cape or 
> https://github.com/cclark2/interacto_bbone_cape. 
>
 -- 
> 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...@googlegroups.com.


> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmCC1VDYUXogqwQRBMYqhAh7X5GjEP_2oswGFHTb6qnDg%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...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/491d838b-47a4-4adc-8ffd-fbbfb8ac239c%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmUc8qhi9suXQnWL0yUh9J2qoSYaqJed00Z5ejLmQh3zw%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/17d53767-57cd-427b-af63-3b6336f59336%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Desired existing open source cape recommendation

2017-02-08 Thread William Hermans
If someone here is really good at PCB / electronics design, I can verbally
explain exactly what needs doing, Also, while I personally do prefer an
external style UPS( wide input voltage ). There is probably something to be
said for a cape that has an power management micro controller, plus lets
say an 18650 LiPo battery holder, etc. I really think having hte ability to
use 18650 style batteries would be an awesome feature.

On Wed, Feb 8, 2017 at 7:31 AM, Jason Kridner 
wrote:

> Is the Andice cape readily available already? Is it good for the UPS
> function?
>
> On Wed, Feb 8, 2017 at 9:26 AM Graham  wrote:
>
>> I would like to support William's recommendation for a UPS type cape.
>>
>> Something that would allow the BBB to operate directly from ~11V to ~21V
>> Instantly switch to an optional +12V battery if present, upon primary
>> power loss.
>> Recharge and float the optional +12V battery, if present, after any use.
>> A couple of status outputs.
>>
>> Intended for use in server or remote applications of the BBB.
>> Could also be used as a wide range power supply input without the
>> optional UPS battery.
>>
>> --- Graham
>>
>> ==
>>
>>
>> On Tuesday, February 7, 2017 at 2:17:55 PM UTC-6, William Hermans wrote:
>>
>> I'd recommend just about any decent UPS type cape with good power
>> management features. e.g. Features that addressed the Beaglebone's
>> inability to function remotely( well ).
>>
>> On Tue, Feb 7, 2017 at 1:00 PM, Jason Kridner  wrote:
>>
>> Anyone want to nominate an open source cape to go into production via a
>> group buy?
>>
>> If I don't get suggestions, I'll recommend: http://elinux.org/
>> BeagleBone_Black_RFID_Adaptor_Cape or https://github.com/
>> cclark2/interacto_bbone_cape.
>>
>> --
>> 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...@googlegroups.com.
>>
>>
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/beagleboard/CA%2BT6QPmCC1VDYUXogqwQRBMYqhAh7X
>> 5GjEP_2oswGFHTb6qnDg%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/491d838b-47a4-4adc-8ffd-fbbfb8ac239c%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/CA%2BT6QPmUc8qhi9suXQnWL0yUh9J2qo
> SYaqJed00Z5ejLmQh3zw%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/CALHSORqb7fn3z0nVPH2qEnVSN03TJVc5Bd6rkGRd18d2Y2jhMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: PRU SPI ADC communication

2017-02-08 Thread William Hermans
> I dont know if u can answer me, but i have another two question. What is
the max RAM i can allocate to the samples from PRU, and if is possible to
write directly to an uSDcard working as external
> memory from the PRU. If not, i can do the a discuss about this.

Theoretically, you should be able to access and use all of the ARM's system
memory. Realistically, I'd say you could probably use up to around
300M-400M of the main processors memory. The system needs around ~100M for
processes, and buffering. With all that said, your bottleneck is going to
be the medium you choose to store your samples to. I would avoid the emmc,
as repeated writting / erasing to the emmc would make "short work" of the
emmc. e.g. You'd probably kill the emmc pretty fast. An sdcard will
probably die much quicker.

So the way I see it is that you have two viable options. Some sort of
networked storage, or use an external USB hard drive. Of these two when I
tested this, USB was the fastest option at around 20 Megabytes/second
throughput. The onboard Ethernet is really fast for ethernet at around  ~11
Megabytes / second with the correct tweaks.

Maybe what you really need is a fast C application that grabs the data from
the PRU's memory directly, in real-time, and shuttle that data out just as
fast as you need to. Just off the top of my head, 500ksps will probably be
between 6-7 Megabytes a second, in plain text format. If you dream up some
sort of data packing format, perhaps a good bit less.

-- 
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/CALHSORq18OH%2BoBa2vV-BfHiAiLe%2BKunO586Oh4ET5LaNtCFQ7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread William Hermans
On Wed, Feb 8, 2017 at 3:16 PM, evilwulfie  wrote:

> ME and a software buddy have a nice watchdog timer powered from the BBB
> battery holds up the BBB till it shuts down then removes power
> draws 400uA from the battery while waiting for the power to be reapplied.
>

So, in a pinch, and if you have  physical access to the board. You can use
a LiPO battery, connected to the PMIC battery test points( ask an EE if you
need specifics ), then install the debian package acpid. Then everything
should be fine. e.g. the board will power down cleanly. However, the PMIC
will still be supplying a bit of power from the battery. So if you need it
shutdown for an extended time period. You'll need to disconnect the battery.

As for remotely installed systems. You'll have to design a watchdog / power
management system to disconnect the battery, and reset the processor when
power is reapplied. This is why in Jason's post yesterday, or the day
before. I mentioned I like to see a proper UPS cape with good power
management features built in. The beaglebone as it is is what I'd consider
a very good board, but to cut costs, when designed. Several things were
left out of the board. So instead of paying $100 + per board, we pay ~$50
per board, and design in features we need for our own situations. A fair
trade, but something we need to be aware of.

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


Re: [beagleboard] Failed to start Cape Manager Service.

2017-02-08 Thread Robert Nelson
On Wed, Feb 8, 2017 at 4:32 PM,   wrote:
> During boot I am getting a "Failed to start Cape Manager Service." failure
>
> I have a custom cape that gets loaded via /uEnv.txt along with BB_SPIDEV0,
> both show up in slots
>
> my problem is that the disable for HDMI does not work as the pinmux still
> shows the hdmi pins as assigned.
>
> OS Version
> uname -r 4.1.38-bone-rt-r24

See:

http://elinux.org/Beagleboard:BeagleBone_Debian_Image_Migration#Disabling_eMMC_or_HDMI

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


[beagleboard] Failed to start Cape Manager Service.

2017-02-08 Thread kevin_loll
During boot I am getting a "Failed to start Cape Manager Service." failure

I have a custom cape that gets loaded via /uEnv.txt along with BB_SPIDEV0, 
both show up in slots

my problem is that the disable for HDMI does not work as the pinmux still 
shows the hdmi pins as assigned.

*OS Version*
uname -r 4.1.38-bone-rt-r24

# systemctl status capemgr.service -l
● capemgr.service - Cape Manager Service
   Loaded: loaded (/lib/systemd/system/capemgr.service; enabled)
   Active: failed (Result: exit-code) since Wed 2017-02-08 14:48:51 CST; 
2min 44s ago
  Process: 313 ExecStart=/bin/sh /opt/scripts/boot/capemgr.sh (code=exited, 
status=1/FAILURE)
 Main PID: 313 (code=exited, status=1/FAILURE)


I have tried several different versions of the disable_partno I have found.
= /uEnv.txt
##This will work with: Angstrom's 2013.06.20 u-boot.

loadaddr=0x8200
fdtaddr=0x8800
rdaddr=0x8808

initrd_high=0x
fdt_high=0x

#for single partitions:
mmcroot=/dev/mmcblk0p1
optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
dtb=am335x-boneblack-emmc-overlay.dtb
cape_enable=bone_capemgr.enable_partno=BB-GPIO-1553,BB-SPIDEV0

loadximage=load mmc 0:1 ${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=load mmc 0:1 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize 
${filesize}
loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t 
${loadaddr} ${filesize};
loadall=run loaduEnvtxt; run loadximage; run loadxfdt;

mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} 
${cape_disable} ${cape_enable} root=${mmcroot} rootfstype=${mmcrootfstype} 
${cmdline}

uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} - ${fdtaddr};


-- 


---
This e-mail and any attached files may contain WINTEC, Inc., proprietary 
information and may be legally privileged or subject to export control 
restrictions.  If you are not the addressee, any disclosure, reproduction, 
copying, distribution, or other dissemination or use of this communication 
is strictly prohibited.  If you have received this transmission in error 
please reply to the sender immediately and then delete this e-mail.

-- 
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/7d7c8a7f-f552-4cf8-8f78-d5e66ebaec3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread evilwulfie
ME and a software buddy have a nice watchdog timer powered from the BBB
battery holds up the BBB till it shuts down then removes power
draws 400uA from the battery while waiting for the power to be reapplied.


On 2/8/2017 2:57 PM, Roman Prilutsky wrote:
>
>
> On Wednesday, February 8, 2017 at 7:34:08 AM UTC-5, Roman Prilutsky
> wrote:
>
> My BBB was running debian jessie and i could access it over USB
>  and Ethernet. Then, after one power off/power on it stopped
> booting from eMMC. To be exact I stoped been able too access it
> over both USB and Ethernet.  I can still boot the board from SD
> and access the bard.  eMMC boot though seems never finishes. I can
> see leds blinking in a normal boot sequence and then they end up
> with one led blinking for ever. 
> If i boot from SD i can access eMMC file system (rootfs) and my
> /etc/network/interface on eMMC looks normal. I do not know of any
> other way to read a boot log on eMMC or anything to help me to
> understand the issue.
> Of course i could re-flash eMMC but then i will never know what
> happen :( Any help/ideas are greatly appreciated. Thanks!
>
> Thanks Wulf Man. What exactly have you done to avoid this
> limitation? I'd love to do the same.
>
> -- 
> 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/9c4640af-759f-4f8a-bba8-6ded717dca0a%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/02c88ca6-12fd-0519-5eb8-54aa2c6fc991%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: Invalid partition message during boot

2017-02-08 Thread acheesehead
Robert,

My u-boot mod somehow got wiped. Put it back in and recompiled. I'm still 
having a problem with the device tree (which I don't know enough about):

U-Boot 2017.03-rc1-dirty (Feb 08 2017 - 15:00:15 -0700)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Beagle xM Rev C
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 715e00029ff80156083e0501c01d
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
53 bytes read in 7 ms (6.8 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-4.9.7-armv7-rt-x4 ...
6435000 bytes read in 499 ms (12.3 MiB/s)
loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle-xm.dtb ...
100032 bytes read in 233 ms (418.9 KiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait] ...
debug: [bootz 0x8200 - 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Device Tree to 8ffe4000, end 86bf ... OK
fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###


On Wednesday, February 8, 2017 at 1:39:01 PM UTC-7, RobertCNelson wrote:
>
> On Wed, Feb 8, 2017 at 2:33 PM, acheesehead  > wrote: 
> > Boots ok on Beagleboard xM, but hangs on our custom board. 
> > 
> > U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18) 
> > Trying to boot from MMC1 
> > SPL: Please implement spl_start_uboot() for your board 
> > SPL: Direct Linux boot not active! 
> > reading u-boot.img 
> > reading u-boot.img 
> > 
> > 
> > U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700) 
> > 
> > OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz 
> > OMAP3 Beagle board + LPDDR/NAND 
>
> > Beagle Rev Ax/Bx 
>
> > loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ... 
>
> Why is your board going down the Beagle classic route? 
>
> Take a look at the gpio's used for id on the xM C, you messed those up 
> when you built your custom board.. 
>
> 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/cefbf17e-aea8-4eff-b8fd-48aca613d1f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread Roman Prilutsky


On Wednesday, February 8, 2017 at 7:34:08 AM UTC-5, Roman Prilutsky wrote:
>
> My BBB was running debian jessie and i could access it over USB  and 
> Ethernet. Then, after one power off/power on it stopped booting from eMMC. 
> To be exact I stoped been able too access it over both USB and Ethernet.  I 
> can still boot the board from SD and access the bard.  eMMC boot though 
> seems never finishes. I can see leds blinking in a normal boot sequence and 
> then they end up with one led blinking for ever. 
> If i boot from SD i can access eMMC file system (rootfs) and my 
> /etc/network/interface on eMMC looks normal. I do not know of any other way 
> to read a boot log on eMMC or anything to help me to understand the issue.
> Of course i could re-flash eMMC but then i will never know what happen :( 
> Any help/ideas are greatly appreciated. Thanks!
>
> Thanks Wulf Man. What exactly have you done to avoid this limitation? I'd 
> love to do the same.
>

-- 
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/9c4640af-759f-4f8a-bba8-6ded717dca0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: Invalid partition message during boot

2017-02-08 Thread Robert Nelson
On Wed, Feb 8, 2017 at 2:33 PM, acheesehead  wrote:
> Boots ok on Beagleboard xM, but hangs on our custom board.
>
> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> OMAP3 Beagle board + LPDDR/NAND

> Beagle Rev Ax/Bx

> loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ...

Why is your board going down the Beagle classic route?

Take a look at the gpio's used for id on the xM C, you messed those up
when you built your custom board..

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


[beagleboard] Re: Invalid partition message during boot

2017-02-08 Thread acheesehead
Boots ok on Beagleboard xM, but hangs on our custom board.

U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
Trying to boot from MMC1
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Beagle Rev Ax/Bx
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 715e00029ff80156083e0501c01d
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
26 bytes read in 7 ms (2.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-4.9.7-armv7-rt-x4 ...
6435000 bytes read in 499 ms (12.3 MiB/s)
loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ...
98676 bytes read in 210 ms (458 KiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait musb_hdrc.fifo_mode=5] ...
debug: [bootz 0x8200 - 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Device Tree to 8ffe4000, end 8173 ... OK
fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###


On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as 
> in Robert C. Nelson's page 
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
> Here is what I get during boot, tried on a real Beagleboard xM and get the 
> same behavior. The booting stops at a u-boot prompt.
>
> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - readenv() failed, using default environment
>
> Beagle xM Rev C
> No EEPROM on expansion board
> No EEPROM on expansion board
> OMAP die ID: 101000229ff8016830c319017022
> Net:   usb_ether
> Error: usb_ether address not set.
>
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> 26 bytes read in 7 ms (2.9 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> ** Invalid partition 3 **
> ** Invalid partition 4 **
> ** Invalid partition 5 **
> ** Invalid partition 6 **
> ** Invalid partition 7 **
> =>
>
>

-- 
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/b03e465d-a7b4-4016-a8db-a3480f160973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Invalid partition message during boot

2017-02-08 Thread robertsmaria934 via BeagleBoard


On Wed, 2/8/17, Robert Nelson  wrote:

 Subject: Re: [beagleboard] Invalid partition message during boot
 To: "Beagle Board" 
 Cc: acheeseh...@gmail.com
 Date: Wednesday, February 8, 2017, 10:16 PM
 
 On Wed, Feb 8, 2017 at
 2:10 PM, acheesehead 
 wrote:
 > I built Linux RT for a custom
 board based upon Beagleboard xM exactly as in
 > Robert C. Nelson's page
 https://eewiki.net/display/linuxonarm/BeagleBoard.
 >
 > Here is what I get
 during boot, tried on a real Beagleboard xM and get the
 > same behavior. The booting stops at a
 u-boot prompt.
 >
 >
 U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
 > Trying to boot from MMC1
 > SPL: Please implement spl_start_uboot()
 for your board
 > SPL: Direct Linux boot
 not active!
 > reading u-boot.img
 > reading u-boot.img
 >
 >
 > U-Boot
 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
 >
 > OMAP3630/3730-GP
 ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
 > OMAP3 Beagle board + LPDDR/NAND
 > I2C:   ready
 > DRAM:  512 MiB
 >
 NAND:  0 MiB
 > MMC:   OMAP
 SD/MMC: 0
 > *** Warning - readenv()
 failed, using default environment
 >
 > Beagle xM Rev C
 > No
 EEPROM on expansion board
 > No EEPROM on
 expansion board
 > OMAP die ID:
 101000229ff8016830c319017022
 >
 Net:   usb_ether
 > Error:
 usb_ether address not set.
 >
 > Hit any key to stop autoboot:  0
 > switch to partitions #0, OK
 > mmc0 is current device
 > Scanning mmc 0:1...
 >
 switch to partitions #0, OK
 > mmc0 is
 current device
 > SD/MMC found on device
 0
 > Checking for: /uEnv.txt ...
 > Checking for: /boot/uEnv.txt ...
 > 26 bytes read in 7 ms (2.9 KiB/s)
 > Loaded environment from /boot/uEnv.txt
 > Checking if uname_r is set in
 /boot/uEnv.txt...
 > Running uname_boot
 ...
 > ** Invalid partition 3 **
 > ** Invalid partition 4 **
 > ** Invalid partition 5 **
 > ** Invalid partition 6 **
 > ** Invalid partition 7 **
 
 Please share your
 "/boot/uEnv.txt"
 
 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/CAOCHtYhPsFhONnBb0d4MXhQfqkCCJoSaMGJ4c%2BEf5Xa8W76JPA%40mail.gmail.com.
 For
 more options, visit https://groups.google.com/d/optout.
 stfel  este recunoscuta suveranitatea poporului  singura in masura sa acorde 
puterea si sa impuna legea. Tot ce nu s-a oranduit prin alegerea s' vointa a 
tot norodul  urmeaza a se indeparta. Adunarea norodului  reprezinta vointa 
suverana in stat.

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


[beagleboard] Re: Invalid partition message during boot

2017-02-08 Thread acheesehead
Got around that problem. My uEnv.txt file was wrong.

On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as 
> in Robert C. Nelson's page 
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
>
>

-- 
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/640d76a5-d182-46e2-808a-6f9aca1dc86d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Invalid partition message during boot

2017-02-08 Thread Robert Nelson
On Wed, Feb 8, 2017 at 2:10 PM, acheesehead  wrote:
> I built Linux RT for a custom board based upon Beagleboard xM exactly as in
> Robert C. Nelson's page https://eewiki.net/display/linuxonarm/BeagleBoard.
>
> Here is what I get during boot, tried on a real Beagleboard xM and get the
> same behavior. The booting stops at a u-boot prompt.
>
> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - readenv() failed, using default environment
>
> Beagle xM Rev C
> No EEPROM on expansion board
> No EEPROM on expansion board
> OMAP die ID: 101000229ff8016830c319017022
> Net:   usb_ether
> Error: usb_ether address not set.
>
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> 26 bytes read in 7 ms (2.9 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> ** Invalid partition 3 **
> ** Invalid partition 4 **
> ** Invalid partition 5 **
> ** Invalid partition 6 **
> ** Invalid partition 7 **

Please share your "/boot/uEnv.txt"

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


[beagleboard] Invalid partition message during boot

2017-02-08 Thread acheesehead
I built Linux RT for a custom board based upon Beagleboard xM exactly as in 
Robert C. Nelson's page https://eewiki.net/display/linuxonarm/BeagleBoard.

Here is what I get during boot, tried on a real Beagleboard xM and get the 
same behavior. The booting stops at a u-boot prompt.

U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
Trying to boot from MMC1
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Beagle xM Rev C
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 101000229ff8016830c319017022
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
26 bytes read in 7 ms (2.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
=>

-- 
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/c0b994fd-afff-4bbc-91dc-2c9a668d3531%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread evilwulfie
If you want a board that can be unplugged with no damage better look
elsewhere.
Or do what i have done and design around that limitation.


On 2/8/2017 12:22 PM, Roman Prilutsky wrote:
> No. I am developing some software to run as a part of an automation
> project, so expect the board to be tolerant to the power loss. So i
> just pulled the pug out - no shutdown -h. 
> What could break and what is a way to diagnose it?
>
>
>
>  
>
> On Wednesday, February 8, 2017 at 7:34:08 AM UTC-5, Roman Prilutsky
> wrote:
>
> My BBB was running debian jessie and i could access it over USB
>  and Ethernet. Then, after one power off/power on it stopped
> booting from eMMC. To be exact I stoped been able too access it
> over both USB and Ethernet.  I can still boot the board from SD
> and access the bard.  eMMC boot though seems never finishes. I can
> see leds blinking in a normal boot sequence and then they end up
> with one led blinking for ever. 
> If i boot from SD i can access eMMC file system (rootfs) and my
> /etc/network/interface on eMMC looks normal. I do not know of any
> other way to read a boot log on eMMC or anything to help me to
> understand the issue.
> Of course i could re-flash eMMC but then i will never know what
> happen :( Any help/ideas are greatly 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/c1e88630-ebf7-427b-8943-564bd650bbf9%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/e4ae5261-5fff-8906-57f1-708939c351b8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: PRU SPI ADC communication

2017-02-08 Thread Graham Haddock
Hi David:

I am glad to hear that you got it fixed.

I am posting your reply back to the Beaglebone reflector, so others can
benefit from the discussion.

If you are talking about RAM in the PRU, perhaps some PRU expert can answer
your question. (I am not a PRU expert.)

If you are talking about RAM in the main Sitara memory space, use the Linux
command "free".  You can Google that.

In order to write to a uSD card, I am sure that you will need to have a
small application that will take
the data from the PRU and move it to the uSD card.

--- Graham

==
David Caniceiro


to me
Hi Graham,

Thanks for your answer, i solved the problem minutes after, and it was a
hardware problem in the reference.

I dont know if u can answer me, but i have another two question. What is
the max RAM i can allocate to the samples from PRU, and if is possible to
write directly to an uSDcard working as external memory from the PRU. If
not, i can do the a discuss about this.

Best Regards,
David

On Wed, Feb 8, 2017 at 10:30 AM, Graham  wrote:

> Hi David:
>
> I think it is a hardware problem.
>
> It looks like you are not doing a good job referencing your ground input
> for the ADC, or you have a very dirty Voltage reference for the ADC.
>
> Either way, it is picking up some serious offset from a switching power
> supply (The PMMIC ???) somehow.
>
> I think you need to do an audit of the power going to the Voltage
> reference for the ADC, and the connection of the positive and negative
> Voltage references, and the negative input on the ADC.
>
> --- Graham
>
> ==
>
>
>
> On Wednesday, February 8, 2017 at 6:34:37 AM UTC-6,
> davidvaran...@gmail.com wrote:
>>
>> Hi,
>>
>> I adapted the code from  Derek Molloy example -
>> http://exploringbeaglebone.com/chapter13/ - https://github.com/derekmoll
>> oy/exploringBB/tree/master/chp13/adc - to read this adc - ad4000 -
>> http://www.analog.com/media/en/technical-documentation/data-
>> sheets/AD4000.pdf with a 500kHz sampling.
>> The only thing i changed, according to communicate with this adc, is that
>> i read 16 bits on the PRUADC.p and TIME_CLOCK is 1 (12.5Mhz for SPIclock).
>> I'm not an assembly expert, so i really can't figure out the problem.
>>
>> I tried read the this adc from the SPI0 of BBB(using Derek Molloy
>> exampels too http://exploringbeaglebone.com/chapter18/) , of course not
>> with a 500kHz sampling, just for test, but the problem is the same, i'm
>> working on this for more than 4 weeks, and i can't solve the problem, and
>> is not a hardware problem.
>>
>> In this examples, i have in the analog input of the adc, a square
>> wave(3.3 V), and 3 constantes voltages(680mV,1.8V,3.3V), all examples done
>> on PRU, and this are the results:
>> - Y axis -> Volts
>> - X axis -> Number of sample
>> - Vref of the adc is 4V.
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>>
>>
>> Any help would be aprecciated.
>>
>> Best Regards,
>> David
>>
>>
>>
>> --
> 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/i13Z9oe3EzM/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/b94014a1-7158-4dee-a304-edab41c21e4d%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/CANN_KV6sxtAWLfkEaWVgpJwmekZ4%2BZrPpNo9d_4pnLFn_eNpiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread Robert Nelson
On Wed, Feb 8, 2017 at 1:22 PM, Roman Prilutsky
 wrote:
> No. I am developing some software to run as a part of an automation project,
> so expect the board to be tolerant to the power loss. So i just pulled the
> pug out - no shutdown -h.
> What could break and what is a way to diagnose it?

"expect", well the board isn't designed for that application...

If your just going to yank power with the BBB, "expect" both software
and hardware failures*  (documented in the SRM)..

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


[beagleboard] Re: HELP! - I can't access my BBB any more.

2017-02-08 Thread Roman Prilutsky
No. I am developing some software to run as a part of an automation 
project, so expect the board to be tolerant to the power loss. So i just 
pulled the pug out - no shutdown -h. 
What could break and what is a way to diagnose it?



 

On Wednesday, February 8, 2017 at 7:34:08 AM UTC-5, Roman Prilutsky wrote:
>
> My BBB was running debian jessie and i could access it over USB  and 
> Ethernet. Then, after one power off/power on it stopped booting from eMMC. 
> To be exact I stoped been able too access it over both USB and Ethernet.  I 
> can still boot the board from SD and access the bard.  eMMC boot though 
> seems never finishes. I can see leds blinking in a normal boot sequence and 
> then they end up with one led blinking for ever. 
> If i boot from SD i can access eMMC file system (rootfs) and my 
> /etc/network/interface on eMMC looks normal. I do not know of any other way 
> to read a boot log on eMMC or anything to help me to understand the issue.
> Of course i could re-flash eMMC but then i will never know what happen :( 
> Any help/ideas are greatly 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/c1e88630-ebf7-427b-8943-564bd650bbf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Video image shifts right randomly

2017-02-08 Thread Brett
We've been running with the new bootloader for a few days and it seems like 
updating the bootloader did the trick! Thank you!

On Monday, February 6, 2017 at 2:19:43 PM UTC-7, RobertCNelson wrote:
>
> On Mon, Feb 6, 2017 at 3:09 PM, Brett  
> wrote: 
> > I am using 2014.01. Do we know what version this bug was introduced 
> with? 
>
> Well that bug has always been there, it was just fixed in v2017.01, 
> something worth to try. 
>
> 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/5f493471-6dde-4d4f-9294-9ed5f26d863a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: PRU SPI ADC communication

2017-02-08 Thread Graham
Hi David:

I think it is a hardware problem.

It looks like you are not doing a good job referencing your ground input 
for the ADC, or you have a very dirty Voltage reference for the ADC.

Either way, it is picking up some serious offset from a switching power 
supply (The PMMIC ???) somehow.

I think you need to do an audit of the power going to the Voltage reference 
for the ADC, and the connection of the positive and negative Voltage 
references, and the negative input on the ADC.

--- Graham

==



On Wednesday, February 8, 2017 at 6:34:37 AM UTC-6, davidvaran...@gmail.com 
wrote:
>
> Hi,
>
> I adapted the code from  Derek Molloy example - 
> http://exploringbeaglebone.com/chapter13/ - 
> https://github.com/derekmolloy/exploringBB/tree/master/chp13/adc - to 
> read this adc - ad4000 - 
> http://www.analog.com/media/en/technical-documentation/data-sheets/AD4000.pdf 
> with a 500kHz sampling.
> The only thing i changed, according to communicate with this adc, is that 
> i read 16 bits on the PRUADC.p and TIME_CLOCK is 1 (12.5Mhz for SPIclock). 
> I'm not an assembly expert, so i really can't figure out the problem.
>
> I tried read the this adc from the SPI0 of BBB(using Derek Molloy exampels 
> too http://exploringbeaglebone.com/chapter18/) , of course not with a 
> 500kHz sampling, just for test, but the problem is the same, i'm working on 
> this for more than 4 weeks, and i can't solve the problem, and is not a 
> hardware problem.
>
> In this examples, i have in the analog input of the adc, a square wave(3.3 
> V), and 3 constantes voltages(680mV,1.8V,3.3V), all examples done on PRU, 
> and this are the results:
> - Y axis -> Volts
> - X axis -> Number of sample
> - Vref of the adc is 4V.
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
>
> Any help would be aprecciated.
>
> Best Regards,
> David
>
>
>
>

-- 
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/b94014a1-7158-4dee-a304-edab41c21e4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] HELP! - I can't access my BBB any more.

2017-02-08 Thread evilwulfie
when you shutdown your bone did you just pull the plug or use the
shutdown now -h command then remove power ?



On 2/7/2017 8:57 PM, Roman Prilutsky wrote:
> My BBB was running debian jessie and i could access it over USB  and
> Ethernet. Then, after one power off/power on it stopped booting from
> eMMC. To be exact I stoped been able too access it over both USB and
> Ethernet.  I can still boot the board from SD and access the bard.
>  eMMC boot though seems never finishes. I can see leds blinking in a
> normal boot sequence and then they end up with one led blinking for
> ever. 
> If i boot from SD i can access eMMC file system (rootfs) and my
> /etc/network/interface on eMMC looks normal. I do not know of any
> other way to read a boot log on eMMC or anything to help me to
> understand the issue.
> Of course i could re-flash eMMC but then i will never know what happen
> :( Any help/ideas are greatly 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/062d34cc-7c92-44e3-a609-b27c9cf991a0%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/18842ec3-5e03-7c52-1098-764a245ba8a8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Desired existing open source cape recommendation

2017-02-08 Thread Jason Kridner
Is the Andice cape readily available already? Is it good for the UPS
function?
On Wed, Feb 8, 2017 at 9:26 AM Graham  wrote:

> I would like to support William's recommendation for a UPS type cape.
>
> Something that would allow the BBB to operate directly from ~11V to ~21V
> Instantly switch to an optional +12V battery if present, upon primary
> power loss.
> Recharge and float the optional +12V battery, if present, after any use.
> A couple of status outputs.
>
> Intended for use in server or remote applications of the BBB.
> Could also be used as a wide range power supply input without the optional
> UPS battery.
>
> --- Graham
>
> ==
>
>
> On Tuesday, February 7, 2017 at 2:17:55 PM UTC-6, William Hermans wrote:
>
> I'd recommend just about any decent UPS type cape with good power
> management features. e.g. Features that addressed the Beaglebone's
> inability to function remotely( well ).
>
> On Tue, Feb 7, 2017 at 1:00 PM, Jason Kridner  wrote:
>
> Anyone want to nominate an open source cape to go into production via a
> group buy?
>
> If I don't get suggestions, I'll recommend:
> http://elinux.org/BeagleBone_Black_RFID_Adaptor_Cape or
> https://github.com/cclark2/interacto_bbone_cape.
>
> --
> 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...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmCC1VDYUXogqwQRBMYqhAh7X5GjEP_2oswGFHTb6qnDg%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/491d838b-47a4-4adc-8ffd-fbbfb8ac239c%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/CA%2BT6QPmUc8qhi9suXQnWL0yUh9J2qoSYaqJed00Z5ejLmQh3zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Can not find module 'bonescript'

2017-02-08 Thread wbbenatti


Hi, 
I'm trying to run a simple script using the bonescript library on a 
BeagleBone with Linux Debian installed, and when I run in the Cloud9 IDE, 
it works fine. My script is called blinkled.js and when I try to run in 
line command, like "./blinkled.js", it is shown a long error message that 
starts with "Can not find module 'bonescript'".

How can I correct that?
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/04ec13ee-7d16-401f-9698-f3bfb74240b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Desired existing open source cape recommendation

2017-02-08 Thread Graham
I would like to support William's recommendation for a UPS type cape.

Something that would allow the BBB to operate directly from ~11V to ~21V
Instantly switch to an optional +12V battery if present, upon primary power 
loss.
Recharge and float the optional +12V battery, if present, after any use.
A couple of status outputs.

Intended for use in server or remote applications of the BBB.
Could also be used as a wide range power supply input without the optional 
UPS battery.

--- Graham

==

On Tuesday, February 7, 2017 at 2:17:55 PM UTC-6, William Hermans wrote:
>
> I'd recommend just about any decent UPS type cape with good power 
> management features. e.g. Features that addressed the Beaglebone's 
> inability to function remotely( well ).
>
> On Tue, Feb 7, 2017 at 1:00 PM, Jason Kridner  > wrote:
>
>> Anyone want to nominate an open source cape to go into production via a 
>> group buy?
>>
>> If I don't get suggestions, I'll recommend: 
>> http://elinux.org/BeagleBone_Black_RFID_Adaptor_Cape or 
>> https://github.com/cclark2/interacto_bbone_cape. 
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmCC1VDYUXogqwQRBMYqhAh7X5GjEP_2oswGFHTb6qnDg%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/491d838b-47a4-4adc-8ffd-fbbfb8ac239c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] PRU SPI ADC communication

2017-02-08 Thread davidvarandacaniceiro
Hi,

I adapted the code from  Derek Molloy example 
- http://exploringbeaglebone.com/chapter13/ 
- https://github.com/derekmolloy/exploringBB/tree/master/chp13/adc - to 
read this adc - ad4000 - 
http://www.analog.com/media/en/technical-documentation/data-sheets/AD4000.pdf 
with a 500kHz sampling.
The only thing i changed, according to communicate with this adc, is that i 
read 16 bits on the PRUADC.p and TIME_CLOCK is 1 (12.5Mhz for SPIclock). 
I'm not an assembly expert, so i really can't figure out the problem.

I tried read the this adc from the SPI0 of BBB(using Derek Molloy exampels 
too http://exploringbeaglebone.com/chapter18/) , of course not with a 
500kHz sampling, just for test, but the problem is the same, i'm working on 
this for more than 4 weeks, and i can't solve the problem, and is not a 
hardware problem.

In this examples, i have in the analog input of the adc, a square wave(3.3 
V), and 3 constantes voltages(680mV,1.8V,3.3V), all examples done on PRU, 
and this are the results:
- Y axis -> Volts
- X axis -> Number of sample
- Vref of the adc is 4V.











Any help would be aprecciated.

Best Regards,
David



-- 
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/a69a32ff-0e75-43d7-ba62-88dca26814e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Wifi direct on Beaglebone green

2017-02-08 Thread rnd
Hi, how can I enable wifi direct on a beagle bone green?
Thank you.

-- 
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/62a68d7c-c90f-40bb-afbd-105fc04cc2e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] HELP! - I can't access my BBB any more.

2017-02-08 Thread Roman Prilutsky
My BBB was running debian jessie and i could access it over USB  and 
Ethernet. Then, after one power off/power on it stopped booting from eMMC. 
To be exact I stoped been able too access it over both USB and Ethernet.  I 
can still boot the board from SD and access the bard.  eMMC boot though 
seems never finishes. I can see leds blinking in a normal boot sequence and 
then they end up with one led blinking for ever. 
If i boot from SD i can access eMMC file system (rootfs) and my 
/etc/network/interface on eMMC looks normal. I do not know of any other way 
to read a boot log on eMMC or anything to help me to understand the issue.
Of course i could re-flash eMMC but then i will never know what happen :( 
Any help/ideas are greatly 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/062d34cc-7c92-44e3-a609-b27c9cf991a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: UAV Drone out of a BBBW

2017-02-08 Thread 'woody stanford' via BeagleBoard
Ok here is what I have so far. I'm almost finished with the geodesic (I 
still want to "solvent weld" the joints though). Need to swap out the wire 
with picture-hanging wire and get the basswood "base board" to mount my 
electronics on. I'm going to do the motor mounts as aluminum plates that 
I'm going to Drexel fabricate. Looks like I'm going to have to go with the 
mast approach to get my mentioning right though it will make moving my 
boards around difficult.




On Monday, January 30, 2017 at 6:19:30 PM UTC-7, woody stanford wrote:

> I posted the remote control for this in Software, but I put a bunch of 
> hardware in it so I thought I'd post it here.
>
>
> https://groups.google.com/forum/#!category-topic/beagleboard/software/evSIUcuWfUY
>

-- 
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/25e6a968-182f-41d7-9c1a-814fd8d67443%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: Is there a web server on the BBB

2017-02-08 Thread 'woody stanford' via BeagleBoard
An accessable htdocs location that you can serve html files from that will 
pop out on the BBBW's (Rev C) is at:

/usr/share/bone101/Support

Now we don't want to corrupt the web server setup that comes stock with 
Angstrom, so make a directory in this directory. Call it htdocs or maybe 
your name. It will have a funny URL but you can access it, giving you the 
ability to quickly serve static web pages from your BBBW. As far as I can 
tell there is an apache2 httpd running somewhere that is listening to port 
80 on your BBBW and this is where it serves its web pages from (its 
structured a little funny, but still accessible). The URL would be:

http://192.158.7.2/bone101/support//.html

My next question is, is there existing a CGI-enabled directory similar to 
this that if I don't mind a funny URL that I can call some C programs from 
it. I just want to evaluate, and I'll do it the "right way" later.
 
Thoughts?
On Friday, February 3, 2017 at 10:52:36 PM UTC-7, woody stanford wrote:

> I notice something comes back on my port 80.
>
> Is there a real web sever serving that page thats coming back, and if so, 
> where is its htdocs directory (the filespec I mean)?
>

-- 
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/8d10921e-1348-494f-b67d-51fa71cfbfd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.