from:"Dean"

[beagleboard] Re: UART1 and UART2 TX not working on custom cape

2017-04-11 Thread Dean Claxton

Oh - I'm using the latest Debian build from the 19th March 2017.

Cheers,
Dean

On Tuesday, 11 April 2017 16:00:53 UTC+10, Dean Claxton wrote:
>
> Hi,
>
> I'm building a custom cape that uses a number of on-chip peripherals 
> including UART1,2,4,5, SPI1, I2C1, I2C2 (cape eeprom), ADC, plus a number 
> of GPIO.
>
> At the moment I'm in the process of testing the first hardware revision of 
> the cape, and creating the driver overlay - I'd like to be able to include 
> everything in the one overlay.
>
> So far most things are working but I do have a couple of issues. For some 
> reason only RX is working on UART1 and UART2 - UART4 and 5 are working 
> properly for both RX and TX.
>
> Is there something I am missing with UART1 and 2 in regard to TX? The guts 
> of my overlay is shown below  :
>
>
>
> exclusive-use = 
> /* the pin header uses */
> "P8.7",/* gpio2_2   GPIO1 */
> "P8.8", /* gpio2_3   5V_LOAD1_EN */
> "P8.9", /* gpio2_5 GPIO2 */
> "P8.10", /* gpio2_4 12V_LOAD4_EN */
> "P8.11", /* gpio1_13 GPIO3 */
> "P8.12", /* gpio1_12 12V_LOAD3_EN */
> "P8.13", /* gpio0_23   GPIO4 */
> "P8.14", /* gpio0_26 12V_LOAD2_EN */
> "P8.15", /* gpio1_15 GPIO5 */
> "P8.16", /* gpio1_14 12V_LOAD1_EN */
> "P8.17", /* gpio0_27   GPIO6 */
> "P8.26", /* gpio1_29 ONE-WIRE */
> "P8.37", /* uart5_txd */
> "P8.38", /* uart5_rxd */
> "P9.11", /* uart4_rxd_mux2 */
> "P9.12", /* gpio1_28 LCD_DC */
> "P9.13", /* uart4_txd_mux2 */
> "P9.14", /* gpio1_18 LCD_BKLT_EN */
> "P9.16", /* gpio1_19 LCD_RESET */
> "P8.17", /* i2c1_scl */
> "P8.18", /* i2c1_sda */
> "P9.19", /* i2c2_scl */
> "P9.20", /* i2c2_sda */
> "P9.21", /* uart2_txd */
> "P9.22", /* uart2_rxd */
> "P9.24", /* uart1_txd */
> "P9.26", /* uart1_rxd */
> "P9.27", /* gpio3_19 SOLAR_ENABLE */
> "P9.28", /* spi1_cs0 */
> "P9.29", /* spi1_d0 */
> "P9.30", /* spi1_d1 */
> "P9.31", /* spi1_sclk */
> "P9.33", /* AIN4 SOLAR_VOLTAGE */
> "P9.35", /* AIN6 SOLAR_CURRENT */
> "P9.36", /* AIN5 AIN5 */
> "P9.37", /* AIN2 SUPPLY_CURRENT */
> "P9.38", /* AIN3 AIN3 */
> "P9.39", /* AIN0 SUPPLY_VOLTAGE */
> "P9.40", /* AIN1 AIN1 */
> 
> /* the hardware ip uses */
> "gpio2_2",
> "gpio2_3",
> "gpio2_5",
> "gpio2_4",
> "gpio1_13",
> "gpio1_12",
> "gpio0_23",
> "gpio0_26",
> "gpio1_15",
> "gpio1_14",
> "gpio0_27",
> "gpio1_29",
> "uart5",
> "uart4",
> "gpio1_28",
> "gpio1_18",
> "gpio1_19",
> "i2c1",
> "i2c2",
> "uart2",
> "uart1",
> "gpio3_19",
> "spi1",
> "tscadc";
>
> fragment@0 {
> target = <_pinmux>;
> __overlay__ {
> bb_spi1_pins: pinmux_bb_spi1_pins {
> pinctrl-single,pins = <
> 0x190 0x33 /* mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3 */
> 0x194 0x33 /* mcasp0_fsx.spi1_d0, INPUT_PULLUP | MODE3 */
> 0x198 0x13 /* mcasp0_axr0.spi1_d1, OUTPUT_PULLUP | MODE3 */
> 0x19c 0x13 /* mcasp0_ahclkr.spi1_cs0, OUTPUT_PULLUP | MODE3 */
> 0x164 0x12 /* eCAP0_in_PWM0_out.spi1_cs1 OUTPUT_PULLUP | MODE2 */
> >;
> };
> bb_i2c1_pins: pinmux_bb_i2c1_pins {
> pinctrl-single,pins = <
> 0x15c 0x72 /* spi0_cs0.i2c1_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
> 0x158 0x72 /* spi0_d1.i2c1_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
> >;
> };
> bb_i2c2_pins: pinmux_bb_i2c2_pins {
> pinctrl-single,pins = <
> 0x17c 0x73 /* uart1_rtsn.i2c2_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
> 0x178 0x73 /* uart1_ctsn.i2c2_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
> >;
> };
> bb_uart1_pins: pinmux_bb_uart1_pins {
> pinctrl-single,pins = <
> 0x184 0x00 /* P9.24 uart1_txd.uart1_txd | MODE0 OUTPUT */
> 0x180 0x20 /* P9.26 uart1_rxd.uart1_rxd | MODE0 INPUT */
> >;
> };
> bb_uart2_pins: pinmux_bb_uart2_pins {
> pinctrl-single,pins = <
> 0x150 0x21 /* P9.22 spi0_sclk.uart2_rxd | MODE1 INPUT */
> 0x154 0x01 /* P9.21 spi0_d0.uart2_txd | MODE1 OUTPUT */
> >;
> };
> bb_uart4_pins: pinmux_bb_uart4_pins {
> pinctrl-single,pins = <
> 0x070 0x26 /* P9.11 gpmc_wait0.uart4_rxd | MODE6 INPUT */
> 0x074 0x06 /* P9.13 gpmc_wpn.uart4_txd | MODE6 OUTPUT

[beagleboard] UART1 and UART2 TX not working on custom cape

2017-04-11 Thread Dean Claxton

Hi,

I'm building a custom cape that uses a number of on-chip peripherals 
including UART1,2,4,5, SPI1, I2C1, I2C2 (cape eeprom), ADC, plus a number 
of GPIO.

At the moment I'm in the process of testing the first hardware revision of 
the cape, and creating the driver overlay - I'd like to be able to include 
everything in the one overlay.

So far most things are working but I do have a couple of issues. For some 
reason only RX is working on UART1 and UART2 - UART4 and 5 are working 
properly for both RX and TX.

Is there something I am missing with UART1 and 2 in regard to TX? The guts 
of my overlay is shown below  :



exclusive-use = 
/* the pin header uses */
"P8.7",/* gpio2_2   GPIO1 */
"P8.8", /* gpio2_3   5V_LOAD1_EN */
"P8.9", /* gpio2_5 GPIO2 */
"P8.10", /* gpio2_4 12V_LOAD4_EN */
"P8.11", /* gpio1_13 GPIO3 */
"P8.12", /* gpio1_12 12V_LOAD3_EN */
"P8.13", /* gpio0_23   GPIO4 */
"P8.14", /* gpio0_26 12V_LOAD2_EN */
"P8.15", /* gpio1_15 GPIO5 */
"P8.16", /* gpio1_14 12V_LOAD1_EN */
"P8.17", /* gpio0_27   GPIO6 */
"P8.26", /* gpio1_29 ONE-WIRE */
"P8.37", /* uart5_txd */
"P8.38", /* uart5_rxd */
"P9.11", /* uart4_rxd_mux2 */
"P9.12", /* gpio1_28 LCD_DC */
"P9.13", /* uart4_txd_mux2 */
"P9.14", /* gpio1_18 LCD_BKLT_EN */
"P9.16", /* gpio1_19 LCD_RESET */
"P8.17", /* i2c1_scl */
"P8.18", /* i2c1_sda */
"P9.19", /* i2c2_scl */
"P9.20", /* i2c2_sda */
"P9.21", /* uart2_txd */
"P9.22", /* uart2_rxd */
"P9.24", /* uart1_txd */
"P9.26", /* uart1_rxd */
"P9.27", /* gpio3_19 SOLAR_ENABLE */
"P9.28", /* spi1_cs0 */
"P9.29", /* spi1_d0 */
"P9.30", /* spi1_d1 */
"P9.31", /* spi1_sclk */
"P9.33", /* AIN4 SOLAR_VOLTAGE */
"P9.35", /* AIN6 SOLAR_CURRENT */
"P9.36", /* AIN5 AIN5 */
"P9.37", /* AIN2 SUPPLY_CURRENT */
"P9.38", /* AIN3 AIN3 */
"P9.39", /* AIN0 SUPPLY_VOLTAGE */
"P9.40", /* AIN1 AIN1 */

/* the hardware ip uses */
"gpio2_2",
"gpio2_3",
"gpio2_5",
"gpio2_4",
"gpio1_13",
"gpio1_12",
"gpio0_23",
"gpio0_26",
"gpio1_15",
"gpio1_14",
"gpio0_27",
"gpio1_29",
"uart5",
"uart4",
"gpio1_28",
"gpio1_18",
"gpio1_19",
"i2c1",
"i2c2",
"uart2",
"uart1",
"gpio3_19",
"spi1",
"tscadc";

fragment@0 {
target = <_pinmux>;
__overlay__ {
bb_spi1_pins: pinmux_bb_spi1_pins {
pinctrl-single,pins = <
0x190 0x33 /* mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3 */
0x194 0x33 /* mcasp0_fsx.spi1_d0, INPUT_PULLUP | MODE3 */
0x198 0x13 /* mcasp0_axr0.spi1_d1, OUTPUT_PULLUP | MODE3 */
0x19c 0x13 /* mcasp0_ahclkr.spi1_cs0, OUTPUT_PULLUP | MODE3 */
0x164 0x12 /* eCAP0_in_PWM0_out.spi1_cs1 OUTPUT_PULLUP | MODE2 */
>;
};
bb_i2c1_pins: pinmux_bb_i2c1_pins {
pinctrl-single,pins = <
0x15c 0x72 /* spi0_cs0.i2c1_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
0x158 0x72 /* spi0_d1.i2c1_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
>;
};
bb_i2c2_pins: pinmux_bb_i2c2_pins {
pinctrl-single,pins = <
0x17c 0x73 /* uart1_rtsn.i2c2_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
0x178 0x73 /* uart1_ctsn.i2c2_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
>;
};
bb_uart1_pins: pinmux_bb_uart1_pins {
pinctrl-single,pins = <
0x184 0x00 /* P9.24 uart1_txd.uart1_txd | MODE0 OUTPUT */
0x180 0x20 /* P9.26 uart1_rxd.uart1_rxd | MODE0 INPUT */
>;
};
bb_uart2_pins: pinmux_bb_uart2_pins {
pinctrl-single,pins = <
0x150 0x21 /* P9.22 spi0_sclk.uart2_rxd | MODE1 INPUT */
0x154 0x01 /* P9.21 spi0_d0.uart2_txd | MODE1 OUTPUT */
>;
};
bb_uart4_pins: pinmux_bb_uart4_pins {
pinctrl-single,pins = <
0x070 0x26 /* P9.11 gpmc_wait0.uart4_rxd | MODE6 INPUT */
0x074 0x06 /* P9.13 gpmc_wpn.uart4_txd | MODE6 OUTPUT */
>;
};
bb_uart5_pins: pinmux_bb_uart5_pins {
pinctrl-single,pins = <
0x0c4 0x24 /* P8.38 lcd_data8.uart5_rxd | MODE4 INPUT */
0x0c0 0x04 /* P8.37 lcd_data9.uart5_txd | MODE4 OUTPUT */
>;
};
bb_gpio_pins: pinmux_bb_gpio_pins {
pinctrl-single,pins = <
0x090 0x27 /* P8.7 gpmc_advn_ale.gpio2_2 RX_ENABLE | MODE7 */
0x094 0x07 /* P8.8 gpmc_oen_ren.gpio2_3   MODE7 */
0x09c 0x27 /* P8.9 gpmc_ben0_cle.gpio2_5 RX_ENABLE | MODE7 */
0x098 0x07 /* P8.10 gpmc_wen.gpio2_4 MODE7 */
0x034 0x27 /* P8.11 gpmc_ad13.gpio1_13 RX_ENABLE | MODE7 */
0x030 0x07 /* P8.12 gpmc_ad12.gpio1_12 MODE7 */
0x024 0x27 /* P8.13 gpmc_ad9.gpio0_23   RX_ENABLE | MODE7 */
0x028 0x07 /* P8.14 gpmc_ad10.gpio0_26 MODE7 */
0x03c 0x27 /* P8.15 gpmc_ad15.gpio1_15 RX_ENABLE | MODE7 */
0x038 0x07 /* P8.16 gpmc_ad14.gpio1_14 MODE7 */
0x02c 0x27 /* P8.17 gpmc_ad11.gpio0_27   RX_ENABLE | MODE7 */
0x07c 0x37 /* P8.26 gpmc_csn0.gpio1_29 RX_ENABLE | MODE7 */
0x078 0x07 /* P9.12 gpmc_ben1.gpio1_28 MODE7 */
0x048 0x07 /* P9.14 gpmc_a2.gpio1_18 MODE7 */
0x04c 0x07 /* P9.16 gpmc_a3.gpio1_19 MODE7 */
0x1a4 0x07 /* P9.27 mcasp0_fsr.gpio3_19 MODE7 */
>;
};
bb_onewire_pins: pinmux_bb_onewire_pins {
 pinctrl-single,pins =  <
0x7c 0x37 /* gpio1_29, RX_ENABLE | MODE 7 */ >;
 
 };
};
};

fragment@1 {
target = <>; /* spi1 is numbered correctly */
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_spi1_pins>;

Re: [beagleboard] Re: UART2 on Beaglebone Black Rev C - What changed from Debian 7 to Debian 8?

2017-04-06 Thread Dean Claxton

Thanks Pak,
I've posted a new topic specific to my configuration - I can receive on
uart1 and 2 but no transmit. Uart5 and 5 are all good.

Cheers,
Dean

On 7 Apr 2017 12:55 AM, <deanclax...@gmail.com> wrote:

Hi,

I am experiencing a similar issue on 4.4.54 - I am attempting to use uarts
1,2,4 and 5 on a custom cape (loading a custom overlay file on startup) -
uarts 4 and 5 are both working (RX and TX). Uarts 1 and 2 however are
working for RX only.

Did you make any further progress with your issue?

Cheers,
Dean

On Wednesday, 8 March 2017 11:49:14 UTC+10, pak...@gmail.com wrote:
>
> Further testing shows that there is a conflict during bootup
>
> [2.798087] bone_capemgr bone_capemgr: Using override eeprom data at
> slot 8
> [2.798124] bone_capemgr bone_capemgr: slot #8: 'Override Board
> Name,00A0,Override Manuf,BB-ADC'
> [2.799100] bone_capemgr bone_capemgr: initialized OK.
> [2.807649] PM: bootloader does not support rtc-only!
> [2.809270] omap_rtc 44e3e000.rtc: setting system clock to 2016-09-01
> 10:26:24 UTC (1472725584)
> [2.809354] of_cfs_init
> [2.809539] of_cfs_init: OK
> [2.813323] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 184,
> base_baud = 300) is a 8250
> [2.818299] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 186,
> base_baud = 300) is a 8250
> [2.819877] *pinctrl-single 44e10800.pinmux: pin 44e10954.0 already
> requested by 481a8000.serial; cannot claim for 48024000.serial*
> [2.819962] pinctrl-single 44e10800.pinmux: pin-85 (48024000.serial)
> status -22
> [2.820010] pinctrl-single 44e10800.pinmux: could not request pin 85
> (44e10954.0) from group pinmux_bb_uart2_pins  on device pinctrl-single
> [2.820064] omap8250 48024000.serial: Error applying setting, reverse
> things back
> [2.821135] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 187,
> base_baud = 300) is a 8250
> [2.823309] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 188,
> base_baud = 300) is a 8250
> [2.824063] bone_capemgr bone_capemgr: slot #4: dtbo
> 'BB-UART1-00A0.dtbo' loaded; overlay id #0
> [2.824367] bone_capemgr bone_capemgr: slot #7: dtbo
> 'BB-UART5-00A0.dtbo' loaded; overlay id #3
> [2.824537] bone_capemgr bone_capemgr: slot #6: dtbo
> 'BB-UART4-00A0.dtbo' loaded; overlay id #1
> [2.824719] bone_capemgr bone_capemgr: slot #5: dtbo
> 'BB-UART2-00A0.dtbo' loaded; overlay id #2
> [2.829155] bone_capemgr bone_capemgr: slot #8: dtbo 'BB-ADC-00A0.dtbo'
> loaded; overlay id #4
>
> I have tried various combinations of BB-UART1, BB-UART2, etc and it works
> if I just use BB-UART1 and BB-UART2 but as soon as I include BB-UART4 and
> BB-UART5 I see these messages.
>
> Does anyone else have any idea what's going on?
>
> Regards,
> Pak
>
>
> On Wednesday, March 8, 2017 at 12:17:52 AM UTC+11, pak...@gmail.com wrote:
>>
>> Hello Dominik,
>>
>> Did you resolve this issue? I am seeing the same thing at the moment
>> where the cape_mngr at boot up says it loaded the UARTs and the device
>> appear on /dev/ttyO* but I am unable to communicate with the attached
>> device. I am wondering if the fact that I am not seeing a pinmux_uart2_pins
>> in the pinctrl path has anything to do with it.
>>
>> Checking for: /uEnv.txt ...
>> Checking for: /boot.scr ...
>> Checking for: /boot/boot.scr ...
>> Checking for: /boot/uEnv.txt ...
>> gpio: pin 55 (gpio 55) value is 1
>> 1550 bytes read in 29 ms (51.8 KiB/s)
>> Loaded environment from /boot/uEnv.txt
>> Using: *dtb=am335x-boneblack-emmc-overlay.dtb* ...
>> Checking if uname_r is set in /boot/uEnv.txt...
>> gpio: pin 56 (gpio 56) value is 1
>> Running uname_boot ...
>> loading /boot/vmlinuz-4.4.52 ...
>> 8686800 bytes read in 504 ms (16.4 MiB/s)
>> loading /boot/dtbs/4.4.52/am335x-boneblack-emmc-overlay.dtb ...
>> 54478 bytes read in 160 ms (332 KiB/s)
>> loading /boot/initrd.img-4.4.52 ...
>> 4079584 bytes read in 267 ms (14.6 MiB/s)
>> debug: [root=UUID=0abe7613-556f-4720-918c-57548c139814 ro
>> rootfstype=ext4 rootwait fixrtc console=ttyS0,115200 coherent_pool=1M
>> init=/lib/systemd/systemd bone_capemgr.enable_partno=BB-
>> UART1,BB-UART2,BB-UA.
>> debug: [bootz 0x8200 0x8808:3e3fe0 0x8800] ...
>> Kernel image @ 0x8200 [ 0x00 - 0x848cd0 ]
>> ## Flattened Device Tree blob at 8800
>>Booting using the fdt blob at 0x8800
>>Loading Ramdisk to 8fc1c000, end 8fe0 ... OK
>>Loading Device Tree to 8fc0b000, end 8fc1b4cd ... OK
>>
>> Starting kernel ...
>>
>> [0.00] Kernel command line: 
>> root=UUID=0abe7613-556f-4720-918c-57548c139814

[beagleboard] Custom cape - issues with UART1, UART2

2017-04-06 Thread Dean Claxton

P9.16 gpmc_a3.gpio1_19 MODE7 */
0x1a4 0x07 /* P9.27 mcasp0_fsr.gpio3_19 MODE7 */
>;
};
bb_onewire_pins: pinmux_bb_onewire_pins {
 pinctrl-single,pins =  <
0x7c 0x37 /* gpio1_29, RX_ENABLE | MODE 7 */ >;
 
 };
};
};

