Re: [beagleboard] Tips on using a BBGW in a consumer product

[woody.lois via BeagleBoard]

On Tue, 2/21/17, Gerald Coley  wrote:

 Subject: Re: [beagleboard] Tips on using a BBGW in a consumer product
 To: "beagleboard@googlegroups.com" 
 Cc: "Jason Kridner" 
 Date: Tuesday, February 21, 2017, 11:08 PM
 
 It arrived
 in the group posting.
 Gerald
 
 On Tue, Feb 21, 2017 at
 2:32 PM, Steve Groen 
 wrote:
 Jason
 Kridner, Generally:
 How do you incorporate a BBGW into a consumer
 product?
 Does anybody do this, or do they design their own
 board
 using BBGW as a base? Reset/Upgrade:
 How does a customer 'factory reset' a bricked
 BBGW?  Swap
 out the SD card?  Provide an externally accessible
 slot
 for the SD card, or allow customer to open and
 replace
 the card?  RMA? 
 How are field upgrades handled?  Replace SD card?  Over
 the
 air upgrade procedure?  Connect via serial port? 
 RMA?  Jason, did I Cc this
 message properly as you requested?  If so where do I go
 to see this posting?
 
 
 
 
 
 -- 
 
 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+unsubscribe@
 googlegroups.com.
 
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/beagleboard/ 000b01d28c81%24a7a2f470%
 24f6e8dd50%24%40mchsi.com.
 
 For more options, visit https://groups.google.com/d/
 optout.
 
 
 
 
 -- 
 Gerald
  
 ger...@beagleboard.org
 http://beagleboard.org/gcol...@emprodesign.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/CAHK_S%2BdZn1AEeNt6abe%3DiR9mL0G5fY6e5zMgwceOkhy8%3D9UNmQ%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
 8 oct. - Proclamarea statului cehoslovac. 30 oct. - Turcia semneaza 
armistitiul de la Mudros. 3 nov. - Austria semneaza armistitiul de la 
Villa-Giusti. Polonia isi proclama independenta. 11 nov. - Germania semneaza 
armistitiul de la Retondes. 16 nov. - Proclamarea Republicii Ungare. 28 nov. - 
Kaiserul Wilhelm al II abdica si se refugiaza in Olanda.

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

[beagleboard] Re: bb-wl18xx-firmware depends on connman!?

[Juliusz Chroboczek]

> This is the change i implemented..

> https://github.com/rcn-ee/repos/commit/cc43ffb0374efb0e219863621927f5bc29b12212

Perfect, thanks.

-- Juliusz

-- 
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/8760k39i3e.fsf%40trurl.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Tips on using a BBGW in a consumer product

[Gerald Coley]

It arrived in the group posting.

Gerald


On Tue, Feb 21, 2017 at 2:32 PM, Steve Groen  wrote:

> Jason Kridner,
>
>
>
> Generally:
>
>  How do you incorporate a BBGW into a consumer product?
>
>  Does anybody do this, or do they design their own board
>
>  using BBGW as a base?
>
>
>
> Reset/Upgrade:
>
>  How does a customer 'factory reset' a bricked BBGW?  Swap
>
>  out the SD card?  Provide an externally accessible slot
>
>  for the SD card, or allow customer to open and replace
>
>  the card?  RMA?
>
>
>
>  How are field upgrades handled?  Replace SD card?  Over the
>
>  air upgrade procedure?  Connect via serial port?  RMA?
>
>
>
>
>
> Jason, did I Cc this message properly as you requested?  If so where do I
> go
> to see this posting?
>
> --
> 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/000b01d28c81%24a7a2f470%24f6e8dd50%24%40mchsi.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BdZn1AEeNt6abe%3DiR9mL0G5fY6e5zMgwceOkhy8%3D9UNmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Tips on using a BBGW in a consumer product

[Steve Groen]

Jason Kridner,

 

Generally:

 How do you incorporate a BBGW into a consumer product?

 Does anybody do this, or do they design their own board

 using BBGW as a base?

 

