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

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 r

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

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 t

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

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

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

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-4

[beagleboard] Re: u-boot support for pins

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) | RX

[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), b

[beagleboard] u-boot support for pins

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

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

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-

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

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 l

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

> 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, > >> >

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

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 Se

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

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.

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

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

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

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

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

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-

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

-- 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 beagle

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

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 b

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

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 Stei

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

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 configurati

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

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 ex