RE: [beagleboard] Re: BBB- DCAN1 problems using latest debian image

2017-10-31 Thread John Dammeyer 
The CANUSB from Lawicel is a standard USB device that looks like a serial port 
since it can use the FTDI driver.
 
On my MachineKit Debian Beagle 2.0 when I plug in the CANUSB I find I have a 
/dev/ttyUSB0 device.
I installed putty and connected to /dev/ttyUSB0
In the terminal window
V with a CR returns
V1011 
An S5 sets 250kbps
An O opens the port.
t12327788 with a CR again of course sends SID=123, DLC=2, Data 0x77 0x88
With nothing connected to the CANUSB the red LED goes on.  (or if bitrate is 
wrong).
A C closes the port.
An F prints the error flags and shuts off the red led.
 
It’s a good idea to have auto line feed set in putty so that each received 
message is on a new line.
John Dammeyer
 
 
 
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Tracy Smith
Sent: October-31-17 3:42 PM
To: BeagleBoard
Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
 
Hi John,

I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a 
custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.  

The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the 
BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
(pin E18), 

1. Did I miss the names for these pins in u-boot?

2. If u-boot does not support these pins, should they be added to u-boot, 
and/or added to the kernel to support these pins?

Should these pins be pinmuxed in both uboot and the  kernel, or only in the 
kernel dts?  Checking now to see if the kernel has support for these pins.

thx, Tracy

On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote:
Hi,
 
I have been trying to build a proof of concept system using two beaglebone 
black units with there DCAN1 (pins P9_24 and P9_26) and two can transcievers TI 
SN65HVD251P.
The can transceivers are powered from the same 5V bench supply as both of the 
beaglebone blacks. the canh and canl pins are terminated at both ends by 120R 
resistors to ensure the 60R bus impedence. 
 
I was following the instructions in other posts about updating to the latest 
debian version and then upgrading the kernel to 3.14. This i have done.
uname -a
Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC 2015 
armv7l GNU/Linux
 
I added dtb=am335x-boneblack-can1.dtb to the uEnv.txt
 
I have also installed the canbus tools within the image so i can attempt a 
cangen can0 and candump can0.
 
On system boot i am doing the following:
 
modprobe can
modprobe can-dev
modprobe can-raw
 
ip link set can0 type can bitrate 125000 triple-sampling on
ifconfig can0 up
 
however if i use candump can0 and cangen can0 within two seperate putty 
sessions i dont see anything. 
 
If I create a vcan bus i do see the messages in loopback.
sudo modprobe vcan
sudo ip link add dev vcan0 type vcan
 sudo ifconfig vcan0 up
 
Previously I was using an older debian image and found that when i ran cangen 
can0 that the buffer would give me an error that it was full. however now with 
the latest image i am not getting the bufer full message but still not seeing 
anything on the candump. What should i expect to see here?
 
Can anyone see where I have gone wrong or a step i am missing?
 
Thanks in advance.
 
Mark
 
-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/_9u1B6ZkgCU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e6297438-0999-4320-916e-f41d74671533%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/003001d352ac%24d3f24980%247bd6dc80%24%40autoartisans.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

2017-10-31 Thread William Hermans 
SO what is it that you're trying to do ? I've read your posts, but am still
mystified. Just sayin' . . . I've been working with this hardware for
around 5 years now,  have written many device tree overlays for various
hardware configurations. Including GPIO, I2C, UART, CAN, SPI, etc.

I'm willing to give you some guidance, but need to understand what it is
you're trying to do . . .

I2C really isn't that hard to get working. Nor is most of it.

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

[beagleboard] How could I program my custom board EEPROM?

2017-10-31 Thread twinfa5 


Hi, I am a new one at this area. My partner and I made a copy of beaglebone 
black on our board. We just deleted Ethernet and HDMI. We still used 4GB 
DDR3, 4GB eMMC and a empty EEPROM. We will boot it from uSD just like the 
beaglebone black. 

The image file is 
BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz ". Because 
the EEPROM is blank so it would not boot. Learned there is some pinmuxing 
that takes place from the information in the EEPROM that was necessary.


