Re: [beagleboard] Re: Problem with 5V

[Graham Haddock]

Yes, try some other power supplies. and if they stay between 4.75 and 5.25
under all the different load conditions a BBB can create, it will work fine.

USB power is highly variable from computer to computer.  Sometimes it works
fine, sometimes it does not.
USB-1 was 0.5 Amps max, not enough to run a BBB, while booting or updating
the eMMC.
USB-2 is 0.9 Amps, about enough to handle the peak current from a BBB.
The Voltage limits for USB are 4.5 to 5.5 Volts. No margin if at the limits
under full load.

--- Graham

==



On Wed, Nov 8, 2017 at 12:35 PM,  wrote:

> thanks for the answer. i think i need to find other power and test with
> that. If that new one stays 4.75 - 5.25 it will working normally then?
> how about that, im thinking to run it with USB power via USB connector. is
> it ok?
>
>

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

[beagleboard] Re: SPI0 Overlay for Debian 3.8.13

[Kenny Koller]

For posterity (or extry posterity since this is for 3.8.13):

bone_capemgr should have been capemgr. A working uEnv.txt:

uname_r=3.8.13-bone62

optargs=quiet drm.debug=7

cape_enable=capemgr.enable_partno=BB-SPIDEV0

cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

Next use compatible device tree source.

Clone g...@github.com:beagleboard/linux.git and checkout tag 3.8.13-bone62.

$ find . -name "*.dts" | grep SPI
./firmware/capes/BB-SPIDEV0-00A0.dts
./firmware/capes/BB-SPIDEV1-00A0.dts
./firmware/capes/BB-SPIDEV1A1-00A0.dts

Compile:

$ dtc -W no-unit_address_vs_reg -O dtb -o BB-SPIDEV0-00A0.dtbo -b 0 -@ BB-
SPIDEV0-00A0.dts
$ dtc --version
Version: DTC 1.4.5 

Place the .dtbo in /lib/firmware. Reboot. The SPI loopback test works:

./spidev_test -D /dev/spidev1.1
spi mode: 0
bits per word: 8
max speed: 50 Hz (500 KHz)

FF FF FF FF FF FF 
40 00 00 00 00 95 
FF FF FF FF FF FF 
FF FF FF FF FF FF 
FF FF FF FF FF FF 
DE AD BE EF BA AD 
F0 0D 


