date:20171201

Re: [beagleboard] Linux Kernel tree for porting to mailine and basic support.

2017-12-01 Thread Robert Nelson

> Hi Robert,
>
> I had build the https://github.com/beagleboard/linux before using
> arm-none-eabi-gcc before successfully. After the move to Artful in Ubuntu
> and using the arm-none-eabi-gcc Version 5.4.1 the compiler crashes while
> compiling the source. It does not crash when I build Torvalds mainline. I am
> not sure what the problem is here.
>
> I am aware that you use the arm-linux-gnueabihf-gcc. Does building using
> arm-none-eabi-gcc cause any problems?

it builds fine natively with ubuntu artful:

http://gfnd.rcn-ee.org:81//farm/deb/COMPLETE-4.9.65-ti-r80-artful-armhf.txt

Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
7.2.0-8ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=arm-linux-gnueabihf- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libitm --disable-libquadmath --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-objc-gc=auto --enable-multiarch --enable-multilib
--disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16
--with-float=hard --with-mode=thumb --disable-werror --enable-multilib
--enable-checking=release --build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-8ubuntu3)

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

Re: [beagleboard] Linux Kernel tree for porting to mailine and basic support.

2017-12-01 Thread mindentropy



On Wednesday, November 29, 2017 at 3:26:13 AM UTC+5:30, RobertCNelson wrote:
>
> On Tue, Nov 28, 2017 at 3:52 PM, Graham  > wrote: 
> > The notes on GitHub say to only use VM VirtualBox 5.1.x and to not use 
> > 5.2.x. 
> > 
> > Is that because 5.2 was too new and unstable at the time? Or is there a 
> > fundamental issue with VM Virtualbox 5.2? 
>
> Those notes are just for windows users.  At the time of the lab, 
> 5.2."0" had major issues..  At the time 5.1.30 just worked... 
>
> Linux users can just git clone and move thru the lecture.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/


Hi Robert,

I had build the https://github.com/beagleboard/linux before using 
arm-none-eabi-gcc before successfully. After the move to Artful in Ubuntu 
and using the arm-none-eabi-gcc Version 5.4.1 the compiler crashes while 
compiling the source. It does not crash when I build Torvalds mainline. I 
am not sure what the problem is here.

I am aware that you use the arm-linux-gnueabihf-gcc. Does building using 
arm-none-eabi-gcc cause any problems?

Thanks,
Gautam.

-- 
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/648a2a31-020c-4f6a-bf13-d73ae882e3a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Help resetting signal to reuse prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);

2017-12-01 Thread Joseph Foster


I'm trying to reuse the prussdrv_pru_send_event(ARM_PRU0_INTERRUPT); 
function, but I can't reset the register for WBS r31,30

This is my PRU code:
Enter code here...// Origin 0 defines the start of the program in the
// PRU's instruction RAM, entrypoint is for debugging
#define CONST_PRUCFG C4
#define CONST_PRUSHAREDRAM   C28
 
#define PRU0_CTRL0x22000
#define PRU1_CTRL0x24000
 
#define CTPPR0   0x28
 
#define OWN_RAM  0x000
#define OTHER_RAM0x020
#define SHARED_RAM   0x00012000




.origin 0 // offset of the start of the code in PRU memory
.entrypoint START // program entry point, used by debugger only

#define PRU0_R31_VEC_VALID (1<<5)
#define SIGNUM 3 // corresponds to PRU_EVTOUT_0


START:
// initialize loop counter
WBS r31,30 //Wait for signal
MOV R16, SHARED_RAM
lbbo r1,r16,0,8
add r3,r1,r2
sbbo R3, R16, 8, 4
MOV r15,30
clr r31,r15
WBS r31,30 //Wait for signal
MOV R31.b0, PRU0_R31_VEC_VALID | SIGNUM
HALT

And this is the c:
Enter code here...#include 
#include 
#include 
#include 
#include 

#define PRU_SHARED_MEM_ADDR 0x00012000
#define SHM_OFFSET 2048