Reset/Upgrade:

 How does a customer 'factory reset' a bricked BBGW?  Swap

 out the SD card?  Provide an externally accessible slot

 for the SD card, or allow customer to open and replace

 the card?  RMA?

 

 How are field upgrades handled?  Replace SD card?  Over the

 air upgrade procedure?  Connect via serial port?  RMA?

 

 

Jason, did I Cc this message properly as you requested?  If so where do I go
to see this posting?



-- 
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/000b01d28c81%24a7a2f470%24f6e8dd50%24%40mchsi.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW testing

[Kevin Gordon]

Progress:
The error I struck using grow_partition.sh was: 

Re-reading the partition table ... 
sfdisk: BLKRRPART: Device or resource busy 
sfdisk: The command to re-read the partition table failed. 
Run partprobe(8), kpartx(8) or reboot your system now, 
before using mkfs 
sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use 
dd(1) 
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1 
(See fdisk(8).) 

I rebooted and ran: 

root@beaglebone:/opt/scripts/tools# ./version.sh 
git:*/opt/scripts/*:[e066cb50c5eda24ce09227b1a155da823d56225a] 
eeprom:[A335BNLTBWA51646BBWG0358] 
dogtag:[BeagleBoard.org Debian Image 2017-02-12] 
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-3-ga09f2d] 
bootloader:[/dev/mmcblk1]:[U-Boot 2016.11-rc3-2-g73df7f] 
kernel:[4.4.48-ti-r88] 
nodejs:[v4.7.3] 
root@beaglebone:/opt/scripts/tools# df 
Filesystem 1K-blocksUsed Available Use% Mounted on 
udev   10240   0 10240   0% /dev 
tmpfs  999563036 96920   4% /run 
/dev/mmcblk0p1   7376168 2934944   4090164  42% / 
tmpfs 249884   4249880   1% /dev/shm 
tmpfs   5120   4  5116   1% /run/lock 
tmpfs 249884   0249884   0% /sys/fs/cgroup 
tmpfs  49980   0 49980   0% /run/user/1000 

root@beaglebone:/opt/scripts/tools# fdisk -l /dev/mmcblk0 

Disk /dev/mmcblk0: 7.2 GiB, 7744782336 bytes, 15126528 sectors 
Units: sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 512 bytes 
I/O size (minimum/optimal): 512 bytes / 512 bytes 
Disklabel type: dos 
Disk identifier: 0xc9171f1a 

Device Boot Start  End  Sectors  Size Id Type 
/dev/mmcblk0p1 * 8192 15126527 15118336  7.2G 83 Linux 

I HAVE NOT RUN mkfs. 

So there is only one partition BUT it starts at 8192 sectors. Is there 
absolutely nothing pior to 8192 sectors? Is there a MRB in the first 512 
bytes? If I used dd in linux must I allow for that? Why so many sectors 
(8192)? 

The version is: bootloader:[/dev/mmcblk0]:[U-Boot 
2017.03-rc1-3-ga09f2d] Is U-Boot 2017.03-rc1-3 sufficiently up to 
date? 

This is how my slots are at present: 

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01 

1: PF -1 

2: PF -1 

3: PF -1 

In /boot/uEnv.txt I uncommented: enable_uboot_overlays=1 and 
disable_uboot_overlay_video=1 

Moved /uEnv.txt to /uEnv.txt.old 

I shutdown the BBBW and it actually shutdown not rebooted After so long 
faulty? 

After restart checked slots which was the same as above. 

In /boot/uEnv.txt I uncommented:disable_uboot_overlay_audio=1 

In /boot/uEnv.txtadded 
cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-I2C1,BB-UART4 

I shutdown the BBBW but it rebooted. 

New slots: 

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01 

1: PF -1 

2: PF -1 

3: PF -1 

4: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART1 

5: P-O-L- 2 Override Board Name,00A0,Override Manuf,BB-I2C1 

6: P-O-L- 3 Override Board Name,00A0,Override Manuf,BB-UART4 

I tried adding BB-ADC with no effect. BB-BONE-LCD7-01 uses some of AIN 
pins. AIN0 to AIN3? Not sure. 

root@beaglebone:/home/debian# cd /sys/bus/iio/devices/iio:device0 
root@beaglebone:/sys/bus/iio/devices/iio:device0# ls -al 
total 0 
drwxr-xr-x 5 root root0 Feb 20 23:41 . 
drwxr-xr-x 4 root root0 Feb 20 23:41 .. 
drwxr-xr-x 2 root root0 Feb 21 03:49 buffer 
-r--r--r-- 1 root root 4096 Feb 21 03:49 dev 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage4_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage5_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage6_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage7_raw 
-r--r--r-- 1 root root 4096 Feb 21 03:49 name 
lrwxrwxrwx 1 root root0 Feb 21 03:49 of_node -> 
../../../../../../firmware/devicetree/base/ocp/tscadc@44e0d000/adc 
drwxr-xr-x 2 root root0 Feb 21 03:49 power 
drwxr-xr-x 2 root root0 Feb 21 03:49 scan_elements 
lrwxrwxrwx 1 root root0 Feb 21 03:49 subsystem -> 
../../../../../../bus/iio 
-rw-r--r-- 1 root root 4096 Feb 20 23:41 uevent 
root@beaglebone:/sys/bus/iio/devices/iio:device0# 

I guess from the above I can use AIN3 to AIN6? 

The important result is that using uboot overlays does NOT impact on 
wireless. 

Regards, 

Kevin. 

-- 
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/7ad9a79c-fefb-4556-815f-8bc5dd3327d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Tips for incorporating a BBGW into a consumer product?

[Steve Groen]

 

 

Generally:

 How do you incorporate a BBGW into a consumer product?

 Does anybody do this, or do they design their own board

 using BBGW as a base?

 

Reset/Upgrade:

 How does a customer 'factory reset' a bricked BBGW?  Swap

 out the SD card?  Provide an externally accessible slot

 for the SD card, or allow customer to open and replace

 the card?  RMA?

 

 How are field upgrades handled?  Replace SD card?  Over the

 air upgrade procedure?  Connect via serial port?  RMA?

 

-- 
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/000601d28c7a%24fd3a7090%24f7af51b0%24%40mchsi.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: RT Linux boot crash

[acheesehead]

More info, from disassembled image, abort occurs in enter_kernel at 9e4:

09e0 <__enter_kernel>:
 9e0: e3a0 mov r0, #0 ; 0x0
 9e4: e1a0f004 mov pc, r4


On Tuesday, February 21, 2017 at 12:14:10 PM UTC-7, acheesehead wrote:
>
> Using JTAG to trace the problem, I found that the code aborts at 
> 0x820009e4, after eventually running a bunch of code in the 0xc000 area 
> of memory. The DM3730 TRM shows this region as reserved, so I am a bit 
> confused as to what could be there. Any suggestions on how to debug this?
>
> Addresses relative to 0x8200
>  9b0: e320f000 nop {0}
>  9b4: e320f000 nop {0}
>  9b8: e320f000 nop {0}
>  9bc: e320f000 nop {0}
>  9c0: eafe b 9c0 <_binary_zImage_start+0x9c0>
>  9c4: eafe b 9c4 <_binary_zImage_start+0x9c4>
>  9c8: eafe b 9c8 <_binary_zImage_start+0x9c8>
>  9cc: eafe b 9cc <_binary_zImage_start+0x9cc>
>  9d0: eafe b 9d0 <_binary_zImage_start+0x9d0>
>  9d4: ea01 b 9e0 <_binary_zImage_start+0x9e0>
>  9d8: eafe b 9d8 <_binary_zImage_start+0x9d8>
>  9dc: eafe b 9dc <_binary_zImage_start+0x9dc>
>  9e0: e3a0 mov r0, #0
>  9e4: e1a0f004 mov pc, r4 jumps to 80008000, eventually gets to 
> 8000805C, then 80101878, then 800080B8
>  then 80008078 branches to 8012028C, then 8011f6a4, then 8011f69c, 
> then C149728C
>
> Regs after crash, the link register shows C0D6F77C:
> PC: (R15) = 000C, CPSR = A1D7 (ABORT mode, ARM FIQ dis. IRQ dis.)
> Current:
>  R0 =D2FFB254, R1 =5B4C, R2 =0001420C, R3 =00014254
>  R4 =D2FFB254, R5 =CFFE7000, R6 =5B3C, R7 =000B
>  R8 =0014, R9 =0014, R10=, R11=C127A4E8, R12=CFFECB84
>  R13=C1601DFC, R14=C1601E00, SPSR=C176218C
> USR: R8 =, R9 =C127A4E8, R10=CFFECB84, R11=C1601DFC, R12=C1601E00
>  R13=, R14=
> FIQ: R8 =756FDFF6, R9 =65F6, R10=F57DEBFF, R11=7FE73FFF, R12=78C3DFF7
>  R13=C17621A4, R14=C17621A4, SPSR=
> IRQ: R13=C1762180, R14=C1762180, SPSR=8173
> SVC: R13=C1601DF0, R14=C0D6F77C, SPSR=61D3
> ABT: R13=C176218C, R14=0010, SPSR=A1D7
> UND: R13=C1762198, R14=C1762198, SPSR=
>

-- 
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/fde55eda-2eca-41d7-b11b-b4a5eb7aefa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] RT Linux boot crash

[acheesehead]

Using JTAG to trace the problem, I found that the code aborts at 
0x820009e4, after eventually running a bunch of code in the 0xc000 area 
of memory. The DM3730 TRM shows this region as reserved, so I am a bit 
confused as to what could be there. Any suggestions on how to debug this?

Addresses relative to 0x8200
 9b0: e320f000 nop {0}
 9b4: e320f000 nop {0}
 9b8: e320f000 nop {0}
 9bc: e320f000 nop {0}
 9c0: eafe b 9c0 <_binary_zImage_start+0x9c0>
 9c4: eafe b 9c4 <_binary_zImage_start+0x9c4>
 9c8: eafe b 9c8 <_binary_zImage_start+0x9c8>
 9cc: eafe b 9cc <_binary_zImage_start+0x9cc>
 9d0: eafe b 9d0 <_binary_zImage_start+0x9d0>
 9d4: ea01 b 9e0 <_binary_zImage_start+0x9e0>
 9d8: eafe b 9d8 <_binary_zImage_start+0x9d8>
 9dc: eafe b 9dc <_binary_zImage_start+0x9dc>
 9e0: e3a0 mov r0, #0
 9e4: e1a0f004 mov pc, r4 jumps to 80008000, eventually gets to 
8000805C, then 80101878, then 800080B8
 then 80008078 branches to 8012028C, then 8011f6a4, then 8011f69c, then 
C149728C

Regs after crash, the link register shows C0D6F77C:
PC: (R15) = 000C, CPSR = A1D7 (ABORT mode, ARM FIQ dis. IRQ dis.)
Current:
 R0 =D2FFB254, R1 =5B4C, R2 =0001420C, R3 =00014254
 R4 =D2FFB254, R5 =CFFE7000, R6 =5B3C, R7 =000B
 R8 =0014, R9 =0014, R10=, R11=C127A4E8, R12=CFFECB84
 R13=C1601DFC, R14=C1601E00, SPSR=C176218C
USR: R8 =, R9 =C127A4E8, R10=CFFECB84, R11=C1601DFC, R12=C1601E00
 R13=, R14=
FIQ: R8 =756FDFF6, R9 =65F6, R10=F57DEBFF, R11=7FE73FFF, R12=78C3DFF7
 R13=C17621A4, R14=C17621A4, SPSR=
IRQ: R13=C1762180, R14=C1762180, SPSR=8173
SVC: R13=C1601DF0, R14=C0D6F77C, SPSR=61D3
ABT: R13=C176218C, R14=0010, SPSR=A1D7
UND: R13=C1762198, R14=C1762198, SPSR=

-- 
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/6543088c-50aa-4bb6-b059-7b96034ff0e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bb-wl18xx-firmware depends on connman!?

[Robert Nelson]

On Mon, Feb 20, 2017 at 11:34 PM, Robert Nelson  wrote:
> On Mon, Feb 20, 2017 at 6:05 PM, Juliusz Chroboczek  wrote:
> bb-wl18xx-firmware
> Depends: bc
> Depends: bsdmainutils
> Depends: connman
> Depends: coreutils
> Depends: dnsmasq
>>
>> I've rebuilt the package without the spurious dependency.  It solves my
>> local problem, at least until the next upgrade.
>>
 A low-level piece of firmware should certainly not depend on high-level
 infrastructure (connman, dnsmasq).
>>
>>> While yes true, it grew it to 'fix' the 2016-11 image releases.
>>
>> Robert, you could either downgrade the Depends to a Recommends (which is
>> basically a Depends, but can be easily overridden by the user), or, even
>> better, split the package into a -firmware package and a -tether, with
>> the latter depending on the former.
>
> This is the change i implemented..
>
> https://github.com/rcn-ee/repos/commit/cc43ffb0374efb0e219863621927f5bc29b12212
>
> Of course, after landing in Portland for ELC, turns out my build farm
> sbuild tar got corrupted over the weekend..
>
> So yeah, till i rebuild the debian sbuild tar files and push it out to
> the build farm can't do much.. crap
>
> I fly back Saturday

Okay, rebuilt the corrupted sbuild tar, and pushed out the package

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/CAOCHtYi2vA%3Dh-b4gYKHeJiT7AU%3DCfAa%2BGQx2SoyPpX6e8um%3DDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB android

[Andrew Henderson]

The limiting factor in supporting Android on the BBB with newer kernels is 
support for SGX OpenGL ES. Newer Androids rely heavily on GLES for 
rendering. You can always fall back to PixelFlinger for software rendering, 
but a variety of apps will not work (or will work very slowly) when you use 
software rendering. For post 3.2 kernels, there are additional Android 
graphics libraries that are missing that you need for accelerated GLES. 
These libraries are proprietary and must be supplied by TI. Unfortunately, 
they are not supported any more, as support for the Android Graphics SDK 
has ended.   

For non-GLES builds, I recommend that you look at 
Android4Beagle: http://www.2net.co.uk/android4beagle.html

Andrew

On Tuesday, February 14, 2017 at 1:01:40 PM UTC-5, Harshdeep Dhatt wrote:
>
> Is Android being actively supported on BBB? I found resources online which 
> said Android 4.4 was ported sometime back - 
> http://www.2net.co.uk/tutorial/android-4.4-beaglebone
>
> Does it make sense to support the latest Android versions on the BBB? is 
> there an audience for such a project? I know its not straightforward to 
> port android to latest bbb kernels. But i just want to know if there is 
> such a need. Then maybe the effort is worth the pain :)
>
> Thanks,
> Harshdeep
>

-- 
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/417ee533-cf3d-4977-9233-28331f1514ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagleboard OpenCV-SVM-Tesseract-OCR (Support) IIoT

[amandalmia14]

HI All,

I want to develop an application similar 
to https://www.youtube.com/watch?v=vtSGSXKggEo (an industrial IoT solution 
). 

Will BeagleBoard will support, if yes which version ? (I think x15 should 
work).  If yes can you please explain how? 


Thanks,
Aman Dalmia

-- 
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/257b773d-6a28-4454-8d55-bc4a6fd06826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UAV Drone out of a BBBW

['woody stanford' via BeagleBoard]

OK better code example with complete force-moment-mass model coded, minimal 
guidance, simulation support.

https://www.raspberrypi.org/forums/viewtopic.php?p=1117477#p1117477

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/e9588e7b-cf60-489f-a905-dbaacf1cff5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Unable to import tkinter

[Chris Green]

anishece...@gmail.com wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 10 lines --]
> 
> When I am trying to import tkinter, I am getting error message.
> 
If you told us what you are doing to try and import tkinter and also
(more important) what the error message is we might be able to help!
:-)

-- 
Chris Green
·

-- 
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/5katnd-e7k.ln1%40esprimo.zbmc.eu.
For more options, visit https://groups.google.com/d/optout.