I found a DTS file that was included as part of an example of the use of 
> the ADAFruit Python library. I compiled it and placed in /lib/firmware:
>
> $ ls /lib/firmware
> 3.8.13-bone62  ADA-SPI0-01-00A0.dtbo  BB-SPI0-01-00A0.dtbo
>
> I attempt to enable this overlay in uEnv.txt.
>
> uname_r=3.8.13-bone62
> optargs=quiet drm.debug=7
> cape_enable=bone_capemgr.enable_partno=ADA-SPI0-01
>
> I can see that it is passed to the kernel.
>
> $ cat /proc/cmdline
> console=tty0 console=ttyO0,115200n8 quiet drm.debug=7 bone_capemgr.
> enable_partno=ADA-SPI0-01 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
>
> However the device nodes are not created and I do not see the overlay 
> listed.
>  
> $ cat /sys/devices/bone_capemgr.*/slots
>  0: 54:PF--- 
>  1: 55:PF--- 
>  2: 56:PF--- 
>  3: 57:PF--- 
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART4
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
>
> dmesg information:
>
> [0.552308] bone-capemgr bone_capemgr.9: Baseboard: 
> 'A335BNLT,00C0,0816BBBK0B26'
> [0.552332] bone-capemgr bone_capemgr.9: compatible-baseboard=ti,
> beaglebone-black
> [0.583227] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [0.620334] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [0.657443] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [0.694551] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [0.700772] bone-capemgr bone_capemgr.9: slot #4: specific override
> [0.700795] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 4
> [0.700811] bone-capemgr bone_capemgr.9: slot #4: 
> 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
> [0.700893] bone-capemgr bone_capemgr.9: slot #5: specific override
> [0.700911] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 5
> [0.700925] bone-capemgr bone_capemgr.9: slot #5: 
> 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
> [0.700994] bone-capemgr bone_capemgr.9: slot #6: specific override
> [0.701011] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 6
> [0.701025] bone-capemgr bone_capemgr.9: slot #6: 
> 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
> [0.701356] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-
> EMMC-2G:00A0 (prio 1)
> [0.701371] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-
> EMMC-2G:00A0 (prio 1)
> [0.701446] bone-capemgr bone_capemgr.9: loader: before slot-5 BB-
> BONELT-HDMI:00A0 (prio 1)
> [0.701459] bone-capemgr bone_capemgr.9: loader: check slot-5 BB-BONELT
> -HDMI:00A0 (prio 1)
> [0.701494] bone-capemgr bone_capemgr.9: initialized OK.
> [0.701950] bone-capemgr bone_capemgr.9: loader: after slot-4 BB-BONE-
> EMMC-2G:00A0 (prio 1)
> [0.701974] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 
> 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
> [0.701999] bone-capemgr bone_capemgr.9: slot #4: dtbo 
> 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
> [0.702186] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
> [0.702778] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
> [0.702796] bone-capemgr bone_capemgr.9: loader: done slot-4 BB-BONE-
> EMMC-2G:00A0 (prio 1)
> [0.704413] bone-capemgr bone_capemgr.9: loader: after slot-5 BB-BONELT
> -HDMI:00A0 (prio 1)
> [0.704439] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware 
> 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version 
> '00A0'
> [0.704468] bone-capemgr bone_capemgr.9: slot #5: dtbo 
> 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
> [0.705075] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
> [0.709778] bone-capemgr bone_capemgr.9: slot #5: Applied #4 overlays.
> [0.709795] 

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[Riko]

Dear BeagleBoard Member,


I got this message :

usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 6 using musb-hdrc
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 7 using musb-hdrc
usb 1-1: device not accepting address 7, error -110
usb 1-1: new high-speed USB device number 8 using musb-hdrc
usb 1-1: device not accepting address 8, error -110
usb usb1-port1: unable to enumerate USB device
usb usb1-port1: over-current condition


I'm using 4 ports USB Hub, does it matter ?

Regards,


On 23/10/17 12:39, Robert Nelson wrote:



On Oct 22, 2017 10:52 PM, "Riko" > wrote:


It's working until root shell but, always miss USB drive
initialization.

I got no idea why, looks like there's a voltage drop.

Is it ok, if I remove FB8 from the board ? It's connected to T18
on the chip

Probably not.

Which board?

Regards,


--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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/f20265d4-2155-f3a7-6180-52d73e503cf4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black availability

[Graham]

It looks like Digikey is out of stock, but Mouser has 1300+ on the shelf.

Mouser Part #:  958-BBB01-SC-505
Manufacturer Part #:BBB01-SC-505
Manufacturer:   BeagleBoard by GHI
Description:Single Board Computers Beaglebone Black
In Stock
1:  $55.00

==

-- 
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/10b0400c-48f8-4a27-9f11-c4af8ce91cd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[sami kamal]

YouTube videos of



 U.S. Congress money laundering hearing


of

Saudi Billionaire  " Maan  Al sanea"

 with *bank of America*


and  The  owner of Saad Hospital and  Schools

 in the Eastern Province in *Saudi Arabia*



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


With Arabic Subtitles





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

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



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



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



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



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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAH%3DZeA5vTJyJcXA%2BkhnyPyOpr9m-B%2BM2KrKofMdiRSHnC9BcTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Weird behaviour with pins and PRUs

[Loïc Droz]

Hello,

I am a beginner in PRU and embedded programming in general so I apologize 
if I am missing something obvious.

I am trying to implement an audio processing algorithm (CIC filter) to run 
on the PRUs. To do so, I need to generate a CLK signal for the microphone, 
which I generate on PRU0, output from PRU0 to pin P8.11 and I then connect 
the mic's CLK pin to this pin directly. However, I also need to be able to 
read the CLK signal from PRU1, so I figured I would plug the CLK signal 
generated by PRU0 to pin P8.46 which I then poll from PRU1.