static int pru_cleanup(void) {
   int rtn = 0;

   /* clear the event (if asserted) */
   if(prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT)) {
  fprintf(stderr, "prussdrv_pru_clear_event() failed\n");
  rtn = -1;
   }

   /* halt and disable the PRU (if running) */
   if((rtn = prussdrv_pru_disable(0)) != 0) {
  fprintf(stderr, "prussdrv_pru_disable() failed\n");
  rtn = -1;
   }

   /* release the PRU clocks and disable prussdrv module */
   if((rtn = prussdrv_exit()) != 0) {
  fprintf(stderr, "prussdrv_exit() failed\n");
  rtn = -1;
   }

   return rtn;
}

static int pru_setup(const char * const path) {
   int rtn;
   tpruss_intc_initdata intc = PRUSS_INTC_INITDATA;

   if(!path) {
  fprintf(stderr, "pru_setup(): path is NULL\n");
  return -1;
   }

   /* initialize PRU */
   if((rtn = prussdrv_init()) != 0) {
  fprintf(stderr, "prussdrv_init() failed\n");
  return rtn;
   }

   /* open the interrupt */
   if((rtn = prussdrv_open(PRU_EVTOUT_0)) != 0) {
  fprintf(stderr, "prussdrv_open() failed\n");
  return rtn;
   }

   /* initialize interrupt */
   if((rtn = prussdrv_pruintc_init(&intc)) != 0) {
  fprintf(stderr, "prussdrv_pruintc_init() failed\n");
  return rtn;
   }

   /* load and run the PRU program */
   if((rtn = prussdrv_exec_program(0, path)) < 0) {
  fprintf(stderr, "prussdrv_exec_program() failed\n");
  return rtn;
   }

   return rtn;
}

volatile int32_t* init_prumem()
{
volatile int32_t* p;
prussdrv_map_prumem(PRUSS0_SHARED_DATARAM, (void**)&p);
return p+SHM_OFFSET;
}

int main()
{
printf("Init PRU..\n");
int ret = pru_setup("PRUTest.bin");
if(ret == -1) return -1;
volatile int* shared_mem = init_prumem();
//usleep(100);
printf("Waiting for message...\n");
shared_mem[0] = 5;
shared_mem[1] = 10;
prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);
int n = prussdrv_pru_wait_event(PRU_EVTOUT_0);
printf("Pru ended. Event: %i\n", n);
printf("Got number %d\n", shared_mem[2]);
pru_cleanup();
return 0;
}

In this example, the c code should never exit because the PRU code should 
be waiting for a second signal, but it does exit. How do I reset the signal 
so that I can reuse the interrupt?

-- 
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/d089cfe7-ae0f-4f5b-a156-22aafe573e39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Linux Kernel tree for porting to mailine and basic support.

2017-12-01 Thread Robert Nelson

> Hi Dimitar,
>
> I have not decided on anything to mainline as of now as I am new to BBB.  So
> the first step is to build the kernel from the right tree (which itself is
> confusing) and see where I can improve. At least try to solve simple
> problems and then move on to harder stuff. I will also start documenting
> stuff as I go along.
>
> Working on the i.mx6 and i.mx7 I find the approach of NXP better where I can
> just "git pull" from the NXP source tree and build the kernel rather than
> apply a set of patches using a script. Submissions of patches would be to
> the i.mx maintainers which would be eventually mainlined.

We "are not" TI...

TI does the same thing, you can go grab their tree here:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.14.y

or:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.9.y

or:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.4.y

and they push things mainline..

We just use it as a base for BeagleBoard.org and then include things
that have been rejected multple times on mainline, but our users use.

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

[beagleboard] Re: Linux Kernel tree for porting to mailine and basic support.

2017-12-01 Thread mindentropy

On Wednesday, November 29, 2017 at 1:09:37 AM UTC+5:30, din...@gmail.com 
wrote:
>
> Hi,
>
> I think https://github.com/beagleboard/linux would be the best reference 
> tree.
>
> Which subsystem are you going to mainline? 
>
> Regards,
> Dimitar
>

Hi Dimitar,

I have not decided on anything to mainline as of now as I am new to BBB.  
So the first step is to build the kernel from the right tree (which itself 
is confusing) and see where I can improve. At least try to solve simple 
problems and then move on to harder stuff. I will also start documenting 
stuff as I go along.

Working on the i.mx6 and i.mx7 I find the approach of NXP better where I 
can just "git pull" from the NXP source tree and build the kernel rather 
than apply a set of patches using a script. Submissions of patches would be 
to the i.mx maintainers which would be eventually mainlined.