fragment@1 {
target = <>; /* spi1 is numbered correctly */
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_spi1_pins>;

#address-cells = <1>;
#size-cells = <0>;

/* add any spi devices connected here */
/* note that you can do direct SPI via spidev now */
spi1_0{
#address-cells = <1>;
#size-cells = <0>;
compatible = "spidev";
reg = <0>;
spi-max-frequency = <1600>;
spi-cpol;
spi-cpha;  
};
spi1_1{
#address-cells = <1>;
#size-cells = <0>;
compatible = "spidev";
reg = <1>;
spi-max-frequency = <1600>;
spi-cpol;
spi-cpha;
};
};
};

fragment@2 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_i2c1_pins>;

/* this is the configuration part */
clock-frequency = <10>; 

#address-cells = <1>;
#size-cells = <0>;

/* add any i2c devices on the bus here */

};
};
fragment@3 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_i2c2_pins>;

/* this is the configuration part */
clock-frequency = <10>; 

#address-cells = <1>;
#size-cells = <0>;

/* add any i2c devices on the bus here */

};
};
fragment@4 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_uart1_pins>;
};
};
fragment@5 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_uart2_pins>;
};
};
fragment@6 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_uart4_pins>;
};
};
fragment@7 {
target = <>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_uart5_pins>;
};
};
fragment@8 {
target = <>;
__overlay__ {

status = "okay";
adc {
ti,adc-channels = <0 1 2 3 4 5 6>;
ti,chan-step-avg = <0x16 0x16 0x16 0x16 0x16 0x16 0x16>;
ti,chan-step-opendelay = <0x98 0x98 0x98 0x98 0x98 0x98 0x98>;
ti,chan-step-sampledelay = <0x0 0x0 0x0 0x0 0x0 0x0 0x0>; 
};
};
};
fragment@9 {
target = <>;
__overlay__ {
onewire@0 {
status  = "okay";
compatible  = "w1-gpio";
pinctrl-names   = "default";
pinctrl-0   = <_onewire_pins>;
gpios = < 29 0>;
};
};
};


My dtbo loads on boot and the cape is shown in slot 0 which is where my 
eeprom is addressed. I've tested the adc, some gpio, one wire and uarts so 
far. Uart4 and 5 are both operating correctly, however uart1 and 2 are not 
transmitting - they are receiving ok.

I initially thought I'd made an error with the pin mux but it looks ok. I 
haven't probed the board yet with a scope, but physically the board looks 
ok (solder joints etc).