Doing this gives strange results though. As soon as I connect P8.11 (output 
CLK) to P8.46 (input CLK), the CLK signal from P8.11 gets stuck at Vdd. If 
I unplug it it will remain stuck at Vdd. Even restarting both programs (the 
clock generating one on PRU0 and the audio processing one on PRU1) does not 
fix the issue. Only restarting the Beaglebone does. I checked the voltage 
of P8.46 and it is always at 0.

I tried running only the PRU0 CLK program and the issue does not happen, it 
looks like the PRU1 program causes some issues.

Here is the code for the PRU0 CLK program :




/* Code for the clock generated by PRU0 and sent to the microphone. */
.origin 0
.entrypoint TOP

#include "prudefs.hasm"

#define CYCLES 39
#define CLK_PIN r30.b1

TOP:
MOV r0, CYCLES
_LOOP:
SUB r0, r0, 1
QBNE_LOOP, r0, 0

// Toggle CLK signal
XOR CLK_PIN, CLK_PIN, 1 << 7
QBA TOP




And here is the code for the PRU1 audio program (sorry it's a little long) :




#define PRU1_ARM_INTERRUPT 20

// Input pins offsets
#define CLK_OFFSET 1
#define DATA_OFFSET 0

// Register aliases
#define IN_PINS r31
#define SAMPLE_COUNTER r5
#define WAIT_COUNTER r6
#define TMP_REG r7
#define BYTE_COUNTER r8

#define HOST_MEM r20
// Host mem size is multiple of 8, this is ensured on the host side
#define HOST_MEM_SIZE r21
#define LOCAL_MEM r22
// Defined in page 19 of the AM335x PRU-ICSS Reference guide
#define LOCAL_MEM_ADDR 0x2000

#define INT0 r0
#define INT1 r1
#define INT2 r2
#define INT3 r3
#define LAST_INT r4

#define COMB0 r10
#define COMB1 r11
#define COMB2 r12
//#define COMB3 r13
#define LAST_COMB0 r14
#define LAST_COMB1 r15
#define LAST_COMB2 r16

// DEBUG (assumes pin P8.44)
#define SET_LED SET r30, r30, 3
#define CLR_LED CLR r30, r30, 3

.origin 0
.entrypoint TOP

TOP:
//MOV r31.b0, PRU1_ARM_INTERRUPT + 16
SET_LED
// ### Memory management ###
// Enable OCP master ports in SYSCFG register
// It is okay to use the r0 register here (which we use later too) 
because it merely serves as a mean to temporary hold the value of C4 + 4, 
the OCP masters are enabled by writing the correct data to C4
LBCOr0, C4, 4, 4
CLR r0, r0, 4
SBCOr0, C4, 4, 4
// Load the local memory address in a register
MOV LOCAL_MEM, LOCAL_MEM_ADDR
// From local memory, grab the address of the host memory (passed by 
the host before this program started)
LBBOHOST_MEM, LOCAL_MEM, 0, 4
// Likewise, grab the host memory length
LBBOHOST_MEM_SIZE, LOCAL_MEM, 4, 4

// ### Set up start configuration ###
// Setup counters to 0 at first
LDI SAMPLE_COUNTER, 0
LDI BYTE_COUNTER, 0
// Set all integrator and comb registers to 0 at first
LDI INT0, 0
LDI INT1, 0
LDI INT2, 0
LDI INT3, 0
LDI COMB0, 0
LDI COMB1, 0
LDI COMB2, 0
//LDI COMB3, 0
LDI LAST_INT, 0
LDI LAST_COMB0, 0
LDI LAST_COMB1, 0
LDI LAST_COMB2, 0

// ### Signal processing ###
wait_edge:
// First wait for CLK = 0
WBC IN_PINS, CLK_OFFSET
// Then wait for CLK = 1
WBS IN_PINS, CLK_OFFSET