Thanks,
Gautam.

-- 
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/dd781dd2-2b1b-4fbf-b9f5-00e4f9016ae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] prussdrv_open() on new debian kernel

2017-12-01 Thread Robert Nelson

On Fri, Dec 1, 2017 at 8:59 PM, Joseph Foster
 wrote:
> Ok so I am now load and execute on the PRUs, but how do I set the pinmux for
> the PRUs. I think it would use the U-Boot Cape Universal but the load
> example uses slots.

you can use config-pin to mux in the pins for the pru...

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

Re: [beagleboard] prussdrv_open() on new debian kernel

2017-12-01 Thread Joseph Foster

Ok so I am now load and execute on the PRUs, but how do I set the pinmux 
for the PRUs. I think it would use the U-Boot Cape Universal but the load 
example uses slots.

On Friday, December 1, 2017 at 10:52:30 AM UTC-6, RobertCNelson wrote:
>
> On Thu, Nov 30, 2017 at 11:45 PM, Joseph Foster 
> > wrote: 
> > Where would the slots file now be located. Its not in the 
> > /sys/devices/platform/bone_capemgr/ directory for me 
>
> Slots file is disabled when using U-Boot Overlays: 
>
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>
> 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/bae59066-3f03-4257-beb0-dc0281f5bc28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are these motors suitable?

2017-12-01 Thread 'Ludingtonian' via BeagleBoard

Thanks, Mark. That's what I was hoping to hear. 

On Friday, December 1, 2017 at 9:13:38 PM UTC, Mark Barton wrote:
>
> On 12/1/17 2:47 PM, rengl...@gmail.com  wrote:
>
> Hi. I'm looking at a tank-track chassis that comes with motors included. 
> Are they suitable for being controlled by a Blue or should I use an 
> external motor controller? For what it's worth, I'm looking at powering the 
> Blue with a 1600mAh LiPo battery. 
>
> Here are the details of the motors:
>   Operating Voltage Range: 3~7.5V
>   Rated Voltage: 6V
>   Max. No-load Current(3V): 140 mA
>   Max. No-load Current(6V): 170 mA
>   Max. Stall Current: 2.8 A
>
> Thank you. My apologies if this query is miscategorised.
>
>
>
> -- 
> 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/5b983893-2918-4af7-8de4-333c839d2677%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> You should be in good shape. The Beaglebone Blue has a Toshiba TB6612FNG 
> chip for the motor driver. You should be below the average current spec 
> unless you are planning on have a huge load. The stall current does exceed 
> the spec, but it is protected from thermal overload and will simply 
> shutdown. You software should also check for a stall and turn off the 
> drivers anyway.
>
> https://www.sparkfun.com/datasheets/Robotics/TB6612FNG.pdf
>
> HTH
> Mark
>

-- 
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/758820ab-9848-4173-bbac-9c4cc656bf24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are these motors suitable?

2017-12-01 Thread Mark Barton


On 12/1/17 2:47 PM, renglun...@gmail.com wrote:
Hi. I'm looking at a tank-track chassis that 
comes with motors included. Are they suitable 
for being controlled by a Blue or should I use 
an external motor controller? For what it's 
worth, I'm looking at powering the Blue with a 
1600mAh LiPo battery.


Here are the details of the motors:
  Operating Voltage Range: 3~7.5V
  Rated Voltage: 6V
  Max. No-load Current(3V): 140 mA
  Max. No-load Current(6V): 170 mA
  Max. Stall Current: 2.8 A

Thank you. My apologies if this query is 
miscategorised.




--
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/5b983893-2918-4af7-8de4-333c839d2677%40googlegroups.com 
.
For more options, visit 
https://groups.google.com/d/optout.
You should be in good shape. The Beaglebone Blue 
has a Toshiba TB6612FNG chip for the motor driver. 
You should be below the average current spec 
unless you are planning on have a huge load. The 
stall current does exceed the spec, but it is 
protected from thermal overload and will simply 
shutdown. You software should also check for a 
stall and turn off the drivers anyway.


https://www.sparkfun.com/datasheets/Robotics/TB6612FNG.pdf

HTH
Mark

--
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/5A21C5EF.3050803%40atldes.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are these motors suitable?

2017-12-01 Thread 'Ludingtonian Ludingtonian' via BeagleBoard