Is there a gotcha on the TX for uart1 and uart2?

Also in regard to the cape eeprom - is the pin usage section actually used 
at all? Perhaps I need to revisit my eeprom contents if that section is 
actually processed - or is it only used when a second cape is found and it 
uses the eeprom pin usage section to look for pin clashes?


Cheers,
Dean

-- 
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/dac9ce0e-2b55-48d6-b01f-5f3671d18de6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 192.168.7.2 works on SD card, but not from eMMC

2017-03-15 Thread Dean Gouramanis

I am having the same symptom with BBB rC. I am trying to install a -bone 
mainline kernel. 

I tried 4 of the latest images. When I use a ti kernel ssh works. As soon 
as I install a -bone kernel 192.168.7.2 stops working.

I installed identical images on uSD/eMMC. Works ok from SD card. eMMc 
conflicts with ssh. 

My Linux PC ifconfig says:

enp0s29f7u7u4: flags=4163  mtu 1500
inet6 fe80::6b49:8ea0:67b:599d  prefixlen 64  scopeid 0x20
ether 04:a3:16:ec:bb:c9  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 24  bytes 7714 (7.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 


BeagleBone ifconfig says:

usb0  Link encap:Ethernet  HWaddr 04:a3:16:ec:bb:c0   
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252 
  inet6 addr: fe80::6a3:16ff:feec:bbc0/64 Scope:Link 
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
  RX packets:50 errors:0 dropped:0 overruns:0 frame:0 
  TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 
  collisions:0 txqueuelen:1000  
  RX bytes:13512 (13.1 KiB)  TX bytes:12833 (12.5 KiB)

Install info is:

root@beaglebone:~# lsb_release -a 
> No LSB modules are available. 
> Distributor ID:Debian 
> Description:Debian GNU/Linux 8.4 (jessie) 
> Release:8.4 
> Codename:jessie
>


root@beaglebone:~# uname -a 
> Linux beaglebone 4.4.53-bone16 #1 Tue Mar 14 05:36:36 UTC 2017 armv7l 
> GNU/Lin
>

Is there a standard image for Beaglebone using a 4.x mainline kernel?

What is causing the problem?
 

On Friday, October 28, 2016 at 7:57:49 PM UTC-4, Gregg Harrington wrote:
>
> Hello Everyone,
>
> I am having an issue with my BeagleBone Black when I move the OS from the 
> SD card to the eMMC on board. Here are the steps I use and results, please 
> let me know if you see the problem.
>
> 1. Download the latest image from beagleboard.org
> 1a. Flash it to an SD card
> 2. Use the "power/user" button to boot the SD card via power adapter. 
> (however, it also boots from the SD card as long as it's just in there)
> 3. Connect the USB Cable, windows creates the 192.168.7.1 interface and I 
> can SSH to 192.168.7.2 and everything works fine. 
> 4. Reboot to check it, works fine again
> 5. Uncomment the flashing line in side of the /boot/uEnv.txt
>
> cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> 6. Reboot, watch the lights flash while it is flashing eMMC
> 7. Remove the SD card
> 8. Boot the beaglebone
> 9. Windows doesn't even make a sound like it normally does when attaching a 
> USB device and the BeagleBone Black is not available.
>
>
> If I reflash and go back, it starts working again as long as I boot from 
> the SD card. 
>
> As a secondary note, here is my df -h output. I am not sure if it is 
> booting correctly now the eMMC and because the SD card is in, it is working 
> properly.
>
> root@beaglebone:~# df -h
> Filesystem  Size  Used Avail Use% Mounted on
> udev 10M 0   10M   0% /dev
> tmpfs99M  8.4M   91M   9% /run
> /dev/mmcblk0p1  3.3G  3.0G   35M  99% /
> tmpfs   247M  4.0K  247M   1% /dev/shm
> tmpfs   5.0M  4.0K  5.0M   1% /run/lock
> tmpfs   247M 0  247M   0% /sys/fs/cgroup
> tmpfs50M 0   50M   0% /run/user/1000
> root@beaglebone:~# 
>
> Any thoughts or debugging steps would be greatly appreciated. 
>
> Cheers,
>
> Gregg
>
>

-- 
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/2c5cb0d3-9fc4-4b79-ba88-defc9b215711%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB/jessie/4.1.10-ti-r21 -- bone_capemgr: loader: failed to load slot-0 BB-SERIAL:00A0 (prio 0)

2017-01-02 Thread Dean Gouramanis

I solved the problem by installing the latest image from beaglebone.org. 
Now I can load capes no problem.

Thanks anyway. 


On Sunday, January 1, 2017 at 2:16:58 AM UTC-5, Dean Gouramanis wrote:
>
> I am having a similar problem as described above. I am trying to load a 
> custom cape. 
>
> I am trying to load a copy of BB-BONE-LCD4.dts. Eventually I plan to 
> modify this overlay to include an LCD panel, but for now i've *cloned the 
> dts file*, changed the part number to DOPTOCAPE1, and renamed the file 
> DOPTOCAPE1.dts
>
> I placed the file in /src/arm directory, then ran install.sh
>
> I cheked that DOPTOCAPE1.dtbo is now in /lib/firmware
>
> Then I made the changes in my uEnv.txt file, and rebooted.
>
> Here is debug from the boot process:
>
> [0.00] Kernel command line: console=ttyO0,115200n8 
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> capemgr.enable_partno=dev_OPTOCAPE 
> root=UUID=509a5094-05c2-4cf0-803d-945708cd72b5 ro rootfstype=ext4 rootwait 
> coherent_pool=1M quiet net.ifnames=0 
> [0.610669] bone-capemgr bone_capemgr.9: Baseboard: 
> 'A335BNLT,000C,3914BBBK2717' 
> [0.610691] bone-capemgr bone_capemgr.9: 
> compatible-baseboard=ti,beaglebone-black 
> [0.610729] bone-capemgr bone_capemgr.9: Skipping disabled cape with 
> part# BB-BONELT-HDMI 
> [0.610773] bone-capemgr bone_capemgr.9: Skipping disabled cape with 
> part# BB-BONELT-HDMIN 
> [0.641898] bone-capemgr bone_capemgr.9: slot #0: No cape found 
> [0.679000] bone-capemgr bone_capemgr.9: slot #1: No cape found 
> [0.716114] bone-capemgr bone_capemgr.9: slot #2: No cape found 
> [0.753223] bone-capemgr bone_capemgr.9: slot #3: No cape found 
> [0.759455] bone-capemgr bone_capemgr.9: slot #4: specific override 
> [0.759476] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 4 
> [0.759492] bone-capemgr bone_capemgr.9: slot #4: 
> 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' 
> [0.759565] bone-capemgr bone_capemgr.9: slot #5: specific override 
> [0.759582] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 5 
> [0.759595] bone-capemgr bone_capemgr.9: slot #5: 
> 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' 
> [0.759667] bone-capemgr bone_capemgr.9: slot #6: specific override 
> [0.759683] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 6 
> [0.759696] bone-capemgr bone_capemgr.9: slot #6: 
> 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' 
> [0.759755] bone-capemgr bone_capemgr.9: enabled_partno part_number 
> 'dev_OPTOCAPE', version 'N/A', prio '0' 
> [0.759768] bone-capemgr bone_capemgr.9: slot #7: generic override 
> [0.759779] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 7 
> [0.759792] bone-capemgr bone_capemgr.9: slot #7: 'Override Board 
> Name,00A0,Override Manuf,dev_OPTOCAPE' 
> [0.759896] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
> cape with part# BB-BONELT-HDMI 
> [0.759908] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
> cape with part# BB-BONELT-HDMIN 
> [0.760092] bone-capemgr bone_capemgr.9: loader: before slot-4 
> BB-BONE-EMMC-2G:00A0 (prio 1) 
> [0.760107] bone-capemgr bone_capemgr.9: loader: check slot-4 
> BB-BONE-EMMC-2G:00A0 (prio 1) 
> [0.760134] bone-capemgr bone_capemgr.9: initialized OK. 
> [0.762291] bone-capemgr bone_capemgr.9: loader: check slot-4 
> BB-BONE-EMMC-2G:00A0 (prio 1) 
> [0.764081] bone-capemgr bone_capemgr.9: loader: before slot-7 
> dev_OPTOCAPE:00A0 (prio 0) 
> [0.764094] bone-capemgr bone_capemgr.9: loader: check slot-7 
> dev_OPTOCAPE:00A0 (prio 0) 
> [0.764109] bone-capemgr bone_capemgr.9: loader: after slot-7 
> dev_OPTOCAPE:00A0 (prio 0) 
> [0.764124] bone-capemgr bone_capemgr.9: slot #7: Requesting part 
> number/version based 'dev_OPTOCAPE-00A0.dtbo 
> [0.764139] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 
> 'dev_OPTOCAPE-00A0.dtbo' for board-name 'Override Board Name', version 
> '00A0' 
> [1.239617] bone-capemgr bone_capemgr.9: failed to load firmware 
> 'dev_OPTOCAPE-00A0.dtbo' 
> [1.248179] bone-capemgr bone_capemgr.9: loader: failed to load slot-7 
> dev_OPTOCAPE:00A0 (prio 0) 
> [1.257645] bone-capemgr bone_capemgr.9: loader: check slot-4 
> BB-BONE-EMMC-2G:00A0 (prio 1) 
> [1.257662] bone-capemgr bone_capemgr.9: loader: after slot-4 
> BB-BONE-EMMC-2G:00A0 (prio 1) 
> [1.257685] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 
> 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0' 
> [1.257702] bone-capemgr bone_capemgr.9: slot #4: dtbo 
>

[beagleboard] Re: BBB/jessie/4.1.10-ti-r21 -- bone_capemgr: loader: failed to load slot-0 BB-SERIAL:00A0 (prio 0)

2016-12-31 Thread Dean Gouramanis

I am having a similar problem as described above. I am trying to load a 
custom cape. 

I am trying to load a copy of BB-BONE-LCD4.dts. Eventually I plan to modify 
this overlay to include an LCD panel, but for now i've *cloned the dts file*, 
changed the part number to DOPTOCAPE1, and renamed the file DOPTOCAPE1.dts

I placed the file in /src/arm directory, then ran install.sh

I cheked that DOPTOCAPE1.dtbo is now in /lib/firmware

Then I made the changes in my uEnv.txt file, and rebooted.

Here is debug from the boot process:

[0.00] Kernel command line: console=ttyO0,115200n8 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
capemgr.enable_partno=dev_OPTOCAPE 
root=UUID=509a5094-05c2-4cf0-803d-945708cd72b5 ro rootfstype=ext4 rootwait 
coherent_pool=1M quiet net.ifnames=0 
[0.610669] bone-capemgr bone_capemgr.9: Baseboard: 
'A335BNLT,000C,3914BBBK2717' 
[0.610691] bone-capemgr bone_capemgr.9: 
compatible-baseboard=ti,beaglebone-black 
[0.610729] bone-capemgr bone_capemgr.9: Skipping disabled cape with 
part# BB-BONELT-HDMI 
[0.610773] bone-capemgr bone_capemgr.9: Skipping disabled cape with 
part# BB-BONELT-HDMIN 
[0.641898] bone-capemgr bone_capemgr.9: slot #0: No cape found 
[0.679000] bone-capemgr bone_capemgr.9: slot #1: No cape found 
[0.716114] bone-capemgr bone_capemgr.9: slot #2: No cape found 
[0.753223] bone-capemgr bone_capemgr.9: slot #3: No cape found 
[0.759455] bone-capemgr bone_capemgr.9: slot #4: specific override 
[0.759476] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 4 
[0.759492] bone-capemgr bone_capemgr.9: slot #4: 
'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' 
[0.759565] bone-capemgr bone_capemgr.9: slot #5: specific override 
[0.759582] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 5 
[0.759595] bone-capemgr bone_capemgr.9: slot #5: 
'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' 
[0.759667] bone-capemgr bone_capemgr.9: slot #6: specific override 
[0.759683] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 6 
[0.759696] bone-capemgr bone_capemgr.9: slot #6: 
'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' 
[0.759755] bone-capemgr bone_capemgr.9: enabled_partno part_number 
'dev_OPTOCAPE', version 'N/A', prio '0' 
[0.759768] bone-capemgr bone_capemgr.9: slot #7: generic override 
[0.759779] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 7 
[0.759792] bone-capemgr bone_capemgr.9: slot #7: 'Override Board 
Name,00A0,Override Manuf,dev_OPTOCAPE' 
[0.759896] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
cape with part# BB-BONELT-HDMI 
[0.759908] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
cape with part# BB-BONELT-HDMIN 
[0.760092] bone-capemgr bone_capemgr.9: loader: before slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
[0.760107] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
[0.760134] bone-capemgr bone_capemgr.9: initialized OK. 
[0.762291] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
[0.764081] bone-capemgr bone_capemgr.9: loader: before slot-7 
dev_OPTOCAPE:00A0 (prio 0) 
[0.764094] bone-capemgr bone_capemgr.9: loader: check slot-7 
dev_OPTOCAPE:00A0 (prio 0) 
[0.764109] bone-capemgr bone_capemgr.9: loader: after slot-7 
dev_OPTOCAPE:00A0 (prio 0) 
[0.764124] bone-capemgr bone_capemgr.9: slot #7: Requesting part 
number/version based 'dev_OPTOCAPE-00A0.dtbo 
[0.764139] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 
'dev_OPTOCAPE-00A0.dtbo' for board-name 'Override Board Name', version 
'00A0' 
[1.239617] bone-capemgr bone_capemgr.9: failed to load firmware 
'dev_OPTOCAPE-00A0.dtbo' 
[1.248179] bone-capemgr bone_capemgr.9: loader: failed to load slot-7 
dev_OPTOCAPE:00A0 (prio 0) 
[1.257645] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
[1.257662] bone-capemgr bone_capemgr.9: loader: after slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
[1.257685] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 
'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0' 
[1.257702] bone-capemgr bone_capemgr.9: slot #4: dtbo 
'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree 
[1.257911] bone-capemgr bone_capemgr.9: slot #4: #2 overlays 
[1.286653] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays. 
[1.286678] bone-capemgr bone_capemgr.9: loader: done slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1) 
(initramfs) :


Then I repeated the process, loading "BB-BONE-LCD4-01" instead. I rebooted, 
and this overlay loaded with no problems. 


Then I tried loading manually with:

echo BB-BONE-LCD4-01 >/sys/devices/bone_capemgr.9/slots

This worked also. When I tried the same with my custom file, the shell 
returned:

sh: I/O error


So it seems I am

Re: [beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

2016-01-31 Thread Dean

I ought to qualify what I am saying here. To be clear this application does 
not appear to be looking for a spidev2.0. All said I am still not getting a 
change in state. I had a similar problem with GPIO's yet that went away 
with the latests updates, this however seems to be sticking. No change. Am 
I missing something here ?

On Sunday, January 31, 2016 at 7:12:15 PM UTC-7, Dean wrote:
>
>
> I backed away from the previous application this one is not the same. It 
> appears to be okay ...
>
> root@beaglebone:~# ls -lh /dev/spi*
> crw-rw 1 root spi 153, 0 Jan 27 02:43 /dev/spidev1.0
> crw-rw 1 root spi 153, 1 Jan 27 02:43 /dev/spidev1.1
>
>

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

[beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

2016-01-31 Thread Dean

 

I am trying to get the SPI bus to work, unfortunately it will not change 
states. Is there something obvious that I am missing. I believe that this 
ties into my previous post on strace and is the reason that I cannot my LCD 
to work. Thanks in advance to those that respond to this post.



Linux beaglebone 4.1.15-ti-r43 #1 SMP PREEMPT Thu Jan 21 22:33:31 UTC 2016 
armv7l GNU/Linux

BeagleBoard.org Debian Image 2015-11-12


root@beaglebone:~# . ~/.profile


root@beaglebone:~# echo $SLOTS

/sys/devices/platform/bone_capemgr/slots


root@beaglebone:~# echo $PINS

/sys/kernel/debug/pinctrl/44e10800.pinmux/pins


root@beaglebone:~# ls

DM-SPI-Test-00A0.dtbo DM-SPI-Test.dtbo DM-SPI-Test.dts bb.org-overlays 
boneDeviceTree exploringBB git


root@beaglebone:~# dtc -O dtb -o DM-SPI-Test-00A0.dtbo -b 0 -@ 
DM-SPI-Test.dts


root@beaglebone:~# cp DM-SPI-Test-00A0.dtbo /lib/firmware


root@beaglebone:~# cd /lib/firmware


root@beaglebone:/lib/firmware# ls

ADAFRUIT-SPI0-00A0.dtbo BB-UART3-00A0.dtbo PyBBIO-gpio0_11-00A0.dtbo 
PyBBIO-gpio1_3-00A0.dtbo PyBBIO-gpio3_19-00A0.dtbo

ADAFRUIT-SPI1-00A0.dtbo BB-UART4-00A0.dtbo PyBBIO-gpio0_12-00A0.dtbo 
PyBBIO-gpio1_30-00A0.dtbo PyBBIO-gpio3_21-00A0.dtbo

ADAFRUIT-UART1-00A0.dtbo BB-UART5-00A0.dtbo PyBBIO-gpio0_13-00A0.dtbo 
PyBBIO-gpio1_31-00A0.dtbo PyBBIO-usr0-00A0.dtbo

ADAFRUIT-UART2-00A0.dtbo BB-W1-P9.12-00A0.dtbo PyBBIO-gpio0_14-00A0.dtbo 
PyBBIO-gpio1_4-00A0.dtbo PyBBIO-usr1-00A0.dtbo

ADAFRUIT-UART4-00A0.dtbo DM-SPI-Test-00A0.dtbo PyBBIO-gpio0_15-00A0.dtbo 
PyBBIO-gpio1_5-00A0.dtbo PyBBIO-usr2-00A0.dtbo

ADAFRUIT-UART5-00A0.dtbo DVK530-LCD4-01-00A0.dtbo PyBBIO-gpio0_2-00A0.dtbo 
PyBBIO-gpio1_6-00A0.dtbo PyBBIO-usr3-00A0.dtbo

BB-ADC-00A0.dtbo LICENCE.atheros_firmware PyBBIO-gpio0_20-00A0.dtbo 
PyBBIO-gpio1_7-00A0.dtbo bone_eqep0-00A0.dtbo

BB-BBBMINI-00A0.dtbo LICENCE.broadcom_bcm43xx PyBBIO-gpio0_22-00A0.dtbo 
PyBBIO-gpio2_1-00A0.dtbo bone_eqep1-00A0.dtbo

BB-BONE-AUDI-02-00A0.dtbo LICENCE.rtlwifi_firmware.txt 
PyBBIO-gpio0_23-00A0.dtbo PyBBIO-gpio2_10-00A0.dtbo bone_eqep2-00A0.dtbo

BB-BONE-BACONE-00A0.dtbo LICENCE.ti-connectivity PyBBIO-gpio0_26-00A0.dtbo 
PyBBIO-gpio2_11-00A0.dtbo bone_eqep2b.dtbo

BB-BONE-CRYPTO-00A0.dtbo NL-AB-BBBC-00D0.dtbo PyBBIO-gpio0_27-00A0.dtbo 
PyBBIO-gpio2_12-00A0.dtbo brcm

BB-BONE-DVID-01-00A3.dtbo PyBBIO-ADC-00A0.dtbo PyBBIO-gpio0_3-00A0.dtbo 
PyBBIO-gpio2_13-00A0.dtbo cape-CBB-Serial-r01.dtbo

BB-BONE-LCD3-01-00A2.dtbo PyBBIO-AIN0-00A0.dtbo PyBBIO-gpio0_30-00A0.dtbo 
PyBBIO-gpio2_14-00A0.dtbo cape-bone-ibb-00A0.dtbo

BB-BONE-LCD4-01-00A1.dtbo PyBBIO-AIN1-00A0.dtbo PyBBIO-gpio0_31-00A0.dtbo 
PyBBIO-gpio2_15-00A0.dtbo cape-univ-audio-00A0.dtbo

BB-BONE-LCD7-01-00A3.dtbo PyBBIO-AIN2-00A0.dtbo PyBBIO-gpio0_4-00A0.dtbo 
PyBBIO-gpio2_16-00A0.dtbo cape-univ-emmc-00A0.dtbo

BB-BONE-REPLICAP-00B1.dtbo PyBBIO-AIN3-00A0.dtbo PyBBIO-gpio0_5-00A0.dtbo 
PyBBIO-gpio2_17-00A0.dtbo cape-univ-hdmi-00A0.dtbo

BB-BONE-SERL-03-00A1.dtbo PyBBIO-AIN4-00A0.dtbo PyBBIO-gpio0_7-00A0.dtbo 
PyBBIO-gpio2_2-00A0.dtbo cape-universal-00A0.dtbo

BB-BONE-WTHR-01-00B0.dtbo PyBBIO-AIN5-00A0.dtbo PyBBIO-gpio0_8-00A0.dtbo 
PyBBIO-gpio2_22-00A0.dtbo cape-universaln-00A0.dtbo

BB-CAN1-00A0.dtbo PyBBIO-AIN6-00A0.dtbo PyBBIO-gpio0_9-00A0.dtbo 
PyBBIO-gpio2_23-00A0.dtbo carl9170-1.fw

BB-I2C1-00A0.dtbo PyBBIO-AIN7-00A0.dtbo PyBBIO-gpio1_0-00A0.dtbo 
PyBBIO-gpio2_24-00A0.dtbo dev-USB-PWR-CTL-00A1.dtbo

BB-I2C1-PCA9685-00A0.dtbo PyBBIO-ecap0-00A0.dtbo PyBBIO-gpio1_1-00A0.dtbo 
PyBBIO-gpio2_25-00A0.dtbo htc_9271.fw

BB-I2C2-0A00.dtbo PyBBIO-ecap1-00A0.dtbo PyBBIO-gpio1_12-00A0.dtbo 
PyBBIO-gpio2_3-00A0.dtbo mt7601u.bin

BB-RELAY-4PORT-00A0.dtbo PyBBIO-ehrpwm1-00A0.dtbo PyBBIO-gpio1_13-00A0.dtbo 
PyBBIO-gpio2_4-00A0.dtbo rtlwifi

BB-RTC-01-00A0.dtbo PyBBIO-ehrpwm2-00A0.dtbo PyBBIO-gpio1_14-00A0.dtbo 
PyBBIO-gpio2_5-00A0.dtbo ti-connectivity

BB-SPI0-MCP3008-00A0.dtbo PyBBIO-epwmss0-00A0.dtbo 
PyBBIO-gpio1_15-00A0.dtbo PyBBIO-gpio2_6-00A0.dtbo univ-all-00A0.dtbo

BB-SPI1-01-00A0.dtbo PyBBIO-epwmss1-00A0.dtbo PyBBIO-gpio1_16-00A0.dtbo 
PyBBIO-gpio2_7-00A0.dtbo univ-emmc-00A0.dtbo

BB-SPIDEV1-00A0.dtbo PyBBIO-epwmss2-00A0.dtbo PyBBIO-gpio1_17-00A0.dtbo 
PyBBIO-gpio2_8-00A0.dtbo univ-hdmi-00A0.dtbo

BB-SPIDEV1.dtbo PyBBIO-eqep0-00A0.dtbo PyBBIO-gpio1_18-00A0.dtbo 
PyBBIO-gpio2_9-00A0.dtbo univ-nhdmi-00A0.dtbo

BB-SPIDEV1A1-00A0.dtbo PyBBIO-eqep1-00A0.dtbo PyBBIO-gpio1_19-00A0.dtbo 
PyBBIO-gpio3_14-00A0.dtbo

BB-UART1-00A0.dtbo PyBBIO-eqep2-00A0.dtbo PyBBIO-gpio1_2-00A0.dtbo 
PyBBIO-gpio3_15-00A0.dtbo

BB-UART2-00A0.dtbo PyBBIO-eqep2b-00A0.dtbo PyBBIO-gpio1_28-00A0.dtbo 
PyBBIO-gpio3_16-00A0.dtbo

BB-UART2-RTSCTS-00A0.dtbo PyBBIO-gpio0_10-00A0.dtbo 
PyBBIO-gpio1_29-00A0.dtbo PyBBIO-gpio3_17-00A0.dtbo

root@beaglebone:/lib/firmware# cat $SLOTS

0: PF -1 

1: PF -1 

2: PF -1 

3: PF -1 


root@beaglebone:/lib/firmware# cat $PINS|grep 950

pin 84 (44e10950.0) 0037 pinctrl-single 


root@beaglebone:/lib/firmware# cat $PINS|grep 954

pin 85 (44e10954.0) 0037

Re: [beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

2016-01-31 Thread Dean


root@beaglebone:~# dmesg | grep bone
[5.093226] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,000C,2715BBBK0795'
[5.100609] bone_capemgr bone_capemgr: 
compatible-baseboard=ti,beaglebone-black - #slots=4
[5.168530] bone_capemgr bone_capemgr: slot #0: No cape found
[5.228522] bone_capemgr bone_capemgr: slot #1: No cape found
[5.288522] bone_capemgr bone_capemgr: slot #2: No cape found
[5.348521] bone_capemgr bone_capemgr: slot #3: No cape found
[5.354392] bone_capemgr bone_capemgr: initialized OK.
[6.570208] systemd[1]: Set hostname to .
[6.839587] systemd[1]: Configuration file 
/lib/systemd/system/bonescript.socket is marked world-inaccessible. This 
has no effect as configuration data is accessible via APIs without 
restrictions. Proceeding anyway.
[6.860332] systemd[1]: Configuration file 
/lib/systemd/system/bonescript.service is marked world-inaccessible. This 
has no effect as configuration data is accessible via APIs without 
restrictions. Proceeding anyway.
[6.963418] systemd[1]: Configuration file 
/lib/systemd/system/bonescript-autorun.service is marked 
world-inaccessible. This has no effect as configuration data is accessible 
via APIs without restrictions. Proceeding anyway.
[  507.748022] bone_capemgr bone_capemgr: part_number 'DM-SPI-Test', 
version 'N/A'
[  507.756582] bone_capemgr bone_capemgr: slot #4: override
[  507.770021] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[  507.777097] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,DM-SPI-Test'
[  507.801823] bone_capemgr bone_capemgr: slot #4: dtbo 
'DM-SPI-Test-00A0.dtbo' loaded; overlay id #0


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

Re: [beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

2016-01-31 Thread Dean


I backed away from the previous application this one is not the same. It 
appears to be okay ...

root@beaglebone:~# ls -lh /dev/spi*
crw-rw 1 root spi 153, 0 Jan 27 02:43 /dev/spidev1.0
crw-rw 1 root spi 153, 1 Jan 27 02:43 /dev/spidev1.1

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

Re: Re[2]: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-26 Thread Dean

I found a great source of information on SPI ...

https://www.kernel.org/doc/Documentation/spi/



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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean


He is also using an accompanying 74HC595 8 bit serial shift register in a 4 
bit (interface DB4-DB7 configuration).

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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean

Interesting. Just reloaded with an updated kernel and this time it did not 
crash. All the same similar problems remain. William all things equal if 
you found the book remedial I would like to challenge you on that. Buy 
yourself an LCD and see if you can replicate what Derek Molloy did there in 
Chapter 9 page 362 Listing 9-10 - we both know talking and doing are not 
the same thing. For now I must dig deeper. Some of his examples were not 
nearly as frustrating. It's a great book by the way. I could of started 
with arduino, but n I started with BBB. 

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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean

Newhaven Model: NHD-0216K1Z-NSB-FBW-L. 


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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean

The code came from Derek Molloy's Exploring Beaglebone -Tools and 
Techniques Chapter 9 page 362 Listing 9-10. Regarding a decent book on how 
to spidev have you any recommendations? I am the first to admit I am a 
novice and it goes without saying that we all started somewhere as 
frustrating as that is. So to recap add code to trace code? That sounds 
like a plan. All aside the real question on my mind is that I would like to 
rule out that there is not something else going on here with the device 
tree overlays that I would not be aware of? It would be helpful at this end 
if a guy knew where to look for updates (i.e. the source) and had a listing 
of what they were or how they might affect things downstream. I know how 
ridiculous that must sound in that Linux is an open source community backed 
by volunteers nonetheless I am not clear on the structure on how things 
come together and as such I find it utterly amazing that things work. I 
understand that Robert has had a big hand in it and there are many others, 
but I am not sure on how it all comes together. Thanks for the input no 
offense taken.

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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean

 

*apt-get install build-essential * 



*In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first" is 
spidev1 (even if spi1 over spi0..) > * 


* SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both 
loaded)*

*The code is trying to open /dev/spidev2.0, but it's not there*


*This should be your first worry-> open("/dev/spidev2.0", O_RDWR) = -1 
ENOENT (No such file or directory)*

Find out why your system thinks this file does not exist. As in perhaps it 
doesn't because you need to load a device tree file as mike mentioned 
above. But also as stated above, there can be many reasons why your 
application does not think this file exists.

So did you tell the BBB to load the spidev interface??? 

PS.. "4.1.12-ti-r29" was way before i fixed spi/dma..  So you really 
should upgrade: (unless you only plan to send 159 bytes over spi) 

cd /opt/scripts/tools/ 
git pull 
sudo ./update_kernel.sh --ti-rt-channel --lts-4_1 
cd ~/ 

git clone https://github.com/ 
 --depth=1 
cd ./bb.org-overlays 
./dtc-overlay.sh 
./install.sh 

Then: 

sudo sh -c "echo 'cape_enable=bone_capemgr.
>> /boot/uEnv.txt" 

*Here is an update of the steps performed ...*

*1) I did an update on **apt-get install build-essential*

*2) Change code from ... **SPIDevice *busDevice = new SPIDevice(2,0)*

* to* *SPIDevice *busDevice = new SPIDevice(1,0)*

*3) Updated kernel and ./dtc overlay*

*OUTCOME: The SPIDEV2.0 problem went away – unfortunately shortly 
thereafter my BBB would no longer connect with ssh root@192.168.7.2 
. I therefore reloaded back to what I started with 
originally as below.*

*Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux*

*Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015*

*BeagleBoard.org Debian Image 2015-11-12*

*When I set out again to run natively on my BBB the error changed from ...*

*SPI: SPI_IOC_MESSAGE Failed: Bad file descriptor * 

*to * 

*SPI: SPI_IOC_MESSAGE Failed: Invalid argument * 

*and the SPIDEV2.0 of course went away with libEBBLibrary.so loading and 
SPIDEV1.0 now loading. That said there still remains to be a number of 
directories that are still missing. I am taking this latest error as a sign 
of progress, but I have yet to resolve it. I also should mention that I 
ruled out my laptop, and loading the same configuration on my clunker with 
the same outcome. Here is latests strace ... For brevity I removed portions 
of it because it repeats itself at nauseum.*



*SPI: SPI_IOC_MESSAGE Failed: Invalid argument*


root@beaglebone:~/exploringBB/chp09/LCDcharacter# ls

LCDApp LCDApp.cpp LCDProb build build_static

root@beaglebone:~/exploringBB/chp09/LCDcharacter# strace ./LCDApp

execve("./LCDApp", ["./LCDApp"], [/* 19 vars */]) = 0

brk(0) = 0x8b9000

uname({sys="Linux", node="beaglebone", ...}) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f4d000

access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3

fstat64(3, {st_mode=S_IFREG|0644, st_size=26752, ...}) = 0

mmap2(NULL, 26752, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f46000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp", 0xbea86370) = -1 ENOENT 
(No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/vfp", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l", 0xbea86370) = -1 ENOENT (No such 
file or directory)

open("/lib/arm-linux-gnueabihf/tls/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/linux-gnueabihf/tls/neon/vflib/armp", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/neon", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean



*pt-get install build-essential * 



*In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first" is 
spidev1 (even if spi1 over spi0..) > * 


* SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both 
loaded)*

*The code is trying to open /dev/spidev2.0, but it's not there*


*This should be your first worry-> open("/dev/spidev2.0", O_RDWR) = -1 
ENOENT (No such file or directory)*

Find out why your system thinks this file does not exist. As in perhaps it 
doesn't because you need to load a device tree file as mike mentioned 
above. But also as stated above, there can be many reasons why your 
application does not think this file exists.

So did you tell the BBB to load the spidev interface??? 

PS.. "4.1.12-ti-r29" was way before i fixed spi/dma..  So you really 
should upgrade: (unless you only plan to send 159 bytes over spi) 

cd /opt/scripts/tools/ 
git pull 
sudo ./update_kernel.sh --ti-rt-channel --lts-4_1 
cd ~/ 

git clone https://github.com/ 
 --depth=1 
cd ./bb.org-overlays 
./dtc-overlay.sh 
./install.sh 

Then: 

sudo sh -c "echo 'cape_enable=bone_capemgr.
>> /boot/uEnv.txt" 

*Here is an update of the steps performed ...*

*1) I did an update on **apt-get install build-essential*

*2) Change code from ... **SPIDevice *busDevice = new SPIDevice(2,0)*

