[beagleboard] Re: Homes required for BeagleBone Whites and various capes

[Mark A. Yoder]

Jonathan:
   I'd be happy to put these in the hands of my students, or the campus 
Maker Lab.

--Mark


On Friday, May 3, 2019 at 8:17:20 PM UTC-4, Jonathan Miles wrote:
>
> Hello,
>
> My employers are doing an office clear-out, and there are some BeagleBone 
> whites and capes that are going spare. Does anyone know of a good cause 
> that would be interested in having these?
>
>- 2x BeagleBone (Boxed)
>- 1x BeagleBone (unboxed)
>- 2x BeagleBone DVI-D cape (boxed)
>- 1x BeagleBone DVI-D cape (unboxed)
>- 1x BeagleBone DVI-D with Audio cape (boxed)
>- 1x BeagleBone Breadboard cape (boxed)
>
> Thanks,
>
> Jonathan
>
>

-- 
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/c1ad64e3-8b1b-4928-afbb-28bd94a7d5ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Single wire interface module(SWIM) programming for STM8 MCUs

[TJF]

A W1 bus can handle multiple devises, each one addressed by an 8 byte ID. 
Different devices can share the same bus, ie. sensors, MCUs, .. But the 
w1-kernel driver doesn't support multiple devices.

Have a look at libpruw1 project .

Regards

-- 
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/5803db5c-6550-496c-81d6-91cef81ccc85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Blue: Hack to boot when DC power is restored to DC Jack?

[Louis Whitcomb]

Dear Graham,

   Thanks for your reply!  Yes, I am aware of power-on reset ICs, as well 
as simple power-on reset circuits with discrete components.  I was hoping 
that the designers of the BeagleBone Blue, or experts on the OSD3358, might 
be aware solution that was already designed into the system (cut a trace, 
short an input, burn a fuse, etc).  

   Thanks and Best Regards,
 
-Louis

On Monday, May 6, 2019 at 9:03:03 PM UTC-4, gra...@flex-radio.com wrote:
>
> Louis:
>
> There are multiple families of a type of IC known as a Power-On reset IC, 
> or supervisory reset IC
>
> They wait for a Voltage to appear above a threshold, and remain stable for 
> some period, then send a reset output for a predetermined time.
>
> If you go to the On Semi site, and search on "Power On Reset", you will 
> get hits about ten different ICs.
> Check out the MAX809 as an example
>
> TI has a selector page, see
> http://www.ti.com/power-management/supervisor-reset-ic/overview.html
>
> If you go to the On Semi site, and search on "Power On Reset", you will 
> get hits about ten different ICs.
> Check out the MAX809 as an example
>
> They are generally cheap and small, and many require no support or glue 
> parts other than a bypass cap, if their default Voltages and times work for 
> you.
>
> --- Graham,
>
>
>>

-- 
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/a696f6c6-bdd4-4ca7-9156-713a57cf80d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to program through Raspberry Pi 3

[gulrej . ansari]

Hi,

I want to program through Beaglebone, is it possible? we have 12 PCBA in a 
single panel, each PCBA have Z-Wave and STM8 MCU
For the Z-Wave SPI interface is available for programming and for STM8 SWIM 
(Single Wire Interface Module) is available for programming 

So, we need to do parallel programming to all PCBA's at the same time 
through the RPi, is it possible? if yes then how? Kindly do the needful for 
the same

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/2a87f893-03db-4cdd-bd92-b9ab12a934f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Hugh Frater]

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

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

version.sh shows:

git:/opt/scripts/:[c2a5ae96746d10d711c60bc84ba244f4cd7b75c3]
eeprom:[A335BNLT00C03816BBBK190D]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
2018.09-2-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.108-ti-r104]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_emmc=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[disable_uboot_overlay_wireless=1]
uboot_overlay_options:[disable_uboot_overlay_adc=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.4.20190429.0-0rcnee0~stretch+20190429]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 quiet]
dmesg | grep remote
[1.302485] remoteproc remoteproc0: wkup_m3 is available
[1.389525] remoteproc remoteproc0: powering up wkup_m3
[1.389661] remoteproc remoteproc0: Booting fw image 
am335x-pm-firmware.elf, size 217168
[1.393097] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[0.971911] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 
568
dmesg | grep gpio-of-helper
[0.984114] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

What am I doing wrong here? Surely PRU support is one of those things that 
should be working out of the box with the correct u-boot overlay applied?





-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a71c3102-1ead-43cc-8553-464325a9557d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[n ithinu]

I do not have the link anymore. Anyway, it said to get the last version of 
the system on an sd card, but it is not enough as the old bootloader from 
the eMMc would still be used. So it said to desactivate the bootloader

sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k

Possibly it loses the contents of all partitions on the eMMC, I do not know.

If you need the EEPROM and do not want to use the sd card, you should 
instead update the eMMC. I guess you will find links for that.