Thank you.

On Friday, December 1, 2017 at 8:01:01 PM UTC, Przemek Klosowski wrote:
>
> Beaglebone can source few dozen mA at 3.3V so you do need to put some 
> controller to drive those motors.
>
> On Fri, Dec 1, 2017 at 2:47 PM, > wrote:
>
>> Hi. I'm looking at a tank-track chassis that comes with motors included. 
>> Are they suitable for being controlled by a Blue or should I use an 
>> external motor controller? For what it's worth, I'm looking at powering the 
>> Blue with a 1600mAh LiPo battery. 
>>
>> Here are the details of the motors:
>>   Operating Voltage Range: 3~7.5V
>>   Rated Voltage: 6V
>>   Max. No-load Current(3V): 140 mA 
>> 
>>   Max. No-load Current(6V): 170 mA
>>   Max. Stall Current: 2.8 A
>>
>> Thank you. My apologies if this query is miscategorised.
>>
>>
>>
>> -- 
>> 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/5b983893-2918-4af7-8de4-333c839d2677%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/528cc423-cd75-4531-b80d-18d2226cbeb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are these motors suitable?

2017-12-01 Thread Przemek Klosowski

Beaglebone can source few dozen mA at 3.3V so you do need to put some
controller to drive those motors.

On Fri, Dec 1, 2017 at 2:47 PM,  wrote:

> Hi. I'm looking at a tank-track chassis that comes with motors included.
> Are they suitable for being controlled by a Blue or should I use an
> external motor controller? For what it's worth, I'm looking at powering the
> Blue with a 1600mAh LiPo battery.
>
> Here are the details of the motors:
>   Operating Voltage Range: 3~7.5V
>   Rated Voltage: 6V
>   Max. No-load Current(3V): 140 mA
> 
>   Max. No-load Current(6V): 170 mA
>   Max. Stall Current: 2.8 A
>
> Thank you. My apologies if this query is miscategorised.
>
>
>
> --
> 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/5b983893-2918-4af7-8de4-333c839d2677%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/CAC%3D1GgG8AN%3DTu2xD-NvFRooBC23Hx6ZMs1V1fX79uktrmsV22g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Rotary quadrature encoder

2017-12-01 Thread Przemek Klosowski

On Fri, Dec 1, 2017 at 1:53 PM,  wrote:

> Hi all
>
> I am developing on a beaglebone black and want to include a rotary knob to
> Control cursors on my display in user space etc.
>
> The selected quadrature encoder is here : http://www.mouser.com/ds/2/54/
> EL12T-777462.pdf
>
> I need to convert the pulses into a direction and count up or down
> accordingly so I plan on using an external low cost micro controller to
> count up or down and send the value out onto the bus.
>

Beaglebone has a hardware quadrature decoder called eQEP.
http://beagleboard.org/project/eqep_rotary_encoder.

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

[beagleboard] Are these motors suitable?

2017-12-01 Thread renglund63

Hi. I'm looking at a tank-track chassis that comes with motors included. 
Are they suitable for being controlled by a Blue or should I use an 
external motor controller? For what it's worth, I'm looking at powering the 
Blue with a 1600mAh LiPo battery. 

Here are the details of the motors:
  Operating Voltage Range: 3~7.5V
  Rated Voltage: 6V
  Max. No-load Current(3V): 140 mA
  Max. No-load Current(6V): 170 mA
  Max. Stall Current: 2.8 A

Thank you. My apologies if this query is miscategorised.



-- 
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/5b983893-2918-4af7-8de4-333c839d2677%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Rotary quadrature encoder

2017-12-01 Thread bodetechnics

Hi all

I am developing on a beaglebone black and want to include a rotary knob to 
Control cursors on my display in user space etc.

The selected quadrature encoder is here : 
http://www.mouser.com/ds/2/54/EL12T-777462.pdf

I need to convert the pulses into a direction and count up or down accordingly 
so I plan on using an external low cost micro controller to count up or down 
and send the value out onto the bus.

I then plan to send the value as it is updated onto the i2c bus to the 
beaglebone. The beaglebone will then react accordingly to the events.

So the order of hardware/software from end to end will be:

Rotary encoder -> External PIC - > i2c bus -> userspace

Am I attacking this from the wrong direction?