* to* *SPIDevice *busDevice = new SPIDevice(1,0)*

*3) Updated kernel and ./dtc overlay*

*OUTCOME: The SPIDEV2.0 problem went away – unfortunately shortly 
thereafter my BBB would no longer connect with ssh root@192.168.7.2 
. I therefore reloaded back to what I started with 
originally as below.*

*Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux*

*Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015*

*BeagleBoard.org Debian Image 2015-11-12*

*When I set out again to run natively on my BBB the error changed from ...*

*SPI: SPI_IOC_MESSAGE Failed: Bad file descriptor * 

*to * 

*SPI: SPI_IOC_MESSAGE Failed: Invalid argument * 

*and the SPIDEV2.0 of course went away with libEBBLibrary.so loading and 
SPIDEV1.0 now loading. That said there still remains to be a number of 
directories that are still missing. I am taking this latest error as a sign 
of progress, but I have yet to resolve it. I also should mention that I 
ruled out my laptop, and loading the same configuration on my clunker with 
the same outcome. Here is latests strace ... For brevity I removed portions 
of it because it repeats itself at nauseum.*



*SPI: SPI_IOC_MESSAGE Failed: Invalid argument*


root@beaglebone:~/exploringBB/chp09/LCDcharacter# ls

LCDApp LCDApp.cpp LCDProb build build_static