The question is how will we do about the EEPROM to boot our board properly? 
Can we just copy the files from EEPROM of original Beaglebone black to our 
custom board EEPROM?

 

Best regards,

-Sam

-- 
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/ca0427af-d67c-44c8-8a49-929eb31463a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How can I program my custom board EEPROM??

2017-10-31 Thread hongsc 


Hi, I am a new one at this area. My partner and I made a copy of beaglebone 
black on our board. We just deleted Ethernet and HDMI. We still used 4GB 
DDR3, 4GB eMMC and a empty EEPROM. We will boot it from uSD just like the 
beaglebone black. The image file is 
BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz ". Because 
the EEPROM is blank so it would not boot. Learned there is some pinmuxing 
that takes place from the information in the EEPROM that was necessary.


The question is how will we do about the EEPROM to boot our board properly? 
Can we just copy the files from EEPROM of original Beaglebone black to our 
custom board EEPROM?

 

Best regards,

-Sam

 

-- 
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/68937024-7127-4868-a66c-e62b5cb23fd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: u-boot support for pins

2017-10-31 Thread Tracy Smith 


An update.   In u-boot/board/ti/am335x I do see the following. So, the pad 
name for I2C_DATA is uart1_ctsn for D18.  For pad name uart1_rtsn it is pin 
D17.  So this will give the DCAN0_TX/RX for u-boot.


static struct module_pin_mux i2c2_pin_mux[] = {
{OFFSET(uart1_ctsn), (MODE(3) | RXACTIVE |
PULLUP_EN | PULLUDEN | SLEWCTRL)},  /* I2C_DATA 
*/
{OFFSET(uart1_rtsn), (MODE(3) | RXACTIVE |
PULLUP_EN | PULLUDEN | SLEWCTRL)},  /* I2C_SCLK 
*/
{-1},
};

Now looking in u-boot/board/ti/am335x for E17/E18 for DCAN1_TX/RX.  One 
could use E17/E18 for CAN1 instead of the P9 expansion header.

On Tuesday, October 31, 2017 at 5:37:43 PM UTC-5, Tracy Smith wrote:
>
> The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h 
> includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
> for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
> (pin E18), 
>
> 1. Did I miss the names for these pins in u-boot?
>
> 2. If u-boot does not support these pins, should they be added to u-boot, 
> and/or added to the kernel to support these pins?
>
> Need these pins to support USB/CAN device on a custom BBB. Need to pinmux 
> these for the USB/CAN from Lawicel.
>
> thx,
> Tracy
>

-- 
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/f1e6ec6e-97c4-4d27-ac1f-4fd4fa881efc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB- DCAN1 problems using latest debian image

2017-10-31 Thread Tracy Smith 
Hi John,

I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have 
a custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.  

The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for 
the BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see 
names for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) 
nor TP9 (pin E18), 

1. Did I miss the names for these pins in u-boot?

2. If u-boot does not support these pins, should they be added to u-boot, 
and/or added to the kernel to support these pins?

Should these pins be pinmuxed in both uboot and the  kernel, or only in the 
kernel dts?  Checking now to see if the kernel has support for these pins.

thx, Tracy