Does anybody have a better recommendation on how to interface a rotary Control 
knob into linux user space?

For reference, I will also be interfacing a keypad using the Ti TCA8418 keypad 
scanner which will also be hooked onto the i2c bus.

Thanks again 

-- 
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/4740d6e5-815a-4963-9121-57ec6dad1494%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is cape manager obsolete? What about device tree overlays?

2017-12-01 Thread Robert Nelson

On Thu, Nov 30, 2017 at 11:40 PM, Johan Henselmans
 wrote:
> Thanks for the explanation, but could you elaborate a bit more on it?
>
> As far as I understand the world as it is now works  this way:
>
> 0- If you are running anything beyond kernel 4.1 you should be using uboot
> overlays. Be careful to load the latest bb-cape overlays and be sure that
> uboot is the latest version, check via /opt/script/tools/version.sh,
> look for
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.01-1-gb2412df]
> this is wrong:
> ^^
> Should be something like:
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.09-2-g0f3f1c7907]
>
> If not, do
> /opt/scripts/tools/developers/update_bootloader.sh
> This should put an updated bootloader in the boot block of your Beaglebone.
> Careful: you should have booted from the internal flash, not from an
> external flash-card.
>
> 1-Overlays are now loaded in /boot/uEnv.txt at boot time.
> Cape-universal or the other universal capes make it possible to use
> config-pin to configure the pins that you want to use,
> example:
> config-pin -l p9-21
> gives all the possible settings
> config-pin -q p9-21
> gives the current setting
> config-pin -a p9-21 i2c
> makes the pin respond to i2c signals.
>
> 
>
> 2-if another overlay is loaded in /bootuEnv.txt which is not of the
> universal type, config-pin does not work anymore

Correct, someone needs to write a pin manager for U-Boot..  Currently
what we do, if a custom cape is defined, cape_universal is disabled..

However you can toggle oneboard devices:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices

and the cape-universal knows what to do..

> 3-To find out which overlay is loaded if config-pin does not run, use
> command ?? to find out which overlay(s) is/are currently running

sudo /opt/scripts/tools/version.sh

&

USB Serial Debug cable, to track what U-Boot did..

&

cat /proc/cmdline | sed 's/ /\n/g' | grep uboot_detected_capes= || true

(very new: uboot_detected_capes )

> 4-If you want to make a combination of some of the universal settings plus
> an overlay, ??

Source is here:

https://github.com/beagleboard/bb.org-overlays

here is cape universal with

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/univ-bbb-EVA-00A0.dts


>
> 
>
> I am pretty sure it's all wrong, but I am struggling with the info too. I am
> trying to modernize gobot to the latest uboot overlay stufff (it is still
> looking for cape_mgr slots file), but it is not exactly clear how I can find
> out if an overlay is set, or if I am able to set a specific pin after some
> overlay has been loaded.


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

Re: [beagleboard] prussdrv_open() on new debian kernel

2017-12-01 Thread Robert Nelson

On Thu, Nov 30, 2017 at 11:45 PM, Joseph Foster
 wrote:
> Where would the slots file now be located. Its not in the
> /sys/devices/platform/bone_capemgr/ directory for me

Slots file is disabled when using U-Boot Overlays:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

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

Re: [beagleboard] Linux Kernel tree for porting to mailine and basic support.

Re: [beagleboard] Linux Kernel tree for porting to mailine and basic support.

[beagleboard] Help resetting signal to reuse prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);

Re: [beagleboard] Re: Linux Kernel tree for porting to mailine and basic support.

[beagleboard] Re: Linux Kernel tree for porting to mailine and basic support.

Re: [beagleboard] prussdrv_open() on new debian kernel

Re: [beagleboard] prussdrv_open() on new debian kernel

Re: [beagleboard] Are these motors suitable?

Re: [beagleboard] Are these motors suitable?

Re: [beagleboard] Are these motors suitable?

Re: [beagleboard] Are these motors suitable?

Re: [beagleboard] Rotary quadrature encoder

[beagleboard] Are these motors suitable?

[beagleboard] Rotary quadrature encoder

Re: [beagleboard] Is cape manager obsolete? What about device tree overlays?

Re: [beagleboard] prussdrv_open() on new debian kernel

16 matches

Site Navigation

Mail list logo

Footer information