root@beaglebone:~/exploringBB/chp09/LCDcharacter# strace ./LCDApp

execve("./LCDApp", ["./LCDApp"], [/* 19 vars */]) = 0

brk(0) = 0x8b9000

uname({sys="Linux", node="beaglebone", ...}) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f4d000

access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3

fstat64(3, {st_mode=S_IFREG|0644, st_size=26752, ...}) = 0

mmap2(NULL, 26752, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f46000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp", 0xbea86370) = -1 ENOENT 
(No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/vfp", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l", 0xbea86370) = -1 ENOENT (No such 
file or directory)

open("/lib/arm-linux-gnueabihf/tls/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/linux-gnueabihf/tls/neon/vflib/armp", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/neon", 0xbea86370) = -1 ENOENT (No 
such file or directory)

open("/lib/arm-linux-gnueabihf/tls/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-25 Thread Dean

Thanks Robert. I will give it another whirl.


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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-24 Thread Dean


Natively I am running 4.9.2 ...

cat /proc/version
Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015


That said I also have a VM of Debian 8.2 which I have used on occasion for 
cross compilation and Eclipse. All said this post was not from the VM, but 
run natively on the BBB with my desktop as UBuntu 15.04.






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

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-24 Thread Dean


I ran strace and it generated the following output. I am not sure exactly 
what it all means. It seems to me that some files are missing. I am unclear 
at this point in how to obtain the missing files? Are the missing files 
generated by make file or do they come from somewhere else? At any rate it 
would appear that the libEBBLibrary.so (highlighted in purple) is there and 
is accessed, but there are others that are not showing up? Any ideas?? By 
the way William thanks for the strace tip although I am unclear at this 
point about how to interpet??

execve("./LCDApp", ["./LCDApp"], [/* 19 vars */]) = 0

brk(0) = 0x4bf000

uname({sys="Linux", node="beaglebone", ...}) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f95000

access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3

fstat64(3, {st_mode=S_IFREG|0644, st_size=26752, ...}) = 0

mmap2(NULL, 26752, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f8e000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp", 0xbea01370) = -1 ENOENT 
(No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/libEBBLibrary.so", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0`m\0\0004\0\0\0"..., 
512) = 512

lseek(3, 95252, SEEK_SET) = 95252

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1200) = 1200

lseek(3, 63425, SEEK_SET) = 63425

read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) 
= 51

fstat64(3, {st_mode=S_IFREG|0755, st_size=96452, ...}) = 0

mmap2(NULL, 128964, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6f5

mprotect(0xb6f5f000, 65536, PROT_NONE) = 0

mmap2(0xb6f6f000, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6f6f000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/usr/lib/arm-linux-gnueabihf/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0 n\4\0004\0\0\0"..., 
512) = 512

open("/lib/arm-linux-gnueabihf/libEBBLibrary.so", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0`m\0\0004\0\0\0"..., 
512) = 512

lseek(3, 95252, SEEK_SET) = 95252

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1200) = 1200

lseek(3, 63425, SEEK_SET) = 63425

read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) 
= 51

fstat64(3, {st_mode=S_IFREG|0755, st_size=96452, ...}) = 0

mmap2(NULL, 128964, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6f5

mprotect(0xb6f5f000, 65536, PROT_NONE) = 0

mmap2(0xb6f6f000, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6f6f000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/usr/lib/arm-linux-gnueabihf/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0 n\4\0004\0\0\0"..., 
512) = 512

lseek(3, 100684, SEEK_SET) = 100684

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1520) = 1520

lseek(3, 65940, SEEK_SET) = 65940

read(3, "A4\0\0\0aeabi\0\1*\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 53) 
= 53

fstat64(3, {st_mode=S_IFREG|0755, st_size=102204, ...}) = 0

mmap2(NULL, 139836, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6ceb000

mprotect(0xb6cfb000, 61440, PROT_NONE) = 0

mmap2(0xb6d0a000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6d0a000

mmap2(0xb6d0c000, 4668, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6d0c000

close(3) = 0

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8c000

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8b000

set_tls(0xb6f8b4c0, 0xb6f98050, 0xb6f8bbb8, 0xb6f8b4c0, 0xb6f98050) = 0

mprotect(0xb6df6000, 8192, PROT_READ) = 0

mprotect(0xb6d0a000, 4096, PROT_READ) = 0

mprotect(0xb6e97000, 4096, PROT_READ) = 0

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8a000

mprotect(0xb6f44000, 16384, PROT_READ) = 0

mprotect(0xb6f97000, 4096, PROT_READ) = 0

munmap(0xb6f8e000, 26752) = 0

set_tid_address(0xb6f8b068) = 650

set_robust_list(0xb6f8b070, 12) = 0

rt_sigaction(SIGRTMIN, {0xb6cefd9d, [], SA_RESTORER|SA_SIGINFO, 
0xb6d34ae1}, NULL, 8) = 0

rt_sigaction(SIGRT_1, {0xb6cefcbd, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 
0xb6d34ae1},

[beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-24 Thread Dean

 

I am trying to decipher my strace. My setup is Linux beaglebone 
4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 armv7l GNU/Linux 
BeagleBoard.org Debian Image 2015-11-12. I am not sure on how to interpet 
my findings. In particular of the files that are missing is that because I 
need an update or do they arise out a make file that simply is not working 
or incorrect. The CMake version that I am using is 3.0.2. Thanks for 
replies in advance.



execve("./LCDApp", ["./LCDApp"], [/* 19 vars */]) = 0

brk(0) = 0x4bf000

uname({sys="Linux", node="beaglebone", ...}) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f95000

access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3

fstat64(3, {st_mode=S_IFREG|0644, st_size=26752, ...}) = 0

mmap2(NULL, 26752, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f8e000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

stat64("/lib/arm-linux-gnueabihf/tls/v7l/neon/vfp", 0xbea01370) = -1 ENOENT 
(No such file or directory)

open("/lib/arm-linux-gnueabihf/tls/v7l/neon/libEBBLibrary.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

open("/lib/arm-linux-gnueabihf/libEBBLibrary.so", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0`m\0\0004\0\0\0"..., 
512) = 512

lseek(3, 95252, SEEK_SET) = 95252

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1200) = 1200

lseek(3, 63425, SEEK_SET) = 63425

read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) 
= 51