On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote:
>
> Hi,
>
> I have been trying to build a proof of concept system using two beaglebone 
> black units with there DCAN1 (pins P9_24 and P9_26) and two can 
> transcievers TI SN65HVD251P.
> The can transceivers are powered from the same 5V bench supply as both of 
> the beaglebone blacks. the canh and canl pins are terminated at both ends 
> by 120R resistors to ensure the 60R bus impedence. 
>
> I was following the instructions in other posts about updating to the 
> latest debian version and then upgrading the kernel to 3.14. This i have 
> done.
> uname -a
> Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC 
> 2015 armv7l GNU/Linux
>
> I added dtb=am335x-boneblack-can1.dtb to the uEnv.txt
>
> I have also installed the canbus tools within the image so i can attempt a 
> cangen can0 and candump can0.
>
> On system boot i am doing the following:
>
> modprobe can
> modprobe can-dev
> modprobe can-raw
>
> ip link set can0 type can bitrate 125000 triple-sampling on
> ifconfig can0 up
>
> however if i use candump can0 and cangen can0 within two seperate putty 
> sessions i dont see anything. 
>
> If I create a vcan bus i do see the messages in loopback.
> sudo modprobe vcan
> sudo ip link add dev vcan0 type vcan
>  sudo ifconfig vcan0 up
>
> Previously I was using an older debian image and found that when i ran 
> cangen can0 that the buffer would give me an error that it was full. 
> however now with the latest image i am not getting the bufer full message 
> but still not seeing anything on the candump. What should i expect to see 
> here?
>
> Can anyone see where I have gone wrong or a step i am missing?
>
> Thanks in advance.
>
> 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/e6297438-0999-4320-916e-f41d74671533%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] u-boot support for pins

2017-10-31 Thread Tracy Smith 
The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h 
includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
(pin E18), 

1. Did I miss the names for these pins in u-boot?

2. If u-boot does not support these pins, should they be added to u-boot, 
and/or added to the kernel to support these pins?

Need these pins to support USB/CAN device on a custom BBB. Need to pinmux 
these for the USB/CAN from Lawicel.

thx,
Tracy

-- 
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/cbfa210e-1ccd-4983-8599-83960631f01e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Overlays and 4.14 Linux kernel for CAN

2017-10-31 Thread Tracy Smith 
Hi Robert,

the pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h 
includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
for i2c2_scl pin D17 and i2c2_sda pin D18, nor tstpt1 pin E17 nor TP9 pin 
E18, 

1. Did I miss the names for this pins for u-boot?

2. If u-boot does not have support for these pins, should they be added to 
u-boot, and/or added to the kernel to support these pins for a USB/CAN?

thx,
Tracy

On Friday, October 27, 2017 at 10:59:16 AM UTC-5, Tracy Smith wrote:
>
> Need to enable DCAN1 and DCAN2 support for the BeagleBone Black. 
>
>
> 1) Are overlays supported by the 4.14 Linux kernel?  
>
>
> 2) Where can I find documentation on enabling CAN1 and CAN2 for the 
> BeagleBone Black for the 4.x kernel?
>
>
> 3) If overlays are no longer supported, any documentation on enabling CAN 
> without overlays?
>
>
> http://zewaren.net/site/node/152
>
>
> 4) Does Linux kernel 4.14 release support BBB WiFi?
>
>
> 5) Is the following information still reliable for the 4.x kernel and 
> which release is the latest supported release for BeagleBone black with 
> WiFi, is it 4.14 stable? 
>
>
> http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/ 
>
> 
>
>
> http://elixir.free-electrons.com/linux/latest/source/Documentation/devicetree/overlay-notes.txt
>

-- 
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/4aeef0d8-713d-4091-980b-1cbf52bb5c38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Pocket Beagle SPI1 ChipSelect on silkscreen is not CS0 but CS1

2017-10-31 Thread Henner Zeller 
On 31 October 2017 at 13:12, Jason Kridner  wrote:
>
>
>> On Oct 31, 2017, at 2:59 PM, Robert Nelson  wrote:
>>
>>> On Tue, Oct 31, 2017 at 1:41 PM, Graham  wrote:
>>> Robert:
>>>
>>> Are the default device tree pinmux connections for the PocketBeagle the
>>> functions
>>> named in the silkscreen labels on the bottom of the PocketBeagle?
>>
>> Yes,
>>
>>>
>>> So far this appears to be the case.  Any exceptions?
>>
>> If not, let me know. ;) So we can fix it..
>
> 48 should be labeled 44.
>
> SPI1 is CS1, not CS0 (silk screen doesn’t say).

Actually, my pull request to the board fixed the chip-select printing:

https://github.com/beagleboard/pocketbeagle/pull/9
https://github.com/beagleboard/pocketbeagle/commit/1d96a30c13ed9ab13bd1372aa87de865339e5499