// Wait for t_dv time, since it can be at most 125ns, we have to wait 
for 25 cycles
LDI WAIT_COUNTER, 12 // Because 25 = 1 + 12*2 and the loop takes 2 
one-cycle ops
wait_signal:
SUB WAIT_COUNTER, WAIT_COUNTER, 1
QBNEwait_signal, WAIT_COUNTER, 0

// Retrieve data from DATA pin (only one bit!)
AND TMP_REG, IN_PINS, 1 << DATA_OFFSET
LSR TMP_REG, TMP_REG, DATA_OFFSET
// Do the integrator operations
ADD SAMPLE_COUNTER, SAMPLE_COUNTER, 1
ADD INT0, INT0, TMP_REG
ADD INT1, INT1, INT0
ADD INT2, INT2, INT1
ADD INT3, INT3, INT2

// Branch for oversampling
QBNEwait_edge, SAMPLE_COUNTER, 64

// Reset sample counter once we reach R
LDI SAMPLE_COUNTER, 0

// 4 stage comb filter
SUB COMB0, INT3, LAST_INT
SUB COMB1, COMB0, LAST_COMB0
SUB COMB2, COMB1, LAST_COMB1
SUB TMP_REG, COMB2, LAST_COMB2

// Output the result to memory
// We write one word (4 B) from TMP_REG to HOST_MEM with an offset of 
BYTE_COUNTER
SBBOTMP_REG, HOST_MEM, BYTE_COUNTER, 4
// Increment the written bytes counter once the write operation is done
ADD BYTE_COUNTER, BYTE_COUNTER, 4
// First, 

Re: [beagleboard] After /opt/scripts update usb network is not working

[Robert Nelson]

On Wed, Nov 8, 2017 at 12:18 PM, Grzegorz G  wrote:
> Ethernet is working now... I don't know why before link goes down. I can't
> repeat this behaviour.
>
> I have udev rule:
> SUBSYSTEM=="rtc", KERNEL=="rtc1", SYMLINK+="rtc",
> OPTIONS+="link_priority=10", TAG+="systemd"
>
> when it is commented rtc problem remain.

this udev rule in un-reiable.. i fixed this in v4.4.x via, u-boot
overlays and a rtc cape overlay with the "alisas":

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-RTC-01-00A0.dts#L32-L40

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

Re: [beagleboard] After /opt/scripts update usb network is not working

[Grzegorz G]

Ethernet is working now... I don't know why before link goes down. I can't 
repeat this behaviour.

I have udev rule:
SUBSYSTEM=="rtc", KERNEL=="rtc1", SYMLINK+="rtc", 
OPTIONS+="link_priority=10", TAG+="systemd"

when it is commented rtc problem remain.