fstat64(3, {st_mode=S_IFREG|0755, st_size=96452, ...}) = 0

mmap2(NULL, 128964, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6f5

mprotect(0xb6f5f000, 65536, PROT_NONE) = 0

mmap2(0xb6f6f000, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6f6f000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/usr/lib/arm-linux-gnueabihf/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0 n\4\0004\0\0\0"..., 
512) = 512

open("/lib/arm-linux-gnueabihf/libEBBLibrary.so", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0`m\0\0004\0\0\0"..., 
512) = 512

lseek(3, 95252, SEEK_SET) = 95252

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1200) = 1200

lseek(3, 63425, SEEK_SET) = 63425

read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) 
= 51

fstat64(3, {st_mode=S_IFREG|0755, st_size=96452, ...}) = 0

mmap2(NULL, 128964, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6f5

mprotect(0xb6f5f000, 65536, PROT_NONE) = 0

mmap2(0xb6f6f000, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6f6f000

close(3) = 0

access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

open("/usr/lib/arm-linux-gnueabihf/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = 3

read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0 n\4\0004\0\0\0"..., 
512) = 512

lseek(3, 100684, SEEK_SET) = 100684

read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
1520) = 1520

lseek(3, 65940, SEEK_SET) = 65940

read(3, "A4\0\0\0aeabi\0\1*\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 53) 
= 53

fstat64(3, {st_mode=S_IFREG|0755, st_size=102204, ...}) = 0

mmap2(NULL, 139836, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb6ceb000

mprotect(0xb6cfb000, 61440, PROT_NONE) = 0

mmap2(0xb6d0a000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6d0a000

mmap2(0xb6d0c000, 4668, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6d0c000

close(3) = 0

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8c000

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8b000

set_tls(0xb6f8b4c0, 0xb6f98050, 0xb6f8bbb8, 0xb6f8b4c0, 0xb6f98050) = 0

mprotect(0xb6df6000, 8192, PROT_READ) = 0

mprotect(0xb6d0a000, 4096, PROT_READ) = 0

mprotect(0xb6e97000, 4096, PROT_READ) = 0

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb6f8a000

mprotect(0xb6f44000, 16384, PROT_READ) = 0

mprotect(0xb6f97000, 4096, PROT_READ) = 0

munmap(0xb6f8e000, 26752) = 0

set_tid_address(0xb6f8b068) = 650

set_robust_list(0xb6f8b070, 12) = 0

rt_sigaction(SIGRTMIN, {0xb6cefd9d, [], SA_RESTORER|SA_SIGINFO, 
0xb6d34ae1}, NULL, 8) = 0

rt_sigaction(SIGRT_1, {0xb6cefcbd, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 
0xb6d34ae1}, NULL, 8) = 0

rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0

getrlimit(RLIMIT_STACK,

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-24 Thread Dean

I decided to close this post and repost as an strace question as it is more 
to the point. Thanks William for directing my attention to strace.


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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-24 Thread Dean


Thanks for getting back to me. I am running gcc version 4.9.2

crico@crico-X555LAB:~$ cat /proc/version
Linux version 3.19.0-47-generic (buildd@lgw01-56) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu13) ) #53-Ubuntu SMP Mon Jan 18 14:02:48 UTC 2016


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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-24 Thread Dean


4.9.2

cat /proc/version
Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015


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

Re: [beagleboard] strace question on Linux beaglebone 4.1.12-ti-r29 UTC 2015 armv7l GNU/Linux Debian Image 2015-11-12

2016-01-24 Thread Dean


What was posted was running on my BBB. That said I also have a VM of Debian 
8.2 which I did some cross compiling. At any rate my GCC is 4.9.2

cat /proc/version
Linux version 4.1.12-ti-r29 (root@a5-imx6q-wandboard-2gb) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015


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

[beagleboard] cannot install cmake on Linux beaglebone 4.1.12-ti-r29 yet installs on Ubuntu 15.04

2016-01-19 Thread Dean

 

cannot install cmake on Linux beaglebone 4.1.12-ti-r29


crico@crico-X555LAB:~$ ssh dean@192.168.7.2

Debian GNU/Linux 8


BeagleBoard.org Debian Image 2015-11-12


Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian


default username:password is [debian:temppwd]


dean@192.168.7.2's password: 

Last login: Tue Jan 19 19:44:39 2016 from 192.168.7.1

dean@beaglebone:~$ sudo apt-get install cmake

[sudo] password for dean: 

Reading package lists... Done

Building dependency tree 

Reading state information... Done

Package cmake is not available, but is referred to by another package.

This may mean that the package is missing, has been obsoleted, or

is only available from another source


E: Package 'cmake' has no installation candidate

dean@beaglebone:~$ 

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

Re: [beagleboard] cannot install cmake on Linux beaglebone 4.1.12-ti-r29 yet installs on Ubuntu 15.04

2016-01-19 Thread Dean

The more I learn the more I realize how little I know. Robert, thanks for 
coming through on this. Problem solved.


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

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-19 Thread Dean


I now know what is going on, but I'll be damned if I know how to resolve 
it. Prior to adding #include  the usleep function would not take. 
Hopefully a coding guru might be able to help me out on this one as I am 
novice when it comes to coding.

http://stackoverflow.com/questions/34184743/kernel-compiles-but-wont-link-with-unistd-h-reference


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

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-19 Thread Dean


It turns out that #include is not required. I was using the 
usleep function earlier. Regardless the end result is the same. No go. 
Everything would indicate that although it compiles and builds it fails to 
come through on the link. Back to reading.

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ls
LCDAppLCDApp.cpp  build  build_static
root@beaglebone:~/exploringBB/chp09/LCDcharacter# sudo sh -c "echo 
BB-SPIDEV1 > $SLOTS"
root@beaglebone:~/exploringBB/chp09/LCDcharacter# cat $SLOTS|grep SPI
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1
root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./build
root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory
root@beaglebone:~/exploringBB/chp09/LCDcharacter# 


>

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

[beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-18 Thread Dean

*My BBB setup is as follows ...* 
Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux
BeagleBoard.org Debian Image 2015-11-12

*For whatever reason I cannot access a library (i.e. libEBBLibrary.so) and 
I am not sure what I am missing. Might someone offer a suggestion on where 
I am going wrong or what I can do to rectify it?? Thanks in advance who 
those that reply.*
root@beaglebone:~/exploringBB/chp09/LCDcharacter# sudo sh -c "echo 
BB-SPIDEV1 > $SLOTS" 

root@beaglebone:~/exploringBB/chp09/LCDcharacter# cat $SLOTS|grep SPI

4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1



root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./build 

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


root@beaglebone:~/exploringBB/chp09/LCDcharacter# g++ LCDApp.cpp 
../../library/libEBBLibrary.so -o LCDApp -I "../../library"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


root@beaglebone:~/exploringBB/chp09/LCDcharacter# echo $PATH

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"
root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp 
./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


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

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

2016-01-18 Thread Dean

All said something else is going on here. libEBBLibrary.so is definitely 
there yet it does not take. I should mention that namespace std is being 
used to make updates on code easier. See code listed below. 


root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="~/exploringBB/library/libEBBLibrary.so:$LD_LIBRARY_PATH"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory

root@beaglebone:~/exploringBB/chp09/LCDcharacter# cd ../../library

root@beaglebone:~/exploringBB/library# ls

CMakeLists.txt README build bus display docs example gpio libEBBLibrary.a 
libEBBLibrary.so motor network sensor

root@beaglebone:~/exploringBB/library# 


Here is the code ...


#include 
#include 
#include 
#include "display/LCDCharacterDisplay.h"
using namespace std;
using namespace exploringBB;

int main(){
   cout << "Starting EBB LCD Character Display Example" << endl;
   SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both 
loaded)
   busDevice->setSpeed(100);  // Have access to SPI Device object
   ostringstream s;   // Using this to combine text and int 
data
   LCDCharacterDisplay display(busDevice, 16, 2); // Construct 16x2 LCD 
Display
   display.clear();   // Clear the character LCD module
   display.home();// Move the cursor to the (0,0) 
position
   display.print("EBB by D. Molloy"); // String to display on the first row
   for(int x=0; x<=1; x++){   // Do this 10,000 times
  s.str("");  // clear the ostringstream object s
  display.setCursorPosition(1,3); // move the cursor to second row
  s << "X=" << x; // construct a string that has an int 
value
  display.print(s.str()); // print the string X=*** on the LCD 
module
   }
   cout << "End of EBB LCD Character Display Example" << endl;
}


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

[beagleboard] Re: Cannot Set Static IP address on Beaglebone Black Version 4.1.12-ti-r29 Ubuntu 15.04 and Debian 8.2

2016-01-16 Thread Dean


Graham thanks man!! This problem has been solved. Very much appreciated.

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

Re: [beagleboard] GPS Overlay not working on Beaglebone Black 4.1.12-ti-r29 Ubuntu 15.04 and Debian 8.2 VM

2016-01-16 Thread Dean

Robert you Rock !! Thanks man the problem has been solved at this end. Much 
appreciated.

Wrong dtc..
>
> Follow:
>
> https://github.com/beagleboard/bb.org-overlays
>
> and run:
>
> ./dtc-overlay.sh
>
> then use:
>
> /usr/local/bin/dtc
>  
>
>>
>> root@beaglebone:~/boneDeviceTree/overlay# ./build
>>
>>
>> Compiling the overlay from .dts to .dtbo
>>
>>
>> root@beaglebone:~/boneDeviceTree/overlay# ls -al
>>
>>
>> total 20
>>
>> drwxrwxr-x 2 root root 4096 Nov 12 2015 .
>>
>> drwxrwxr-x 10 root root 4096 Nov 12 2015 ..
>>
>> -rw-r--r-- 1 root root 986 Nov 12 21:23 DM-GPIO-Test-00A0.dtbo
>>
>> -rw-r--r-- 1 root root 1591 Nov 12 2015 DM-GPIO-Test.dts
>>
>> -rwxr-xr-x 1 root root 124 Nov 12 2015 build
>>
>>
>> root@beaglebone:~/boneDeviceTree/overlay# cp DM-GPIO-Test-00A0.dtbo 
>> /lib/firmware/
>>
>>
>> root@beaglebone:/lib/firmware# cat $SLOTS
>>
>> 0: PF -1 
>>
>> 1: PF -1 
>>
>> 2: PF -1 
>>
>> 3: PF -1 
>>
>> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln
>>
>>
>> root@beaglebone:/lib/firmware# echo DM-GPIO-Test > $SLOTS 
>>
>
>
> dmesg | grep bone
>
> will show you more..
>  
>
>>
>> root@beaglebone:/lib/firmware# cat $SLOTS
>>
>> 0: PF -1 
>>
>> 1: PF -1 
>>
>> 2: PF -1 
>>
>> 3: PF -1 
>>
>> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln
>>
>
> cape-universaln is already loaded to..
>
> disable by removing: "cape_universal=enable" from:
>
> /boot/uEnv.txt  
>
>
>  
>
>> 5: P-O-L- 1 Override Board Name,00A0,Override Manuf,DM-GPIO-Test
>>
>> root@beaglebone:/lib/firmware# cat $PINS|grep 878
>>
>>
>> pin 30 (44e10878.0) 0037 pinctrl-single 
>>
>> root@beaglebone:/lib/firmware# cat $PINS|grep 984
>>
>> pin 97 (44e10984.0) 0037 pinctrl-single 
>>
>> root@beaglebone:/lib/firmware# cat $PINS|grep 834
>>
>> pin 13 (44e10834.0) 0027 pinctrl-single 
>>
>> root@beaglebone:/lib/firmware# cat $PINS|grep 830
>>
>> pin 12 (44e10830.0) 0027 pinctrl-single 
>>
>> root@beaglebone:/lib/firmware# cat $PINS|grep 824
>>
>> pin 9 (44e10824.0) 0027 pinctrl-single 
>>
>>
>>
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot Fully Disable HDMI device tree overlay, HDMI Okay/HDMIN to be specific.

2016-01-16 Thread Dean

Managed to disable the HDMI with the latest image. Thanks Robert. 

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

[beagleboard] GPS Overlay not working on Beaglebone Black 4.1.12-ti-r29 Ubuntu 15.04 and Debian 8.2 VM

2016-01-14 Thread Dean


I am hoping that someone might be able to help me out on this one. I 
recently updated my Beaglebone Black Image as listed below in the hopes of 
running a script that would allow me to test the i/p and o/p's on my BBB. 
Unfortunately although the code compiles and there does not appear to be 
any issues there the GPIO port to be updated simply does not take. I 
highlighted the problem in yellow. Any help or insight into this would 
really be appreciated. Thanks in advance.


GPS Overlay not working on Beaglebone Black 4.1.12-ti-r29 Ubuntu 15.04 and 
Debian 8.2 VM


Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux


BeagleBoard.org Debian Image 2015-11-12


/* 

* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/

*

* This program is free software; you can redistribute it and/or modify

* it under the terms of the GNU General Purpose License Version 2 as

* published by the Free Software Foundation

*

* Original from: 
github.com/jadonk/validation-scripts/blob/master/test-capemgr/ 

*

* Modified by Derek Molloy for the example on www.derekmolloy.ie

* that maps GPIO pins for the example

*/


/dts-v1/;

/plugin/;


/{

compatible = "ti,beaglebone", "ti,beaglebone-black";

part-number = "DM-GPIO-Test";

version = "00A0";


fragment@0 {

target = <_pinmux>;

__overlay__ {

pinctrl_test: DM_GPIO_Test_Pins {

pinctrl-single,pins = <


0x078 0x07 /* P9_12 60 OUTPUT MODE7 - The LED Output */

0x184 0x2f /* P9_24 15 INPUT MODE7 none - The Button Input */

0x034 0x37 /* P8_11 45 INPUT MODE7 pullup - Yellow Wire */

0x030 0x27 /* P8_12 44 INPUT MODE7 pulldown - Green Wire */

0x024 0x2f /* P8_13 23 INPUT MODE7 none - White Wire */

/* OUTPUT GPIO(mode7) 0x07 pulldown, 0x17 pullup, 0x?f no pullup/down */

/* INPUT GPIO(mode7) 0x27 pulldown, 0x37 pullup, 0x?f no pullup/down */


>;

};

};

};


fragment@1 {

target = <>;

__overlay__ {

test_helper: helper {

compatible = "bone-pinmux-helper";

pinctrl-names = "default";

pinctrl-0 = <_test>;

status = "okay";

};

};

};

};


root@beaglebone:~/boneDeviceTree/overlay# more build


#!/bin/bash 

echo "Compiling the overlay from .dts to .dtbo"


dtc -O dtb -o DM-GPIO-Test-00A0.dtbo -b 0 -@ DM-GPIO-Test.dts


root@beaglebone:~/boneDeviceTree/overlay# ./build


Compiling the overlay from .dts to .dtbo


root@beaglebone:~/boneDeviceTree/overlay# ls -al


total 20

drwxrwxr-x 2 root root 4096 Nov 12 2015 .

drwxrwxr-x 10 root root 4096 Nov 12 2015 ..

-rw-r--r-- 1 root root 986 Nov 12 21:23 DM-GPIO-Test-00A0.dtbo

-rw-r--r-- 1 root root 1591 Nov 12 2015 DM-GPIO-Test.dts

-rwxr-xr-x 1 root root 124 Nov 12 2015 build


root@beaglebone:~/boneDeviceTree/overlay# cp DM-GPIO-Test-00A0.dtbo 
/lib/firmware/


root@beaglebone:/lib/firmware# cat $SLOTS

0: PF -1 

1: PF -1 

2: PF -1 

3: PF -1 

4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln


root@beaglebone:/lib/firmware# echo DM-GPIO-Test > $SLOTS 


root@beaglebone:/lib/firmware# cat $SLOTS

0: PF -1 

1: PF -1 

2: PF -1 

3: PF -1 

4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln

5: P-O-L- 1 Override Board Name,00A0,Override Manuf,DM-GPIO-Test

root@beaglebone:/lib/firmware# cat $PINS|grep 878


pin 30 (44e10878.0) 0037 pinctrl-single 

root@beaglebone:/lib/firmware# cat $PINS|grep 984

pin 97 (44e10984.0) 0037 pinctrl-single 

root@beaglebone:/lib/firmware# cat $PINS|grep 834

pin 13 (44e10834.0) 0027 pinctrl-single 

root@beaglebone:/lib/firmware# cat $PINS|grep 830

pin 12 (44e10830.0) 0027 pinctrl-single 

root@beaglebone:/lib/firmware# cat $PINS|grep 824

pin 9 (44e10824.0) 0027 pinctrl-single 




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

[beagleboard] Cannot Set Static IP address on Beaglebone Black Version 4.1.12-ti-r29 Ubuntu 15.04 and Debian 8.2

2016-01-14 Thread Dean

 


I would like to access the internet while I am on my BBB so that I can 
update some files using git. Unfortunately I have not been successful in 
gaining access to the internet through my BBB. I tried the link below 
without success. I had assumed that the Debian configuration would be the 
procedure that I am after. Having said that I also tried Coonman, but it 
too did not work as there was a file missing and I am still not certain if 
this procedure is relevant given the system that I am using as listed 
below. Any suggestions out there? Thanks in advance if someone replies.




Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux


BeagleBoard.org Debian Image 2015-11-12


http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/

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

Re: [beagleboard] Cannot Fully Disable HDMI device tree overlay, HDMI Okay/HDMIN to be specific.

2016-01-04 Thread dean . bate



On Wednesday, December 9, 2015 at 8:19:06 PM UTC-7, Dean Bate wrote:
>
> Thanks for the reply. In the link that you sent me 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 Is the 
> procedure as listed in section 3.2 (i.e.flash the eMMC) all that is 
> required to update my BB image or is there more to it ? I am very new at 
> this and I am trying to decipher all that is relevant in getting the 
> following command to work ...
>
> $ sudo sh -c "echo BB-SPIDEV1 > $SLOTS
>
> Regards,
>
> Dean
>
> On Wed, Dec 9, 2015 at 3:04 PM, Robert Nelson <robertcnel...@gmail.com> 
> wrote:
>
>> >
>> > I am using Ubuntu 15.04 and the BB Debian image on my BBB is 
>> 2014-04-23. I
>> > have been trying for some days now to disable my HDMI and HDMIN 
>> overlays so
>>
>> It would have been faster to first upgrade to "2015-11-03
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03
>>
>> > that I can access my BB-SPIDEV1 with limited success. One command in
>> > particular (i.e. optargs=quiet
>> > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN) does indeed 
>> disable
>> > HDMI yet with that said it will not allow me to enable SPIDEV1. I have
>> > boldface highlighted the commands that were used as well as the o/p for
>> > presentation purposes. Any insight into resolving this problem would be
>> > helpful and much appreciated. Further note: I also tried
>> > optargs=capemgr.disable_partno=BB-BONELT-HDMI and all to no avail.
>>
>> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>> optargs=capemgr.enable_partno=BB-SPIDEV1
>>
>> Then that would have worked out of the box..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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/FsKmr7hUksg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> For those that might benefit from my findings. Initially I could not flash 
the BBB. Why ? The driver for my card reader is not supported under Linux. 
I have yet to determine if I will now be able to disable the HDMI with this 
latest image
 

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

Re: [beagleboard] Cannot Fully Disable HDMI device tree overlay, HDMI Okay/HDMIN to be specific.

2015-12-09 Thread Dean Bate

Thanks for the reply. In the link that you sent me
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 Is the
procedure as listed in section 3.2 (i.e.flash the eMMC) all that is
required to update my BB image or is there more to it ? I am very new at
this and I am trying to decipher all that is relevant in getting the
following command to work ...

$ sudo sh -c "echo BB-SPIDEV1 > $SLOTS

Regards,

Dean

On Wed, Dec 9, 2015 at 3:04 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> >
> > I am using Ubuntu 15.04 and the BB Debian image on my BBB is 2014-04-23.
> I
> > have been trying for some days now to disable my HDMI and HDMIN overlays
> so
>
> It would have been faster to first upgrade to "2015-11-03
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03
>
> > that I can access my BB-SPIDEV1 with limited success. One command in
> > particular (i.e. optargs=quiet
> > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN) does indeed
> disable
> > HDMI yet with that said it will not allow me to enable SPIDEV1. I have
> > boldface highlighted the commands that were used as well as the o/p for
> > presentation purposes. Any insight into resolving this problem would be
> > helpful and much appreciated. Further note: I also tried
> > optargs=capemgr.disable_partno=BB-BONELT-HDMI and all to no avail.
>
> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> optargs=capemgr.enable_partno=BB-SPIDEV1
>
> Then that would have worked out of the box..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/FsKmr7hUksg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] YouTube tutorial video to install JTAG connector on BeagleBone Black

2014-09-30 Thread Dean Davis

I was trying to find a tutorial on how to install the JTAG connector on the 
BeagleBone Black and the only one I could find is this one: 
https://www.youtube.com/watch?v=7JmHn7aN2FU

Does anyone know of another?

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

[beagleboard] Re: BBB Bare Metal with HDMI

2014-07-28 Thread dean . wedel

Travis:

Would you be willing to share your HDMI code in it's current state? I'd 
like to be able to play with it and see if I could get something working 
with the hardware I've got.

Thanks in advance!

Sincerely,
Dean


On Monday, April 14, 2014 9:50:23 AM UTC-7, dean@gmail.com wrote:

 Travis:

 I know that you have alot going on there with other projects, but just 
 checking if you have any progress on bare-metal HDMI code at this point? 
 I'm looking forward to what you have to show. Especially the pin-muxing 
 part :-)

 Sincerely,
 Dean


 On Wednesday, March 26, 2014 10:07:41 AM UTC-7, dean@gmail.com wrote:

 Thanks alot for all your efforts! I'll keep an eye on this group for your 
 developments.

 On Tuesday, March 25, 2014 9:51:57 AM UTC-7, Travis Estep wrote:

 Yes, I do have this somewhat working now. It has taken a lot of time and 
 many different resources to get to where I am now, but progress is coming 
 along slowly. I have a few other projects going on in parallel, so I don't 
 have all the time if like to devote to it. I should have the code in a 
 stable and mostly functional state pretty soon. But I wouldn't expect ago 
 of the bells and whistles to be working. I'll post back here with the Git 
 repo once I've uploaded it.

 Also, I plan to post any and all docs and information along with the 
 code so that the community can get involved and help make this driver fully 
 functional. Just keep an eye on this post for the next couple of weeks.



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

[beagleboard] Re: BBB Bare Metal with HDMI

2014-04-14 Thread dean . wedel

Travis:

I know that you have alot going on there with other projects, but just 
checking if you have any progress on bare-metal HDMI code at this point? 
I'm looking forward to what you have to show. Especially the pin-muxing 
part :-)

Sincerely,
Dean


On Wednesday, March 26, 2014 10:07:41 AM UTC-7, dean@gmail.com wrote:

 Thanks alot for all your efforts! I'll keep an eye on this group for your 
 developments.

 On Tuesday, March 25, 2014 9:51:57 AM UTC-7, Travis Estep wrote:

 Yes, I do have this somewhat working now. It has taken a lot of time and 
 many different resources to get to where I am now, but progress is coming 
 along slowly. I have a few other projects going on in parallel, so I don't 
 have all the time if like to devote to it. I should have the code in a 
 stable and mostly functional state pretty soon. But I wouldn't expect ago 
 of the bells and whistles to be working. I'll post back here with the Git 
 repo once I've uploaded it.

 Also, I plan to post any and all docs and information along with the code 
 so that the community can get involved and help make this driver fully 
 functional. Just keep an eye on this post for the next couple of weeks.



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

[beagleboard] Re: BBB Bare Metal with HDMI

2014-03-26 Thread dean . wedel

Thanks alot for all your efforts! I'll keep an eye on this group for your 
developments.

On Tuesday, March 25, 2014 9:51:57 AM UTC-7, Travis Estep wrote:

 Yes, I do have this somewhat working now. It has taken a lot of time and 
 many different resources to get to where I am now, but progress is coming 
 along slowly. I have a few other projects going on in parallel, so I don't 
 have all the time if like to devote to it. I should have the code in a 
 stable and mostly functional state pretty soon. But I wouldn't expect ago 
 of the bells and whistles to be working. I'll post back here with the Git 
 repo once I've uploaded it.

 Also, I plan to post any and all docs and information along with the code 
 so that the community can get involved and help make this driver fully 
 functional. Just keep an eye on this post for the next couple of weeks.


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

[beagleboard] Re: BBB Bare Metal with HDMI

2014-03-24 Thread dean . wedel

Travis:

Do you have HDMI output working on the Black with bare-metal? Do you have 
some code that you could share? I'm going bare-metal and would like to 
see what you have.

Thanks in advance!
Dean


On Saturday, January 18, 2014 1:26:27 PM UTC-7, Travis Estep wrote:

 Hello! I've been hacking around with the BBB for some time now, mostly 
 doing bare metal programming. On other boards that I build projects with, I 
 usually use one of my TFTs that I have laying around and use my custom 
 graphical interface for the UI part. But the BBB is different. While I have 
 been able to use a TFT with it, I'd like to get the HDMI up and running on 
 bare metal if possible. Looking over the datasheet for the TDA19988BHN I 
 can see that basically it just takes the LCD RGB signals and concerts that 
 to HDMI output. However, I have not had any luck with feeding it from the 
 library I wrote for my TFT. Is there something different I need to do with 
 the signals? Does the HDMI chip require some kind of initialization before 
 being used? The datasheet I have is one that I found on some third party 
 website and I suspect it may be incomplete. I can't find the official 
 datasheet on NXP's website at all.

 Any help would be appreciated. Any advice for anyone else who has had 
 success in this arena would also be much appreciated. Thanks in advance!



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

[beagleboard] Chipsee Touch-Screen Via Bare-Metal

2014-03-19 Thread dean . wedel

I have a Chipsee 7 LCD/capacitive touch-screen cape that I'm trying to 
interface via bare-metal on a Beaglebone-Black. I am able to drive the 
LCD fine and it works very good. The problem is I'm having difficulty 
understanding the Touch-Screen and interfacing with it.

Now, according to the Chipsee supplied schematic the touch interface has 3 
signals: GPIO1(bit #17), I2C1_SCL, and I2C1_SDA. I can read the event 
flag on GPIO1 (bit #17) just fine and it works as expected as a boolean 
flag. However, I'm really having trouble getting any serial data over SDA. 
I think that my pin/muxing is correctly set to mode#2 and I'm reading 
from data offset at memory 0x4802A000. However, I always get a value of 
0x87 at all times.

Anyone have a suggestion on this?

Thanks in advance!
Dean


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

Re: [beagleboard] Electrical isolation of BBB's ethernet port

2013-11-07 Thread Dean Franks

Yes, it is possible to couple the ports using isolation capacitors instead of 
transformers. This is not unusual in blade/backplane systems.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

46 matches

Mail list logo