-h

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

Re: [beagleboard] Pocket Beagle SPI1 ChipSelect on silkscreen is not CS0 but CS1

2017-10-31 Thread Jason Kridner 


> On Oct 31, 2017, at 2:59 PM, Robert Nelson  wrote:
> 
>> On Tue, Oct 31, 2017 at 1:41 PM, Graham  wrote:
>> Robert:
>> 
>> Are the default device tree pinmux connections for the PocketBeagle the
>> functions
>> named in the silkscreen labels on the bottom of the PocketBeagle?
> 
> Yes,
> 
>> 
>> So far this appears to be the case.  Any exceptions?
> 
> If not, let me know. ;) So we can fix it..

48 should be labeled 44. 

SPI1 is CS1, not CS0 (silk screen doesn’t say). 


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

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

[beagleboard] Re: How to run programms automatically at boot up in beaglebone black

2017-10-31 Thread Mala Dies 
Here: 
https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/doc/run_config-pin_during_startup.md

or...

Here: 
https://learn.adafruit.com/running-programs-automatically-on-your-tiny-computer/systemd-writing-and-enabling-a-service?view=all#systemd-writing-and-enabling-a-service

Seth

P.S. If you need anything else, type a message back to someone.

On Monday, October 30, 2017 at 8:08:35 AM UTC-5, Ahmad Fatehi wrote:
>
> Hello, I have three programms that should be run after booting up the 
> beagle bone black. But now I want these programms run automatically after 
> boot up. I use debian, I made a script that contained 3 commands to run 
> that 3 programms but What should I do so as this script runs automatically 
> after boot up?!
>

-- 
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/10ae4fa5-4283-4c19-af5c-b1abb8c7f97b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Pocket Beagle SPI1 ChipSelect on silkscreen is not CS0 but CS1

2017-10-31 Thread Robert Nelson 
On Tue, Oct 31, 2017 at 1:41 PM, Graham  wrote:
> Robert:
>
> Are the default device tree pinmux connections for the PocketBeagle the
> functions
> named in the silkscreen labels on the bottom of the PocketBeagle?

Yes,

>
> So far this appears to be the case.  Any exceptions?

If not, let me know. ;) So we can fix it..

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

Re: [beagleboard] Pocket Beagle SPI1 ChipSelect on silkscreen is not CS0 but CS1

2017-10-31 Thread Graham 
Robert:

Are the default device tree pinmux connections for the PocketBeagle the 
functions 
named in the silkscreen labels on the bottom of the PocketBeagle?

So far this appears to be the case.  Any exceptions?

--- Graham

==

On Monday, October 30, 2017 at 11:02:56 PM UTC-5, Henner Zeller wrote:
>
> On 4 October 2017 at 06:52, Robert Nelson  > wrote: 
> > On Wed, Oct 4, 2017 at 1:28 AM, Henner Zeller  > wrote: 
> >> Hi, 
> >> Little heads-up: I just spent an hour or so to realize that the simple 
> 'CS' 
> >> (ChipSelect) printed on the silkscreen for SPI1 bus on the PocketBeagle 
> is 
> >> not CS0 as I expected, but CS1. So this is actually bus /dev/spidev2.1 
> >> 
> >> Not sure if this was intended, but if it is, it should probably be 
> marked on 
> >> the silk-screen as CS1 to avoid future confusion; I can send a pull 
> request 
> >> for the board (in general, even CS0 should be marked as such) 
> >> 
> >> If it is _not_ intended, the am335x-pocketbeagle.dts would need to be 
> >> changed before capes start assuming this is CS1 (around line 389 
> Jason). 
> > 
> > HI Henner, 
> > 
> > I've noticed this to while doing the overlays: 
> > 
> > SPI1 CS1 is used as CS 
> > 
> > 
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-SPI1-ETH-CLICK.dts#L83
>  
> > 
> > SPI0 CS0 is used as CS 
> > 
> > 
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-SPI0-ETH-CLICK.dts#L83
>  
> > 
> > I haven't looked to closely, (just let my automated script setup the 
> > pinmux's).. But if SPI1 (CS0) and SPI0 (CS1) is not on the header, we 
> > should remove them from the base tree 
>
> Yes, this would certainly less confusing to leave out the 
> non-available chip-selects in the /dev/spidev* devices. 
>
> Is there a reason why SPI0 shows up as /dev/spidev1.* and SPI1 as 
> /dev/spidev2.* ? This does look like an off-by-one. Is this 
> intentional ? 
>
> Thanks, 
>   Henner. 
>