W dniu środa, 8 listopada 2017 17:24:52 UTC+1 użytkownik Grzegorz G napisał:
>
> I did it. It took 1.5h on my debian virtual machine.
> Results:
> - usb network i not available (still no route in route print),
> + serial over usb is working (it was not available before),
> - in device management there is working com port "USB serial  device COM8" 
> (mentioned above) and there is visible "Gadget serial COM7" defined not 
> exsisted device,
> - big problems with RTC over I2C - almost not readable (before kernel 
> upgrade, there was not as many problems with RTC over i2c),
> - old problem with ethernet is back
>
> [  158.682964] rtc-ds1307 1-0068: read error -121
> [  160.284608] rtc-ds1307 1-0068: read error -121
> [  201.901327] cpsw 4a10.ethernet eth0: Link is Down
>
> [  402.656641] rtc-ds1307 1-0068: read error -110
> [  404.291265] rtc-ds1307 1-0068: read error -121
> [  407.762364] rtc-ds1307 1-0068: read error -121
> [  408.601046] rtc-ds1307 1-0068: read error -121
> [  411.371277] omap_i2c 4802a000.i2c: controller timed out
> [  411.376635] rtc-ds1307 1-0068: read error -110
> [  413.062533] rtc-ds1307 1-0068: read error -121
> [  413.983043] rtc-ds1307 1-0068: read error -121
>
> I didn't make any changes to kernel configuration (I did save, then exit).
>
> PS. My OS is Windows 10 Fall Creators Update.
>
> Did I miss something while compiling kernel?
>
> W dniu poniedziałek, 6 listopada 2017 19:07:13 UTC+1 użytkownik 
> RobertCNelson napisał:
>>
>> On Mon, Nov 6, 2017 at 11:34 AM, Grzegorz G  wrote: 
>> > Thank you very much :) 
>> > Now latest is 4.4.71-bone17 (via ./update_kernel.sh --bone-kernel 
>> --lts-4_4) 
>>
>> Ouch, yeah i stopped doing wheezy (7.x) builds when stretch (9.x) hit 
>> stable.. 
>>
>> > Will 4.4.96-bone20 be available tomorrow or I need to change update 
>> > parameters? 
>>
>> voodoo@hades:~$ git clone -b am33x-v4.4 
>> https://github.com/RobertCNelson/bb-kernel/ --depth=1 
>> voodoo@hades:~$ cd bb-kernel/ 
>> voodoo@hades:~/bb-kernel$ ./build_deb.sh 
>>
>> Then copy the ./deploy/linux-image*.deb to your beagle and run: 
>>
>> sudo dpkg -i linux-image*.deb 
>> sudo reboot 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2c96557d-4e51-40ee-a022-039f73910bf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Best way for events between PRU and processor?

[TJF]

Hi Ken Shirriff!

Here's what I do in the libpruio project:

I don't use interrupts and I don't stop the PRU main loop (no 
prussdrv_pru_wait_event() and prussdrv_pru_clear_event()).

Instead the PRU main loop is running continually and I use a certain area 
in the DRam to exchange status information.

Before the ARM sends a new command, it has to wait until the PRU is ready 
(max. 10 to 15 PRU cycles).

And when the PRU has data for the ARM part, it stores the data in a ring 
buffer and tells the ARM the current ring buffer position.

I'm not keen on ethernet issues, but I think a similar concept should work 
for you as well. Use a FIFO buffer for outgoing data and a ring buffer for 
incomming. Before the ARM can send the next package, it has to wait until 
the current one is done. (When this limitation is insufficient, you'll have 
to use a ring buffer for outgoing data as well.)

BR

-- 
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/1870abc3-64aa-4b07-aeef-57f58e1f4602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black availability

[Robert Nelson]

On Wed, Nov 8, 2017 at 7:26 AM,   wrote:
> Hi,
>
> during last month I noticed the availability of the BBB is not as good as it
> has been before. Farnell/element14 has more and more increasing lead times,
> currently their stock is empty and they expect next batch earliest in more
> than one month. Circuitco itself does not seem to produce any BBBs.

CircuitCo is dead..

>
> So: is this board going to die? Is it discontinued because of all these
> strange clones which are out there meanwhile (BBB Wireless, BBB Industrial,
> ...)?

Both GHI and Embest manufacture all the boards..

Looks like a board shortage...

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

Re: [beagleboard] Beagle Pocket and Cortex-M3 core

[Robert Nelson]

On Wed, Nov 8, 2017 at 5:32 AM,   wrote:
>
> Hello,
>
> Just discovered the Beagle Pocket board features. One of them on the web
> page of the board really attracted me on and it was the M3 core. But if a
> take a look at the datasheet of the manufacturer there is no mention of this
> core. Only cortex-A8 is shown.
>
> So I am confused. Anyone could clarify this ?

It's main use is control of power management of the A8.

It's in the big datasheet..

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

Re: [beagleboard] PWM Problems with BeagleBone Black Debian 8.4 Kernel 4.4

[Robert Nelson]

On Wed, Nov 8, 2017 at 5:23 AM,   wrote:
> Hello Samuel
>
> I too faced came issues in 4.4 and managed to get PWM working.
>
> Now, I need to implement this in C++. The pwmchipX number keeps on changing
> for my desired PWM channel.
>
> Could you please suggest me a way to overcome this?

Easy:

don't use /sys/pwm/pwmchipX, instead use the /sys/devices directory:

/sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip*/

and ignore the "X"...

https://github.com/beagleboard/pocketbeagle/wiki/Peripherals

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/CAOCHtYjyeg16%3D_dK7Nkh2-R2gOEgE4x-hzEEzKT4i7FZW%2BPszw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Best way for events between PRU and processor?

[TJF]

Am Dienstag, 7. November 2017 18:42:58 UTC+1 schrieb din...@gmail.com:
>
> Hi,
>
> FYI, recent remoteproc RPMSG versions have moved from mailboxes to 
> interrupts for communication: 
> https://git.ti.com/pru-software-support-package/pru-software-support-package/commit/69805828df0f262fb60363c2db189d1b8d0b693c0
>  
> 
>

This is a small step in the right direction. When they're finally finishing 
their way, they'll end up where the prussdrv concept started. 

-- 
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/7ddcb272-d791-4f00-8eeb-2931038b3987%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PWM Problems with BeagleBone Black Debian 8.4 Kernel 4.4

[chiragpooniwala]

Hello Samuel

I too faced came issues in 4.4 and managed to get PWM working.

Now, I need to implement this in C++. The pwmchipX number keeps on changing 
for my desired PWM channel.

Could you please suggest me a way to overcome this?

-- 
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/8f8fef20-862a-4297-8251-8c8aea6d1d93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BeagleBone Black availability

[mike . maikaefer]

Hi,

during last month I noticed the availability of the BBB is not as good as 
it has been before. Farnell/element14 has more and more increasing lead 
times, currently their stock is empty and they expect next batch earliest 
in more than one month. Circuitco itself does not seem to produce any BBBs.

So: is this board going to die? Is it discontinued because of all these 
strange clones which are out there meanwhile (BBB Wireless, BBB Industrial, 
...)?

Thanks

Mike


-- 
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/698a2fc5-ee60-4c0b-b573-5e0ec2487225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone X15?

[mike . maikaefer]

I second that. Any plans for an upgraded BBB which provides more computing 
power while being compatible to the current hardware interfaces?

On Thursday, November 10, 2016 at 2:09:05 PM UTC+1, Paul Plankton wrote:
>
> No, it is not a typo: but how about a BeagleBone with this new, dual-core 
> processor?
>
> I know, die to it's size it never could have that much peripherals like 
> the BeagleBoard X15, but having the current interfaces plus this processor 
> should not only bring more computing power but also a better price 
> (comparing to BeagleBoard X15).
>
> Just as an idea...
>
>

-- 
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/d4ea4b9c-8bc5-4401-a709-1d6c2e867e8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Problems with BBB USB serial communication and Windows 10

[mike . maikaefer]

This is a bug in Windows 10. There are a lot of similar complaints in MSDN 
forums. The bad news: only complaints, the bug never has been fixed by MS.


On Monday, May 29, 2017 at 8:07:45 AM UTC+2, Satz Klauer wrote:
>
> Hi,
>
>
> I'm running a StarterWare 2 based application on an BBB which makes use of 
> a USB serial interface implementation based on the StarterWare example and 
> by using a .inf-File which is similar to "usb_dev_serial.inf" which was 
> provided by TI in same StarterWare package. Of course VID and PID have been 
> changed according to my own USB serial interface implementation.
>
>
> This works well with all Windows-versions up to 7 (8.x was never tested) 
> and also with all Linux variants. But now with Windows 10 there is a 
> problem which was reported by different users of this application:
>
>- opening of the serial interface often fails, simple repeating of the 
>procedure then is successful latest after 10 tries
>- sometimes an already opened connection seem to be corrupted, means 
>there is no more communication possible, host application needs to be 
>closed, device needs to be restarted - but after this, the same COM-port 
> is 
>available again, Windows does not change numbering
>
> So: is anything known about such problems in Windows 10 ? Perhaps are 
> there any changes necessary in an INF-file or in USB serial interface code 
> to make it work with Windows 10? Is there anything similar known from the 
> Linux Kernel of the BBB?
>
>
> Any hint or idea is welcome!
>
>
>
>