On Wednesday, May 8, 2019 at 3:27:00 AM UTC+2, layt...@gmail.com wrote:
>
> Thank you! If possible, could you please give me more detailed instruction 
> on how to solve this? Maybe some links would be very helpful!
>
> On Monday, May 6, 2019 at 5:09:27 AM UTC-7, ithinu wrote:
>>
>> It was something like new OS on an sd card, but something outdated in the 
>> booting sequence on the EEPROM and I needed to fill the latter with 
>> zeros... something strange like that if I remember well.
>>
>> On Monday, May 6, 2019 at 1:58:10 PM UTC+2, layt...@gmail.com wrote:
>>>
>>> Hello, I have the same problem here so I cannot run on boot either. Have 
>>> you solved this problem? 
>>> I'm looking forward to hearing from you, thank you!
>>>
>>> On Monday, January 14, 2019 at 5:21:43 AM UTC-8, ith...@gmail.com wrote:

 I use 
 http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
  
 from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
 flashed it into the built-in eMMc as the page told that it is better so.

 Then I configured librobotcontrol to use rc_balance as told here 
 http://strawsondesign.com/#!edumip-software, which gave an error:

 $ systemctl status robotcontrol.service
 ● robotcontrol.service - robotcontrol
Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
 vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 
 UTC; 13s ago
   Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
 status=255)

 Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
 Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached 
 while waiting for pwm driver
 Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
 Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
 process exited, code=exited status=255
 Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
 Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit 
 entered failed state.
 Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed 
 with result 'exit-code'.

 $ uname -a
 Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 
 2018 armv7l GNU/Linux

 I guess the hardware is ok, as I previously used some old image from 
 https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.



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

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

It seems that this stupid board butchered my response. Here's the rest:

... on Beaglebone Black, AIN-[0-6] open, but AIN-7 connected on board to 1V65, 
I get

$ ./hansOK 
initialized, ESize = 4
  F50  ED5  EC6  B6A  83F  845  8EA  F24
  F4E  F13  ECD  D08  A58  941  948  F2F
  F5D  F23  EE5  DF1  BEA  A8C  A09  F28
  F56  F33  F0F  E72  CE9  BB1  AFF  F2F
  F63  F34  F1A  EB8  D9D  CA7  BEA  F25
  F52  F2F  F2D  EE0  E06  D50  CB3  F2F
  F5E  F2D  F2C  EF1  E57  DCF  D4F  F25
  F4B  F2C  F35  EFB  E75  E11  DBF  F2E
  F55  F2D  F2A  EFA  E95  E4B  E0E  F25
  F4D  F2A  F2F  F05  EA0  E68  E3D  F33
  F57  F25  F26  EFC  EAD  E8A  E6A  F28
  F47  F22  F2A  EFF  EB0  E8B  E75  F2F
  F54  F27  F24  EF8  EB3  E9D  E8B  F2A
$ sudo rmmod uio_pruss 
$ sudo modprobe uio_pruss extram_pool_sz=0x80
$ ./hansOK 
initialized, ESize = 80
  F43  ED3  EC0  B64  842  839  8D3  F2F
  F50  F03  EC9  D11  A62  941  930  F2A
  F57  F2B  EE6  DEC  BDE  A8B  A07  F32
  F58  F22  F01  E71  CEF  BB5  AF6  F28
  F5A  F31  F1B  EB2  D95  CA7  BEF  F31
  F58  F28  F23  EDF  E11  D52  CAE  F25
  F51  F2F  F32  EED  E47  DC6  D51  F32
  F54  F2A  F30  EFB  E7B  E15  DB6  F2B
  F4F  F2D  F30  EFC  E89  E4A  E10  F35
  F56  F21  F26  EFF  EA9  E71  E3E  F24
  F4B  F28  F2B  F00  EAC  E82  E67  F37
  F52  F20  F25  EFD  EBA  E94  E74  F2A
  F49  F2A  F2A  EF7  EAE  E98  E89  F33

So here it works with standard (16384 samples) or maximum ERam (220500 
samples) configuration on kernel

4.14.69-ti-r76

Regards

-- 
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/d4b3f47c-3037-4fbc-b71a-f73444cacdad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

Hi Hans!

Am Mittwoch, 8. Mai 2019 22:26:04 UTC+2 schrieb Hans Leeuw:
>
> Oh, and the loop goes on. The problem is not there.
>

Yes, there's a break; statement missing at the end of the while loop.

Sorry, I cannot reproduce the problem. Using this code

// gcc -Wall -o hansOK hansOK.c -lpruio
#include "stdio.h"
#include "libpruio/pruio.h" // include header
#include 