-- 
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/ed6ad773-0550-4e46-bb30-d5f49fd4d752%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Fwd: beaglebone problem. no idea who to contact

2017-10-31 Thread evilwulfie 
I would contact the seller of the bone you bought.

On 10/31/2017 10:08 AM, Sajo Ojas wrote:
>
> -- Forwarded message -
> From: Jason Kridner  >
> Date: Tue, Oct 31, 2017 at 8:57 AM
> Subject: Re: beaglebone problem. no idea who to contact
> To: Sajo Ojas >
>
>
> Send mail to beagleboard@googlegroups.com
> . 
>
> On Mon, Oct 30, 2017 at 9:42 PM Sajo Ojas  > wrote:
>
> Hi,
>
> I recently bought a beaglebone black rev c 4gb off of ebay like a
> week ago and I have problems where I've had to reflash the debian
> os like 5 times so far. It has kernal panics often and it just
> crashes a lot ever since day 1. And I haven't even gotten to
> overclock it yet so it can't be that. I think the hardware has
> some problem where it corrupts the storage or something because
> when I plug it back to my computer, sometimes it can't read it.  
>
> I can't figure out if there is even a support page to get help
> with this issue. I tried 2 different linux versions on 2 different
> samsung sd cards. 8gb and 64gb. Although the 8gb was far more
> stable, it still happens. Ebay seller was no help at all and said
> it was my fault. This is my first beaglebone but I have used many
> raspberry pis before so I know how to use them and it's not my fault.
>
> How can I solve this issue?
>
> -Nina
>
> -- 
> https://beagleboard.org/about
> -- 
> 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/CACdP%3D8Hnb_kbCqsoPHz90aQ30aXihuQ6sGMefYeaSV9uR5ZcHA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d7bde1e7-97dc-3397-38b6-8fa3dd092178%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is it a bug? control flow instruction of PRU does not make right comparison with negative number

2017-10-31 Thread Lingwei Zhan 
Thank you Henner. Since we can only interpret the subtraction result 
correctly when we know its sign, we always need first compare a and b 
(assuming a and b are positive and we do a-b) to know which is greater 
before we do a subtraction.

lingwei

On Tuesday, October 31, 2017 at 12:33:03 PM UTC-4, Henner Zeller wrote:
>
> On 31 October 2017 at 08:49,   wrote: 
> > Thank you Charles. Is it a known issue only for control flow logic? When 
> I 
> > use MOV command to save a negative number (MOV r1, -1), then save r1 
> into 
> > shared RAM, then into a txt file, I do see -1 is saved into the txt file 
> > correctly. 
>
> This always works but has nothing to do with the PRU. 
>
> You can substract a larger value from an unsigned value, which then 
> gets wrapped around; you can then _interpret_ the bit-pattern as a 
> signed value in two-complement and get the expected negative number. 
> This is what you did in this case. 
> This is just a property of how the two-complement encoding works. 
>
> -h 
>
> > 
> > On Tuesday, October 31, 2017 at 9:13:31 AM UTC-4, Charles Steinkuehler 
> > wrote: 
> >> 
> >> On 10/30/2017 4:53 PM, zlw...@gmail.com wrote: 
> >> > I am trying to use QBLT to compare two numbers and found out when one 
> >> > number is negative, the QBLT logic does not seem make right 
> comparison. 
> >> > In 
> >> > the following code, before QBLT, r3 =1-4 = -3, and r2 = 10, so r3 < 
> r2, 
> >> > then the code should execute MOV r3, -1. However, when I run this 
> macro, 
> >> > r3 
> >> > is set to 1. 
> >> > Anyone notices this issue? Any idea how to fix it? 
> >> 
> >> This is a known issue, the PRU supports *ONLY* unsigned integers. 
> >> 
> >> Write your code properly for unsigned data types and you will not have 
> >> any problems. 
> >> 
> >> -- 
> >> Charles Steinkuehler 
> >> cha...@steinkuehler.net 
> > 
> > -- 
> > 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/859b4ea7-a3a6-430d-a715-b5d24ccc6a09%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/a5f31638-a696-4ae6-b326-7eb2559c6fbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Fwd: beaglebone problem. no idea who to contact