-- 
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/c4db0882-0837-4058-8f52-07fe6a9703f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] After /opt/scripts update usb network is not working

[Grzegorz G]

I did it. It took 1.5h on my debian virtual machine.
Results:
- usb network i not available (still no route in route print),
+ serial over usb is working (it was not available before),
- in device management there is working com port "USB serial  device COM8" 
(mentioned above) and there is visible "Gadget serial COM7" defined not 
exsisted device,
- big problems with RTC over I2C - almost not readable (before kernel 
upgrade, there was not as many problems with RTC over i2c),
- old problem with ethernet is back

[  158.682964] rtc-ds1307 1-0068: read error -121
[  160.284608] rtc-ds1307 1-0068: read error -121
[  201.901327] cpsw 4a10.ethernet eth0: Link is Down

[  402.656641] rtc-ds1307 1-0068: read error -110
[  404.291265] rtc-ds1307 1-0068: read error -121
[  407.762364] rtc-ds1307 1-0068: read error -121
[  408.601046] rtc-ds1307 1-0068: read error -121
[  411.371277] omap_i2c 4802a000.i2c: controller timed out
[  411.376635] rtc-ds1307 1-0068: read error -110
[  413.062533] rtc-ds1307 1-0068: read error -121
[  413.983043] rtc-ds1307 1-0068: read error -121

I didn't make any changes to kernel configuration (I did save, then exit).

PS. My OS is Windows 10 Fall Creators Update.

Did I miss something while compiling kernel?

W dniu poniedziałek, 6 listopada 2017 19:07:13 UTC+1 użytkownik 
RobertCNelson napisał:
>
> On Mon, Nov 6, 2017 at 11:34 AM, Grzegorz G  > wrote: 
> > Thank you very much :) 
> > Now latest is 4.4.71-bone17 (via ./update_kernel.sh --bone-kernel 
> --lts-4_4) 
>
> Ouch, yeah i stopped doing wheezy (7.x) builds when stretch (9.x) hit 
> stable.. 
>
> > Will 4.4.96-bone20 be available tomorrow or I need to change update 
> > parameters? 
>
> voodoo@hades:~$ git clone -b am33x-v4.4 
> https://github.com/RobertCNelson/bb-kernel/ --depth=1 
> voodoo@hades:~$ cd bb-kernel/ 
> voodoo@hades:~/bb-kernel$ ./build_deb.sh 
>
> Then copy the ./deploy/linux-image*.deb to your beagle and run: 
>
> sudo dpkg -i linux-image*.deb 
> sudo reboot 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b9f307e0-822d-460a-9323-26d5a8c0be3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Nont able to use overlay at boot time

[Robert Nelson]

On Wed, Nov 8, 2017 at 12:06 AM, Mrigendra Chaubey
 wrote:
> Thanks for the clarification.
>
> One suggestion I need.
> What is the best way to keep up with these changes, because these
> information is so volatile that it may be redundant in few weeks.
> Should I go with the source of overlay files and understand from the
> implementation point of view rather than trying to just make it work
> somehow.
> Which source files or functions would be best to start?
> I just need a direction from where I can start.

Well the decision was made back in March of 2017 to completely scrap
kernel overlays and move to u-boot overlays.

An announcement was made to this mailing list.

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

Re: [beagleboard] BBB powering up problem

[Robert Nelson]

On Wed, Nov 8, 2017 at 8:18 AM,   wrote:
> I got a problem. When i connect 5V PSU only pwr flashes 1 time. And If i use 
> only USB host Port with USB cable, BBB Works normally. Are there sonething 
> broken or what?


https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/beagleboard/n0dbCn2RsG8/e9MJzEoFAQAJ

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

[beagleboard] BBB powering up problem

[pahviaivo]

I got a problem. When i connect 5V PSU only pwr flashes 1 time. And If i use 
only USB host Port with USB cable, BBB Works normally. Are there sonething 
broken or 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/54f6ef9c-171f-4aea-9640-7ab6362a510a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.