int main(int argc, char **argv)
{
  int i = 1, n;
  char *emsg = "CTOR";
  pruIo *io = pruio_new(PRUIO_DEF_ACTIVE, 4, 0x98, 0);
  while (!io->Errr) {
if (pruio_adc_setStep(io,  7, 0, 1, 0, 0)) {emsg = "AIN-0"; i = 2; break
;} //Step  7, AIN-0
if (pruio_adc_setStep(io,  8, 1, 1, 0, 0)) {emsg = "AIN-1"; i = 2; break
;} //Step  8, AIN-1
if (pruio_adc_setStep(io,  9, 2, 1, 0, 0)) {emsg = "AIN-2"; i = 2; break
;} //Step  9, AIN-2
if (pruio_adc_setStep(io, 10, 3, 1, 0, 0)) {emsg = "AIN-3"; i = 2; break
;} //Step 10, AIN-3
if (pruio_adc_setStep(io, 11, 4, 1, 0, 0)) {emsg = "AIN-4"; i = 2; break
;} //Step 11, AIN-4
if (pruio_adc_setStep(io, 12, 5, 1, 0, 0)) {emsg = "AIN-5"; i = 2; break
;} //Step 12, AIN-5
if (pruio_adc_setStep(io, 13, 6, 1, 0, 0)) {emsg = "AIN-6"; i = 2; break
;} //Step 13, AIN-6
if (pruio_adc_setStep(io, 14, 7, 1, 0, 0)) {emsg = "AIN-7"; i = 2; break
;} //Step 14, AIN-7

// upload settings, prepare MM mode
if (pruio_config(io, 220500, 255<<7, 45352, 0)) {emsg = "config";   i = 
3; break;}
//if (pruio_config(io, 16384, 255<<7, 45352, 0)) {emsg = "config";   i 
= 3; break;}
// start measurement   //Starts in rb_mode
if (pruio_rb_start(io)){emsg = "rb_start"; i = 4
; break;}
printf("initialized, ESize = %X\n", io->ESize);
usleep(1);
  /* now current ADC samples are available for AIN-0 to AIN-7 in array 
io->Adc->Value[] */
for(n = 0; n <= 12; n++) { //   print some lines
  for(i = 0; i < 8; i++) //all steps
printf(" %4X", io->Adc->Value[i + (8 * n)]); //  output one channel 
in hex
  printf("\n"); // next line
  }
i = 0; break;
  }
/* we're done */
  if (io->Errr) printf("%s failed (%s)\n", emsg, io->Errr);

  pruio_destroy(io);/* destroy driver structure */
  return i;
}

on Beaglebone Black, AIN-[0-6] open, but AIN-7 connected on board to 1V65, 
I get

$ ./hansOK 
initialized, ESize = 4
  F50  ED5  EC6  B6A  83F  845  8EA  F24
  F4E  F13  ECD  D08  A58  941  948  F2F
  F5D  F23  EE5  DF1  BEA  A8C  A09  F28
  F56  F33  F0F  E72  CE9  BB1  AFF  F2F
  F63  F34  F1A  EB8  D9D  CA7  BEA  F25
  F52  F2F  F2D  EE0  E06  D50  CB3  F2F
  F5E  F2D  F2C  EF1  E57  DCF  D4F  F25
  F4B  F2C  F35  EFB  E75  E11  DBF  F2E
  F55  F2D  F2A  EFA  E95  E4B  E0E  F25
  F4D  F2A  F2F  F05  EA0  E68  E3D  F33
  F57  F25  F26  EFC  EAD  E8A  E6A  F28
  F47  F22  F2A  EFF  EB0  E8B  E75  F2F
  F54  F27  F24  EF8  EB3  E9D  E8B  F2A
$ sudo rmmod uio_pruss 
$ sudo modprobe uio_pruss extram_pool_sz=0x80
$ ./hansOK 
initialized, ESize = 80
  F43  ED3  EC0  B64  842  839  8D3  F2F
  F50  F03  EC9  D11  A62  941  930  F2A
  F57  F2B  EE6  DEC  BDE  A8B  A07  F32
  F58  F22  F01  E71  CEF  BB5  AF6  F28
  F5A  F31  F1B  EB2  D95  CA7  BEF  F31
  F58  F28  F23  EDF  E11  D52  CAE  F25
  F51  F2F  F32  EED  E47  DC6  D51  F32
  F54  F2A  F30  EFB  E7B  E15  DB6  F2B
  F4F  F2D  F30  EFC  E89  E4A  E10  F35
  F56  F21  F26  EFF  EA9  E71  E3E  F24
  F4B  F28  F2B  F00  EAC  E82  E67  F37
  F52  F20  F25  EFD  EBA  E94  E74  F2A
  F49  F2A  F2A  EF7  EAE  E98  E89  F33

So here it works with standard (16384 samples) or maximum ERam (220500 
samples) configuration on kernel

4.14.69-ti-r76

Regards

-- 
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/235b92d2-f2ac-4b46-9697-377df4f445f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How do I detect if I am running off the battery ?

[Dave]

I am using and OSD3358 based PocketBeaglish Board. 

I need to figure out if the board is running from external power or the 
LiPo battery, 
Is there an easy means of doing so ?

Something in sysfs maybe ?

-- 
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/996ff5be-08ba-44d9-927e-04a72baf5931%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.