2017-10-31 Thread Sajo Ojas 
-- Forwarded message -
From: Jason Kridner 
Date: Tue, Oct 31, 2017 at 8:57 AM
Subject: Re: beaglebone problem. no idea who to contact
To: Sajo Ojas 


Send mail to beagleboard@googlegroups.com.

On Mon, Oct 30, 2017 at 9:42 PM Sajo Ojas  wrote:

> Hi,
>
> I recently bought a beaglebone black rev c 4gb off of ebay like a week ago
> and I have problems where I've had to reflash the debian os like 5 times so
> far. It has kernal panics often and it just crashes a lot ever since day 1.
> And I haven't even gotten to overclock it yet so it can't be that. I think
> the hardware has some problem where it corrupts the storage or something
> because when I plug it back to my computer, sometimes it can't read it.
>
> I can't figure out if there is even a support page to get help with this
> issue. I tried 2 different linux versions on 2 different samsung sd cards.
> 8gb and 64gb. Although the 8gb was far more stable, it still happens. Ebay
> seller was no help at all and said it was my fault. This is my first
> beaglebone but I have used many raspberry pis before so I know how to use
> them and it's not my fault.
>
> How can I solve this issue?
>
> -Nina
>
-- 
https://beagleboard.org/about

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

Re: [beagleboard] Is it a bug? control flow instruction of PRU does not make right comparison with negative number

2017-10-31 Thread Henner Zeller 
On 31 October 2017 at 08:49,   wrote:
> Thank you Charles. Is it a known issue only for control flow logic? When I
> use MOV command to save a negative number (MOV r1, -1), then save r1 into
> shared RAM, then into a txt file, I do see -1 is saved into the txt file
> correctly.

This always works but has nothing to do with the PRU.

You can substract a larger value from an unsigned value, which then
gets wrapped around; you can then _interpret_ the bit-pattern as a
signed value in two-complement and get the expected negative number.
This is what you did in this case.
This is just a property of how the two-complement encoding works.

-h

>
> On Tuesday, October 31, 2017 at 9:13:31 AM UTC-4, Charles Steinkuehler
> wrote:
>>
>> On 10/30/2017 4:53 PM, zlw...@gmail.com wrote:
>> > I am trying to use QBLT to compare two numbers and found out when one
>> > number is negative, the QBLT logic does not seem make right comparison.
>> > In
>> > the following code, before QBLT, r3 =1-4 = -3, and r2 = 10, so r3 < r2,
>> > then the code should execute MOV r3, -1. However, when I run this macro,
>> > r3
>> > is set to 1.
>> > Anyone notices this issue? Any idea how to fix it?
>>
>> This is a known issue, the PRU supports *ONLY* unsigned integers.
>>
>> Write your code properly for unsigned data types and you will not have
>> any problems.
>>
>> --
>> Charles Steinkuehler
>> cha...@steinkuehler.net
>
> --
> 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/859b4ea7-a3a6-430d-a715-b5d24ccc6a09%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/CAEQqtJzcZLifkoKKz2ney2Q%3DBhj8vOaCoLO--QanUeLGuiUGww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is it a bug? control flow instruction of PRU does not make right comparison with negative number

2017-10-31 Thread zlw8844 
Thank you Charles. Is it a known issue only for control flow logic? When I 
use MOV command to save a negative number (MOV r1, -1), then save r1 into 
shared RAM, then into a txt file, I do see -1 is saved into the txt file 
correctly.

On Tuesday, October 31, 2017 at 9:13:31 AM UTC-4, Charles Steinkuehler 
wrote:
>
> On 10/30/2017 4:53 PM, zlw...@gmail.com  wrote: 
> > I am trying to use QBLT to compare two numbers and found out when one 
> > number is negative, the QBLT logic does not seem make right comparison. 
> In 
> > the following code, before QBLT, r3 =1-4 = -3, and r2 = 10, so r3 < r2, 
> > then the code should execute MOV r3, -1. However, when I run this macro, 
> r3 
> > is set to 1. 
> > Anyone notices this issue? Any idea how to fix it? 
>
> This is a known issue, the PRU supports *ONLY* unsigned integers. 
>
> Write your code properly for unsigned data types and you will not have 
> any problems. 
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
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/859b4ea7-a3a6-430d-a715-b5d24ccc6a09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Overlays and 4.14 Linux kernel for CAN

2017-10-31 Thread Tracy Smith 
We are using a USB device for the CAN so we are using the AM3358 and
no CAPE and we are not using the P9 header.  The device is an OEM
version and similar to the kvaser USB/CAN connectors.

https://www.kvaser.com/product/kvaser-usb-hs-ii-hsls/

1) Do you see any kernel issues using this configuration once we have
set up the device tree for CAN0/CAN1 pins below?

CAN0 RX is D17
CAN0 TX is D18
CAN1 RX is E17
CAN1 TX is E18

2) Can we access the E17/E18 or D17/D18 through the P9 header?

3)  Is there a particular reason to use the P9 header instead of USB
for CAN (speed not a concern for us)?

4)  Any additional kernel support required for using CAN over USB?
https://www.kvaser.com/product/kvaser-usb-hs-ii-hsls/

On Mon, Oct 30, 2017 at 6:58 PM, Robert Nelson  wrote:
>
>
> On Mon, Oct 30, 2017 at 5:39 PM, Tracy Smith  wrote:
>>
>> I see. Thanks Robert.  The P9 is the BBB expansion header?  If so, we are
>> not using an expansion header and we don't have P9 correct?  So, we need to
>> pinmux the following:
>>
>> CAN0 RX is D17
>> CAN0 TX is D18
>> CAN1 RX is E17
>> CAN1 TX is E18
>>
>> per our pinmux file using the TI PinMux tool to avoid conflicts.
>>
>
> Correct, P9_xy, are on the P9 header,
>
> AM33XX_IOPAD(0x0978, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_20:
> uart1_ctsn.d_can0_tx */
> AM33XX_IOPAD(0x097c, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_19:
> uart1_rtsn.d_can0_rx */
>
> AM33XX_IOPAD(0x0980, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_26:
> uart1_rxd.dcan1_tx */
> AM33XX_IOPAD(0x0984, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_24:
> uart1_txd.dcan1_rx */
>
> Sorry, you'll have to decode the iopad values for the pad names, i hardly
> look a the pad names..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/



-- 
Confidentiality notice: This e-mail message, including any
attachments, may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), please
immediately notify the sender and delete this e-mail message.

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

Re: [beagleboard] Is it a bug? control flow instruction of PRU does not make right comparison with negative number

2017-10-31 Thread Charles Steinkuehler 
On 10/30/2017 4:53 PM, zlw8...@gmail.com wrote:
> I am trying to use QBLT to compare two numbers and found out when one 
> number is negative, the QBLT logic does not seem make right comparison. In 
> the following code, before QBLT, r3 =1-4 = -3, and r2 = 10, so r3 < r2, 
> then the code should execute MOV r3, -1. However, when I run this macro, r3 
> is set to 1.
> Anyone notices this issue? Any idea how to fix it?

This is a known issue, the PRU supports *ONLY* unsigned integers.

Write your code properly for unsigned data types and you will not have
any problems.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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/ecf0f332-a2bc-5119-904b-30d5c336f351%40steinkuehler.net.
For more options, visit https://groups.google.com/d/optout.