Re: [beagleboard] BegleBone Black stops oscillating and not make PORz after power up

[Николай Курочкин]

Perhaps. But how it is connected with the recording in the flash memory. 
eMMC powered from different supply VDD_3V3B. According to documentation it 
takes about 50mA in write mode. So why VDD_1V8 drops down ? Bad 5V power 
from USB ? I will examine this issue. But in all other cases BBB works 
well. I have to find a workarownd.
Externally it looks like some exception or power fail after some time of 
extensive write to eMMC. I should kill some more BBB to find an answer

вторник, 11 октября 2016 г., 22:13:22 UTC+3 пользователь john3909 написал:
>
> If the BBB oscillator is not running, then I suspect the processor is bad. 
> If you have two boards with the same issue, then I suspect the power supply 
> you are using is bad. One of the big issues with the BBB is it doesn’t like 
> to power down. Look at sheet 2 of the OSD335x schematics
>
>
> http://octavosystems.com/octavosystems.com/wp-content/uploads/2016/05/OSD3358-SBC-Referece-Design.pdf
>
> You will see some protection circuitry at the bottom center of the sheet. 
> This ensures the voltage difference between the 3v3 and 1v8 is never 
> greater than 2V. The BBB does not have any such circuitry so when the 5V 
> drops quickly, it is possible for the 1v8 to drop quicker than the 3v3 and 
> hence killing the processor. This happened to me and I had to replace the 
> processor.
>
> The Beagleboard-x15 does have the same protection circuitry 
> (BeagleBoard-X15_RevA2.pdf sheet 4). 
>  
> Regards,
> John
>
>
>
>
> On Oct 11, 2016, at 7:05 AM, Николай Курочкин  > wrote:
>
> Two BeagleBone black boards with 1GHZ processors do not make boot sequece 
> after some unsucceseful attemts to format eMMC.
> It looks like they do not make PORz sequence. Both ocillators inacvtive. 
> NRESET_INOUT is low. PORZn input high. All power voltages are OK.
> I use simple code wich make BBB to act as USB flash drive to monitor eMMC 
> with my PC. Code based on TI usb_dev_msc example in StarterWare.
> It begin happens only with new boards. Old revision boards works OK.
> Any body can help ?
> I going to use JTAG to debug this processors but not shure that JTAG will 
> work in this case.
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/09fb54d2-3afa-4191-b10b-856ad52ae245%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ce78c227-2ecb-44e4-b823-522ba0ebff65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BegleBone Black stops oscillating and not make PORz after power up

[John Syne]

This problem will not occur when burning eMMC. This problem will only occur 
when removing the 5V rail. 

BTW, do not flash eMMC with USB power as this will not work. Always use a good 
5V power supply connected to the 5V plug. 

Regards,
John




> On Oct 12, 2016, at 3:40 AM, Николай Курочкин  wrote:
> 
> Perhaps. But how it is connected with the recording in the flash memory. eMMC 
> powered from different supply VDD_3V3B. According to documentation it takes 
> about 50mA in write mode. So why VDD_1V8 drops down ? Bad 5V power from USB ? 
> I will examine this issue. But in all other cases BBB works well. I have to 
> find a workarownd.
> Externally it looks like some exception or power fail after some time of 
> extensive write to eMMC. I should kill some more BBB to find an answer
> 
> вторник, 11 октября 2016 г., 22:13:22 UTC+3 пользователь john3909 написал:
> If the BBB oscillator is not running, then I suspect the processor is bad. If 
> you have two boards with the same issue, then I suspect the power supply you 
> are using is bad. One of the big issues with the BBB is it doesn’t like to 
> power down. Look at sheet 2 of the OSD335x schematics
> 
> http://octavosystems.com/octavosystems.com/wp-content/uploads/2016/05/OSD3358-SBC-Referece-Design.pdf
>  
> 
> 
> You will see some protection circuitry at the bottom center of the sheet. 
> This ensures the voltage difference between the 3v3 and 1v8 is never greater 
> than 2V. The BBB does not have any such circuitry so when the 5V drops 
> quickly, it is possible for the 1v8 to drop quicker than the 3v3 and hence 
> killing the processor. This happened to me and I had to replace the processor.
> 
> The Beagleboard-x15 does have the same protection circuitry 
> (BeagleBoard-X15_RevA2.pdf sheet 4). 
>  
> Regards,
> John
> 
> 
> 
> 
>> On Oct 11, 2016, at 7:05 AM, Николай Курочкин gmail.com 
>> > wrote:
>> 
>> Two BeagleBone black boards with 1GHZ processors do not make boot sequece 
>> after some unsucceseful attemts to format eMMC.
>> It looks like they do not make PORz sequence. Both ocillators inacvtive. 
>> NRESET_INOUT is low. PORZn input high. All power voltages are OK.
>> I use simple code wich make BBB to act as USB flash drive to monitor eMMC 
>> with my PC. Code based on TI usb_dev_msc example in StarterWare.
>> It begin happens only with new boards. Old revision boards works OK.
>> Any body can help ?
>> I going to use JTAG to debug this processors but not shure that JTAG will 
>> work in this case.
>> 
>> -- 
>> For more options, visit http://beagleboard.org/discuss 
>> 
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@ <>googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/09fb54d2-3afa-4191-b10b-856ad52ae245%40googlegroups.com
>>  
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/ce78c227-2ecb-44e4-b823-522ba0ebff65%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

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

[beagleboard] Re: Beaglebone black edit default am335x-boneblack.dts device tree

[Leonardo Romor]

Hello, I think I had a similar issue, and I would like to report it as well:

If you set a gpio configuration with the dto the kernel correctly loads it, 
but when you export one gpio from that peripheral for the first time, the 
kernel reset the configuration. I solved this by running a script on boot 
that exports the first GPIO for every peripheral and this actually solves 
this problem.
I think is an issue  of the kernel

Il giorno mercoledì 19 agosto 2015 08:31:32 UTC+2, Paco Dupont ha scritto:
>
> Thanks for your answer Andrew but I need that the board setup correctly 
> the pin at boot time (to avoid any trouble in the time elapsed between the 
> DTB is load and the kernel is ready).
> I'm actually facing a strange thing, 1st the number I used to set gpio3_21 
> was wrong : gpio = <107 0>; This call require the GPIO number on the bank 
> and not the PIN number. So using : gpio = <21 0>; I end up with that result 
> :
>
> root@arm:~# cat /sys/kernel/debug/gpio
> GPIOs 0-31, platform/44e07000.gpio, gpio:
>  gpio-6   (cd  ) in  hi IRQ
>
> GPIOs 32-63, platform/4804c000.gpio, gpio:
>  gpio-53  (?   ) out lo
>  gpio-54  (?   ) out lo
>  gpio-55  (?   ) out hi
>  gpio-56  (?   ) out lo
>
> GPIOs 64-95, platform/481ac000.gpio, gpio:
>
> GPIOs 96-127, platform/481ae000.gpio, gpio:
>  gpio-117 (TOR input   ) out lo
> root@arm:~# cat /sys/kernel/debug/gpio
> GPIOs 0-31, platform/44e07000.gpio, gpio:
>  gpio-6   (cd  ) in  hi IRQ
>
> GPIOs 32-63, platform/4804c000.gpio, gpio:
>  gpio-53  (?   ) out hi
>  gpio-54  (?   ) out lo
>  gpio-55  (?   ) out hi
>  gpio-56  (?   ) out lo
>
> GPIOs 64-95, platform/481ac000.gpio, gpio:
>
> GPIOs 96-127, platform/481ae000.gpio, gpio:
>  gpio-117 (TOR input   ) out lo
>
> So this is nice because that's means my DTB is correctly loaded, but the 
> pinmux register didn't change :
> root@arm:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins|grep 9ac
> pin 107 (44e109ac.0) 0027 pinctrl-single
>
> 0x27 means the register is set to INPUT | MODE7 ... Why  The gpio 
> setup and his register differ ... Can this cause me any trouble ? Or should 
> I ignore it ? Is it a problem from my pinctrl,pin setup in the DTB ?
>
>
> Le mercredi 19 août 2015 06:35:25 UTC+2, AndrewTaneGlen a écrit :
>>
>> I had trouble (viz. gave up) working with input pins with the device 
>> tree. I ended up doing all the init at run time (once I'd made sure nothing 
>> else was using the same pins in the device tree).
>> Check that you have removed any reference to the HDMI in your 
>> 'am335x-bone-common-no-capemgr.dtsi' file. I had to remove a 'status = 
>> "okay"' from the standard ''am335x-bone-common.dtsi', not sure if this is 
>> the same in the 'no cape' variant.
>>
>> For BBB expansion header P9, pin 23 (GPIO 1_17), AKA pin 49, I do the 
>> following to intialise an input for use as a switch:
>>
>> echo "49" > /sys/class/gpio/export
>> echo in > /sys/class/gpio/gpio49/direction
>> echo 1 > /sys/class/gpio/gpio49/active_low
>>
>> To read in the state I then use:
>> head -1 /sys/class/gpio/gpio49/value
>>
>> e.g., in a script, use:
>>
>> SWITCH=$(head -1 /sys/class/gpio/gpio49/value)
>>
>> if [ ${SWITCH} = "1" ]; then
>> ...
>> fi
>>
>> For outputs I use the 'standard' led interface, as already used in the 
>> BBB device tree for the heartbeat/mmc leds.
>> e.g., with the pnmux as you have done, add something like the following 
>> to the 'leds' section in the common dtsi file:
>>
>> led@6 {
>> label = "my_led";
>> gpios <&gpio1 16 GPIO_ACTIVE_HIGH>;
>> linux,default-trigger = "none";
>> default-state = "off";
>> };
>>
>> Then set the output state as follows:
>>
>> echo 1 > /sys/devices/leds.4/leds/my_led/value
>>
>> Hope that helps.
>> Andrew.
>>
>> On Wednesday, 19 August 2015 01:16:30 UTC+12, Paco Dupont wrote:
>>>
>>> I've replace the last part I added (&ocp...) by Nelson's advice on this 
>>> post : 
>>> https://groups.google.com/d/msg/beagleboard/iW4i-xy9zJw/JFrr5M9_IwAJ
>>> &gpio3 {
>>>  torout0 {
>>>   gpio-hog;
>>>   gpios = <107 0>;
>>>   output-low;
>>>   line-name = "TOR input";
>>>  };
>>> };
>>>
>>> Just trying for 1 pin but still the same output no change ...
>>>
>>

-- 
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/c84b6570-b0f7-4463-91b8-c4ade04f959a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] GPIO export and device tree overlay on boot.

[Leonardo Romor]

Hi,

I encountered the following behavior (an issue for me) while working with 
PRUs, device trees overlays and the gpio export filesystem.

I guess this is a kernel related problem to the filesystem drivers in 
/sys/class/gpio/export, I have a stable-4.4-bone-rt kernel on a debian. 

when I define a custom boot configuration, for example two gpios of the 
peripheral gpio2 they get correctly configured as outputs and the PRU 
normally manages them (or other process that access to the gpio2 peripheral 
through memory mapping) until I export another GPIO from the same 
peripheral (gpio2) but another gpio. It's like if they are all reset to 
inputs during the export ignoring the initial device tree configuration.
I discovered thsi while using BeagleG + Adafruit python library (that uses 
internally the filesystem exports) and what I found was that the dto 
configuration gets overridden during the export.
What I did to solve the problem was a simple script that exported for each 
peripheral the first gpio solving the issue.


Is this meant to be like that? Shouldn't the kernel respect the dto 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/96ebea25-ea70-480c-b86a-87c75fb12812%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] gdbserver shared library PRU loader

[Jelle Spijker]

Hi All,

I'm running Arch Linux on my BBB, so no remoteproc for me :-( when working with 
the PRU.

In my setup I'm developing a shared library that loads a simple PRU program via 
a unittest to verify if it works. Because I work with prussdrv the program 
should be run with sudo. If that it is the case the shared library can't be 
found, so I have to export LD_LIBRARY=../lib/ for my super user. Now debugging 
works for unit test, but as soon as I have to step into the code of the shared 
library, it doesn't show the code, so I can't figure out where my program hangs.


If anybody knows how to load a PRU firmware with out being root it is much 
preferred.


I'm currently executing gdbserver with the following command:

su --command="export LD_LIBRARY_PATH=../lib && gdbserver localhost:8080 
./runTests"

My current code is one of the most basic pieces just to load a PRU program, 
which toggles a pin, to drive a steppermotor, but I can't see any a pattern on 
my scope, so I assume it doesn't get load, which I can't verify.


Fragment of the devicetree:

/ {
   compatible = "ti,beaglebone", "ti,beaglebone-black", "ti,beaglebone-green";

   // identification
   part-number = "MTI-CATAMARAN";
   version = "00A0";

   // resources this cape uses
   exclusive-use =
  "P9.39",  // AIN0
  "P9.40",  // AIN1
  "P9.37",  // AIN2
  "P9.38",  // AIN3
  "P9.33",  // AIN4
  "P9.36",  // AIN5
  "P9.35",  // AIN6
"P8.44",  /* Sonar front */
"P8.45",  /* Sonar SB */
"P8.46",  /* Sonar PS */
"P8.41",  /* Sonar front Step */
"P8.42",  /* Sonar front Dir */
"P9.13",   /* uart4_txd IMU */
"P9.11",   /* uart4_rxd IMU */

  "tscadc",  // hardware ip used
"pruss";


   fragment@0 {
  target = <&tscadc>;
  __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@1 {
target = <&pruss>;
__overlay__ {

  status = "okay";
};
  };

  fragment@2 {
target = <&am33xx_pinmux>;
__overlay__ {

pru_pru_pins: pinmux_pru_pru_pins {
pinctrl-single,pins = <
BONE_P8_41 (PIN_OUTPUT_PULLDOWN | MUX_MODE5) /* 
lcd_data5.pr1_pru1_pru_r30_4, MODE5 | OUTPUT | PRU, Sonar front Dir */
BONE_P8_42 (PIN_OUTPUT_PULLDOWN | MUX_MODE5) /* 
lcd_data4.pr1_pru1_pru_r30_5, MODE5 | OUTPUT | PRU, Sonar front Step */
BONE_P8_44 (PIN_INPUT_PULLDOWN | MUX_MODE6) /* 
lcd_data3.pr1_pru1_pru_r31_3, MODE6 | INPUT | PRU, Sonar front */
BONE_P8_45 (PIN_INPUT_PULLDOWN | MUX_MODE6) /* 
lcd_data1.pr1_pru1_pru_r31_0, MODE6 | INPUT | PRU, Sonar PS */
BONE_P8_46 (PIN_INPUT_PULLDOWN | MUX_MODE6) /* 
lcd_data0.pr1_pru1_pru_r31_1, MODE6 | INPUT | PRU, Sonar SB */
>;
};

bb_uart4_pins: pinmux_bb_uart4_pins {
pinctrl-single,pins = <
  BONE_P9_13 (PIN_OUTPUT | MUX_MODE6)  // gpmc_wpn.uart4_txd_mux2
  BONE_P9_11 (PIN_INPUT  | MUX_MODE6)  // gpmc_wait0.uart4_rxd_mux2
>;
  };
};
  };

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

};


The PRU firmware:

#include 
#include "resource_table_empty.h"

volatile register unsigned int __R31, __R30;

int main(void)
{
unsigned int i;

for (i = 0; i < 200; i++) {
__R30 = __R30 | (1 << 5); // HIGH
__delay_cycles(6000);
__R30 = __R30 & ~(1 << 5); // LOW
__delay_cycles(6000);
}

__R31 = 32 | 3; // send interrupt to host
__halt();

/* Should never return */
return 0;
}


Fragment of the UnitTest (Google test) (This code I can step through with my 
IDE):

TEST(Controller, PRU_Toggle) {
using namespace oCpt::components::controller;
using namespace oCpt;
World::ptr world = World::ptr(new World());
BBB::ptr controller = BBB::ptr(new BBB(world));
BBB *bbb = static_cast(controller.get());
bbb->loadPRUfirmware(1,"./SonarArray.out");
}


Fragment of the Shared library:

void BBB::loadPRUfirmware(const unsigned int &number, const std::string 
&firmwareLocation) {
//Initialize structure used by prussdrv_pruintc_intc
tpruss_intc_initdata pruss__intc_initdata = PRUSS_INTC_INITDATA;
//Allocate and initialize memory
prussdrv_init();
prussdrv_open(PRU_EVTOUT0);
//Map PRU's interrupts
prussdrv_pruintc_init(&pruss__intc_initdata);
//Load and execute the PRU program on the PRU
prussdrv_exec_program(number, firmwareLocation.c_str());
// Wait for event completion from PRU, returns PRU_EVTOUT_0 number
//int n = p

[beagleboard] Re: gdbserver shared library PRU loader

[TJF]

Hi!

Am Mittwoch, 12. Oktober 2016 15:05:12 UTC+2 schrieb Jelle Spijker:
>
> Hi All,
>
> I'm running Arch Linux on my BBB, so no remoteproc for me :-( when working 
> with the PRU.
>
>
You're lucky, you didn't waste time for testing remoteproc.
 

> Because I work with prussdrv the program should be run with sudo. If that it 
> is the case the shared library can't be found, so I have to export 
> LD_LIBRARY=../lib/ for my super user.
>
>
prussdrv doesn't need root privileges, but the user needs at least read 
access to the interrupt handlers (/dev/uio[0-7]).

Regarding the linker issue: did you update the cache for the run-time 
linker (sudo ldconfig).

Fragment of the Shared library:
>
> void BBB::loadPRUfirmware(const unsigned int &number, const std::string 
> &firmwareLocation) {
> //Initialize structure used by prussdrv_pruintc_intc
> tpruss_intc_initdata pruss__intc_initdata = PRUSS_INTC_INITDATA;
> //Allocate and initialize memory
> prussdrv_init();
> prussdrv_open(PRU_EVTOUT0);
> //Map PRU's interrupts
> prussdrv_pruintc_init(&pruss__intc_initdata);
> //Load and execute the PRU program on the PRU
> prussdrv_exec_program(number, firmwareLocation.c_str());
> // Wait for event completion from PRU, returns PRU_EVTOUT_0 number
> //int n = prussdrv_pru_wait_event(PRU_EVTOUT0);
> //prussdrv_pru_disable(number);
> //prussdrv_exit();
> }
>
>
All prussdrv functions return a value (zero in case of success). What 
return values do you get?
 
Regards

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

[beagleboard] Re: gdbserver shared library PRU loader

[TJF]

Just found another issue:

Am Mittwoch, 12. Oktober 2016 15:05:12 UTC+2 schrieb Jelle Spijker:
>
> Fragment of the Shared library:
>
> void BBB::loadPRUfirmware(const unsigned int &number, const std::string 
> &firmwareLocation) {
> //Initialize structure used by prussdrv_pruintc_intc
> tpruss_intc_initdata pruss__intc_initdata = PRUSS_INTC_INITDATA;
> //Allocate and initialize memory
> prussdrv_init();
> prussdrv_open(PRU_EVTOUT0);
> //Map PRU's interrupts
> prussdrv_pruintc_init(&pruss__intc_initdata);
> //Load and execute the PRU program on the PRU
> prussdrv_exec_program(number, firmwareLocation.c_str());
> // Wait for event completion from PRU, returns PRU_EVTOUT_0 number
> //int n = prussdrv_pru_wait_event(PRU_EVTOUT0);
> //prussdrv_pru_disable(number);
> //prussdrv_exit();
> }
>
>
It should read (underscore before 0):

prussdrv_open(PRU_EVTOUT_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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1fd7eabf-f2e2-47b3-b238-884e44871c31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

[Robert Nelson]

On Tue, Oct 11, 2016 at 5:51 PM, Kevin Fructuoso
 wrote:
> Thanks for the link to the patch. I have not patched the kernel before.
>
> Could you please send a link that explains and walks me through how to patch
> the kernel? Thanks.
>
> Regards,
> Kevin F.

git clone https://github.com/RobertCNelson/yakbuild
cd yakbuild
cp recipe.sh.sample recipe.sh

Open recipe.sh

Change:
toolchain="gcc_linaro_gnueabihf_5"

to:
#toolchain="gcc_linaro_gnueabihf_5"

Enable:
toolchain="gcc_linaro_gnueabihf_4_7"

Change:
kernel_tag="4.4.19-ti-r41"

to:
kernel_tag="3.8.13-bone47"

run:

./build_kernel.sh

After the ".config - Linux/arm 3.8.13 Kernel Configuration" pop's up,
just hit ecape twice, select , hit enter, then hit CTRL-C to stop
build:

Next:

cd KERNEL/

wget 
https://raw.githubusercontent.com/RobertCNelson/bb-kernel/607ae2e36477357a4bb222f285fd7460d5230ab9/patches/net/0009-cpsw-search-for-phy.patch

patch -p1 < 0009-cpsw-search-for-phy.patch

cd ../
./tools/rebuild.sh  (this time build to completion)

Regards,


-- 
Robert Nelson
https://rcn-ee.com/

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

[beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

Hi:

I am running with 4.1.22-ti-rt-r59 and followed the instructions here 
http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black on 
how to install the SGX drivers.

All seems ok (no error while installing the GFX package) , until I got to 
check that the omaplfb and pvrsrvkm had loaded correctly.

root@beaglebone:~# lsmod | grep omaplfb
root@beaglebone:~# lsmod | grep omap
omap_rng4350  0
rng_core7433  1 omap_rng
spi_omap2_mcspi10673  0
root@beaglebone:~# lsmod | grep pvrsrvkm
pvrsrvkm  378818  0
root@beaglebone:~#

It doesn't look like omaplfp is loaded.

What would be your suggestion to debug why omaplfp did not load?

Regards,
JS

-- 
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/2c18720d-b970-4bac-86f2-ec56e0042c87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

By the way I thought I would provide the following information as well:

root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh start
sgx: Starting PVR
mknod: missing operand after '0'
Try 'mknod --help' for more information.


Regards,
JS




On Wednesday, October 12, 2016 at 4:20:06 PM UTC-5, Jean-Sebastien Stoezel 
wrote:
>
> Hi:
>
> I am running with 4.1.22-ti-rt-r59 and followed the instructions here 
> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black on 
> how to install the SGX drivers.
>
> All seems ok (no error while installing the GFX package) , until I got to 
> check that the omaplfb and pvrsrvkm had loaded correctly.
>
> root@beaglebone:~# lsmod | grep omaplfb
> root@beaglebone:~# lsmod | grep omap
> omap_rng4350  0
> rng_core7433  1 omap_rng
> spi_omap2_mcspi10673  0
> root@beaglebone:~# lsmod | grep pvrsrvkm
> pvrsrvkm  378818  0
> root@beaglebone:~#
>
> It doesn't look like omaplfp is loaded.
>
> What would be your suggestion to debug why omaplfp did not load?
>
> Regards,
> JS
>
>

-- 
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/6eb26dff-3343-4c99-b3a7-d1bdb52ca80c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Robert Nelson]

On Wed, Oct 12, 2016 at 4:20 PM, Jean-Sebastien Stoezel
 wrote:
> Hi:
>
> I am running with 4.1.22-ti-rt-r59 and followed the instructions here
> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black on how
> to install the SGX drivers.
>
> All seems ok (no error while installing the GFX package) , until I got to
> check that the omaplfb and pvrsrvkm had loaded correctly.
>
> root@beaglebone:~# lsmod | grep omaplfb
> root@beaglebone:~# lsmod | grep omap
> omap_rng4350  0
> rng_core7433  1 omap_rng
> spi_omap2_mcspi10673  0
> root@beaglebone:~# lsmod | grep pvrsrvkm
> pvrsrvkm  378818  0
> root@beaglebone:~#
>
> It doesn't look like omaplfp is loaded.
>
> What would be your suggestion to debug why omaplfp did not load?

It's not loaded, as the version your linked to on the elinux is an
older SGX release.

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Re: Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Robert Nelson]

On Wed, Oct 12, 2016 at 4:26 PM, Jean-Sebastien Stoezel
 wrote:
> By the way I thought I would provide the following information as well:
>
> root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh start
> sgx: Starting PVR
> mknod: missing operand after '0'
> Try 'mknod --help' for more information.

You mixing sgx instructions..

We don't have either:

v4.1.x-ti
or
v4.4.x-ti

working..

Feel free to use the old "v4.1.x-bone" kernel with those
instructions.. it's fbdev mode only...

I had very specific link in the text at:

http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black

->

http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29

Mainline (lts)

4.1.x BeagleBone/BeagleBone Black + SGX
--bone-kernel --lts

4.1.x BeagleBone/BeagleBone Black + RT + SGX
--bone-rt-kernel --lts

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh 


Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgSbRH9%2B6yFWQG2TRVt%3DMw2c0mBxHY48OAA6Hc%3DBv-bXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Question about /lib/modules on BeagleBoard-xm running Jessie

[David Glaser]

Hmm, this explains the lack of support for hid functionality in the gadget 
libraries.  The driver usb_f_hid.ko is present in the ti versions but not 
the generic arm version.  

I decided to move my development efforts to the BBB.  The Jessie release 
does have the usb_f_hid.ko driver.  The downside is that now I need a USB 
HUB since the BBB has only one host usb port.  Oh well.  Mebbe I should get 
an x15 (I love the choice of name - I remember the stream of new articles 
talking about yeager and the x15.

-David

>
>

-- 
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/5a6885ba-2618-43d7-a243-b685a903127a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

Hi Robert:

Thank you for the quick reply. 

How should I remove the old version I installed on the BBB? And should the 
newer version I should get be am33x-rt-v4.8?

Regards,
JS




On Wednesday, October 12, 2016 at 4:29:13 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Oct 12, 2016 at 4:20 PM, Jean-Sebastien Stoezel 
> > wrote: 
> > Hi: 
> > 
> > I am running with 4.1.22-ti-rt-r59 and followed the instructions here 
> > http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black 
> on how 
> > to install the SGX drivers. 
> > 
> > All seems ok (no error while installing the GFX package) , until I got 
> to 
> > check that the omaplfb and pvrsrvkm had loaded correctly. 
> > 
> > root@beaglebone:~# lsmod | grep omaplfb 
> > root@beaglebone:~# lsmod | grep omap 
> > omap_rng4350  0 
> > rng_core7433  1 omap_rng 
> > spi_omap2_mcspi10673  0 
> > root@beaglebone:~# lsmod | grep pvrsrvkm 
> > pvrsrvkm  378818  0 
> > root@beaglebone:~# 
> > 
> > It doesn't look like omaplfp is loaded. 
> > 
> > What would be your suggestion to debug why omaplfp did not load? 
>
> It's not loaded, as the version your linked to on the elinux is an 
> older SGX release. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2987f282-0465-46bf-809a-45d262ac582d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Robert Nelson]

On Wed, Oct 12, 2016 at 4:33 PM, Jean-Sebastien Stoezel
 wrote:
> Hi Robert:
>
> Thank you for the quick reply.
>
> How should I remove the old version I installed on the BBB? And should the
> newer version I should get be am33x-rt-v4.8?

Well, the "newest" version with any-kinda-working sgx is

am33x-v4.1

Just like those directions say..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Question about /lib/modules on BeagleBoard-xm running Jessie

[Robert Nelson]

On Wed, Oct 12, 2016 at 4:32 PM, David Glaser
 wrote:
> Hmm, this explains the lack of support for hid functionality in the gadget
> libraries.  The driver usb_f_hid.ko is present in the ti versions but not
> the generic arm version.

You could just rebuild the kernel...

> I decided to move my development efforts to the BBB.  The Jessie release
> does have the usb_f_hid.ko driver.  The downside is that now I need a USB
> HUB since the BBB has only one host usb port.  Oh well.  Mebbe I should get
> an x15 (I love the choice of name - I remember the stream of new articles
> talking about yeager and the x15.

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

It looks like we crossed replies/emails.

I am unsure what you mean by:
"
http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29 

 

Mainline (lts) 

4.1.x BeagleBone/BeagleBone Black + SGX 
--bone-kernel --lts 

4.1.x BeagleBone/BeagleBone Black + RT + SGX 
--bone-rt-kernel --lts 

cd /opt/scripts/tools/ 
git pull 
sudo ./update_kernel.sh  "

At this time I am not sure you are implying that I need to update the 
kernel, or that I need to get a different version of SGX from git. "Install 
the "4.1.x" lts/bone kernel: 
http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29";. The kernel I am 
using is 4.1.22-ti-rt-r59.
Would it be possible for you to clarify whether or not I have the right 
kernel, and, if not, point me to a kernel that would allow me to install 
am33x-v4.1, since this is the only version that currently works?


Regards,
JS


On Wednesday, October 12, 2016 at 4:40:39 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Oct 12, 2016 at 4:33 PM, Jean-Sebastien Stoezel 
> > wrote: 
> > Hi Robert: 
> > 
> > Thank you for the quick reply. 
> > 
> > How should I remove the old version I installed on the BBB? And should 
> the 
> > newer version I should get be am33x-rt-v4.8? 
>
> Well, the "newest" version with any-kinda-working sgx is 
>
> am33x-v4.1 
>
> Just like those directions say.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5f3d27f3-9b9d-494c-86b4-b7d30485b8a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Robert Nelson]

On Wed, Oct 12, 2016 at 4:50 PM, Jean-Sebastien Stoezel
 wrote:
> It looks like we crossed replies/emails.
>
> I am unsure what you mean by:
> "
> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29
>
> Mainline (lts)
>
> 4.1.x BeagleBone/BeagleBone Black + SGX
> --bone-kernel --lts
>
> 4.1.x BeagleBone/BeagleBone Black + RT + SGX
> --bone-rt-kernel --lts
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh  "
>
> At this time I am not sure you are implying that I need to update the
> kernel, or that I need to get a different version of SGX from git. "Install
> the "4.1.x" lts/bone kernel:
> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29";. The kernel I am
> using is 4.1.22-ti-rt-r59.
> Would it be possible for you to clarify whether or not I have the right
> kernel, and, if not, point me to a kernel that would allow me to install
> am33x-v4.1, since this is the only version that currently works?

Correct, you don't have the correct kernel..

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-rt-kernel --lts

Will get you what you want..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

Hi Robert:

Thank you for a quick and detailed answer. This is greatly appreciated.
I will give this a try tonight.

Regards,
Jean-Sebastien


> On Oct 12, 2016, at 17:03, Robert Nelson  wrote:
> 
> On Wed, Oct 12, 2016 at 4:50 PM, Jean-Sebastien Stoezel
>  wrote:
>> It looks like we crossed replies/emails.
>> 
>> I am unsure what you mean by:
>> "
>> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29
>> 
>> Mainline (lts)
>> 
>> 4.1.x BeagleBone/BeagleBone Black + SGX
>> --bone-kernel --lts
>> 
>> 4.1.x BeagleBone/BeagleBone Black + RT + SGX
>> --bone-rt-kernel --lts
>> 
>> cd /opt/scripts/tools/
>> git pull
>> sudo ./update_kernel.sh  "
>> 
>> At this time I am not sure you are implying that I need to update the
>> kernel, or that I need to get a different version of SGX from git. "Install
>> the "4.1.x" lts/bone kernel:
>> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29";. The kernel I am
>> using is 4.1.22-ti-rt-r59.
>> Would it be possible for you to clarify whether or not I have the right
>> kernel, and, if not, point me to a kernel that would allow me to install
>> am33x-v4.1, since this is the only version that currently works?
> 
> Correct, you don't have the correct kernel..
> 
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --bone-rt-kernel --lts
> 
> Will get you what you want..
> 
> Regards,
> 
> -- 
> Robert Nelson
> https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5AE98A72-5278-493E-9484-0D8FAD9F80E5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[Jean-Sebastien Stoezel]

Hi Robert:

I did upgrade to the latest -bone-rt kernel.
I am not getting the error I used to have when trying to restart PVR, but
suprisingly pvrsvrkm is not loaded

root@beaglebone:~# lsmod | grep omaplfb
root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh start
sgx: Starting PVR
root@beaglebone:~# lsmod | grep omaplfb
root@beaglebone:~# lsmod | grep omapl
root@beaglebone:~# lsmod | grep omap
omap_sham  19380  0
omap_aes   13255  0
omap_rng4338  0
rng_core7209  1 omap_rng
snd_soc_omap2565  1 snd_soc_davinci_mcasp
snd_soc_core  157683  3
snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_omap
snd_pcm_dmaengine   5045  2 snd_soc_core,snd_soc_omap
snd_pcm77695  4
snd_soc_davinci_mcasp,snd_soc_core,snd_soc_omap,snd_pcm_dmaengine
spi_omap2_mcspi10456  0
root@beaglebone:~# lsmod | grep pvrsrvkm
root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh restart
sgx: Restarting PVR
root@beaglebone:~# lsmod | grep pvr

Is there another way of checking whether omaplfb and pvrsrvkm are loaded?

Regards,
JS

On Wed, Oct 12, 2016 at 5:17 PM, Jean-Sebastien Stoezel <
js.stoe...@gmail.com> wrote:

> Hi Robert:
>
> Thank you for a quick and detailed answer. This is greatly appreciated.
> I will give this a try tonight.
>
> Regards,
> Jean-Sebastien
>
>
> > On Oct 12, 2016, at 17:03, Robert Nelson 
> wrote:
> >
> > On Wed, Oct 12, 2016 at 4:50 PM, Jean-Sebastien Stoezel
> >  wrote:
> >> It looks like we crossed replies/emails.
> >>
> >> I am unsure what you mean by:
> >> "
> >> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29
> >>
> >> Mainline (lts)
> >>
> >> 4.1.x BeagleBone/BeagleBone Black + SGX
> >> --bone-kernel --lts
> >>
> >> 4.1.x BeagleBone/BeagleBone Black + RT + SGX
> >> --bone-rt-kernel --lts
> >>
> >> cd /opt/scripts/tools/
> >> git pull
> >> sudo ./update_kernel.sh  "
> >>
> >> At this time I am not sure you are implying that I need to update the
> >> kernel, or that I need to get a different version of SGX from git.
> "Install
> >> the "4.1.x" lts/bone kernel:
> >> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29";. The kernel I
> am
> >> using is 4.1.22-ti-rt-r59.
> >> Would it be possible for you to clarify whether or not I have the right
> >> kernel, and, if not, point me to a kernel that would allow me to install
> >> am33x-v4.1, since this is the only version that currently works?
> >
> > Correct, you don't have the correct kernel..
> >
> > cd /opt/scripts/tools/
> > git pull
> > sudo ./update_kernel.sh --bone-rt-kernel --lts
> >
> > Will get you what you want..
> >
> > Regards,
> >
> > --
> > Robert Nelson
> > https://rcn-ee.com/
>

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

[beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

[William Hermans]

So I've been searching the groups here for the last several hours. I've 
tried several things, even noted that the device tree "binary" file 
(compiled file in /lib/firmware) was marked as executable. So I set the 
executable bit via chmod -x . . .Anyway, this is a custom device tree 
overlay binary, that enabled several GPO's 6 GPI's, and all 3 "dual 
channel" pwm modules. Plus I think uart4. The overlay fails to load at boot 
via /boot/uEnv.txt.

william@beaglebone:~$ dmesg |grep controller
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 
bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4 
rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
. . .
[2.167008] IPv6: Loaded, but administratively disabled, reboot required 
to enable
[2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'lcontroller' VER 'N/A' PR '0'
[2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,controller'
[3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4 
controller:00A0 (prio 0)



I have tried this with cape_universal=enable, as well as commented out( 
simply removed the text ).

william@beaglebone:~$ uname -r
4.4.14-ti-r34
william@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-05-01
william@beaglebone:~$ dtc -v
Version: DTC 1.4.1

So here is the funny part.

william@beaglebone:~$ sudo config-pin overlay controller
[sudo] password for william:
Loading led-controller overlay

william@beaglebone:~$ dmesg |grep controller
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 
bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4 
rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
[2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO 'controller' 
VER 'N/A' PR '0'
[2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,controller'
[3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4 
controller:00A0 (prio 0)
[ 1972.395048] bone_capemgr bone_capemgr: part_number 'controller', version 
'N/A'
[ 1972.395115] bone_capemgr bone_capemgr: slot #5: 'Override Board 
Name,00A0,Override Manuf,controller'
[ 1972.526297] bone_capemgr bone_capemgr: slot #5: dtbo 
'controller-00A0.dtbo' loaded; overlay id #0



Is this a known issue ? Or maybe I'm doing something wrong ? Maybe I need a 
different board file loaded at boot ?

william@beaglebone:~$ cat /boot/uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.4.14-ti-r34
#uuid=
#dtb=

##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)

##BeagleBone Black: HDMI (Audio/Video) disabled:
dtb=am335x-boneblack-emmc-overlay.dtb

##BeagleBone Black: eMMC disabled:
#dtb=am335x-boneblack-hdmi-overlay.dtb

##BeagleBone Black: HDMI Audio/eMMC disabled:
#dtb=am335x-boneblack-nhdmi-overlay.dtb

##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
#dtb=am335x-boneblack-overlay.dtb

##BeagleBone Black: wl1835
#dtb=am335x-boneblack-wl1835mod.dtb

##BeagleBone Green: eMMC disabled
#dtb=am335x-bonegreen-overlay.dtb

cmdline=coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
#cmdline=ipv6.disable=1 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M quiet cape_universal=enable 
video=HDMI-A-1:1024x768@60e

##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
cape_enable=bone_capemgr.enable_partno=controller

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh


william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
 5: P-O-L-   0 Override Board Name,00A0,Override Manuf,controller



The overlay source file does have some aspects similar to the universal IO 
overlays. dir-changable, init-hi/lo etc.



-- 
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/408d8389-6999-4d06-8b60-21795c240e92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

[William Hermans]

By the way, this has been tested consistently on one BBB RevC, and several(
tens ) of BBG's. By me personally, and another person, elsewhere.

On Wed, Oct 12, 2016 at 6:33 PM, William Hermans  wrote:

> So I've been searching the groups here for the last several hours. I've
> tried several things, even noted that the device tree "binary" file
> (compiled file in /lib/firmware) was marked as executable. So I set the
> executable bit via chmod -x . . .Anyway, this is a custom device tree
> overlay binary, that enabled several GPO's 6 GPI's, and all 3 "dual
> channel" pwm modules. Plus I think uart4. The overlay fails to load at boot
> via /boot/uEnv.txt.
>
> william@beaglebone:~$ dmesg |grep controller
> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
> . . .
> [2.167008] IPv6: Loaded, but administratively disabled, reboot
> required to enable
> [2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
> 'lcontroller' VER 'N/A' PR '0'
> [2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,controller'
> [3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
> controller:00A0 (prio 0)
>
>
>
> I have tried this with cape_universal=enable, as well as commented out(
> simply removed the text ).
>
> william@beaglebone:~$ uname -r
> 4.4.14-ti-r34
> william@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2016-05-01
> william@beaglebone:~$ dtc -v
> Version: DTC 1.4.1
>
> So here is the funny part.
>
> william@beaglebone:~$ sudo config-pin overlay controller
> [sudo] password for william:
> Loading led-controller overlay
>
> william@beaglebone:~$ dmesg |grep controller
> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
> [2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
> 'controller' VER 'N/A' PR '0'
> [2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,controller'
> [3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
> controller:00A0 (prio 0)
> [ 1972.395048] bone_capemgr bone_capemgr: part_number 'controller',
> version 'N/A'
> [ 1972.395115] bone_capemgr bone_capemgr: slot #5: 'Override Board
> Name,00A0,Override Manuf,controller'
> [ 1972.526297] bone_capemgr bone_capemgr: slot #5: dtbo
> 'controller-00A0.dtbo' loaded; overlay id #0
>
>
>
> Is this a known issue ? Or maybe I'm doing something wrong ? Maybe I need
> a different board file loaded at boot ?
>
> william@beaglebone:~$ cat /boot/uEnv.txt
> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>
> uname_r=4.4.14-ti-r34
> #uuid=
> #dtb=
>
> ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)
>
> ##BeagleBone Black: HDMI (Audio/Video) disabled:
> dtb=am335x-boneblack-emmc-overlay.dtb
>
> ##BeagleBone Black: eMMC disabled:
> #dtb=am335x-boneblack-hdmi-overlay.dtb
>
> ##BeagleBone Black: HDMI Audio/eMMC disabled:
> #dtb=am335x-boneblack-nhdmi-overlay.dtb
>
> ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
> #dtb=am335x-boneblack-overlay.dtb
>
> ##BeagleBone Black: wl1835
> #dtb=am335x-boneblack-wl1835mod.dtb
>
> ##BeagleBone Green: eMMC disabled
> #dtb=am335x-bonegreen-overlay.dtb
>
> cmdline=coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
> #cmdline=ipv6.disable=1 quiet
>
> #In the event of edid real failures, uncomment this next line:
> #cmdline=coherent_pool=1M quiet cape_universal=enable
> video=HDMI-A-1:1024x768@60e
>
> ##Example v3.8.x
> #cape_disable=capemgr.disable_partno=
> #cape_enable=capemgr.enable_partno=
>
> ##Example v4.1.x
> #cape_disable=bone_capemgr.disable_partno=
> cape_enable=bone_capemgr.enable_partno=controller
>
> ##enable Generic eMMC Flasher:
> ##make sure, these tools are installed: dosfstools rsync
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>
>
> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  5: P-O-L-   0 Override Board Name,00A0,Override Manuf,controller
>
>
>
> The overlay source file does have some aspects similar to the universal IO
> overlays. dir-changable, init-hi/lo etc.
>
>
>
> --
> 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/408d8389-6999-4d06-8b60-21795c240e92%40googlegroups.com
> 

Re: [beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

[William Hermans]

Additional information if this helps. P9.42 if I recall is one of the pins
that are tied together for mmc_cmd ? So, kind of has my attention.

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P8.8",
"P8.9",
"P8.10",
"P8.11",
"P8.12",
"P8.13",/* EHRPWM2B */
"P8.13",
"P8.14",
"P8.15",
"P8.16",
"P8.17",
"P8.18",
"P8.19",/* EHRPWM2A */
"P8.26",
"P8.27",
"P9.11",/* UART4_RX */
"P9.12",
"P9.13",/* UART4_TX */
"P9.14",/* EHRPWM1A  */
"P9.15",
"P9.16",/* EHRPWM1B  */
"P9.21",/* EHRPWM0A  */
"P9.22",/* EHRPWM0B  */
"P9.23",
"P9.25",
"P9.27",
"P9.28",
"P9.29",
"P9.30",
"P9.31",
*"P9.42",*
/* the hardware ip uses */
"uart4",
"ehrpwm0A",
"ehrpwm0B",
"ehrpwm1A",
"ehrpwm1B",
"ehrpwm2A",
"ehrpwm2B";

On Wed, Oct 12, 2016 at 6:37 PM, William Hermans  wrote:

> By the way, this has been tested consistently on one BBB RevC, and
> several( tens ) of BBG's. By me personally, and another person, elsewhere.
>
> On Wed, Oct 12, 2016 at 6:33 PM, William Hermans 
> wrote:
>
>> So I've been searching the groups here for the last several hours. I've
>> tried several things, even noted that the device tree "binary" file
>> (compiled file in /lib/firmware) was marked as executable. So I set the
>> executable bit via chmod -x . . .Anyway, this is a custom device tree
>> overlay binary, that enabled several GPO's 6 GPI's, and all 3 "dual
>> channel" pwm modules. Plus I think uart4. The overlay fails to load at boot
>> via /boot/uEnv.txt.
>>
>> william@beaglebone:~$ dmesg |grep controller
>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
>> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> . . .
>> [2.167008] IPv6: Loaded, but administratively disabled, reboot
>> required to enable
>> [2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
>> 'lcontroller' VER 'N/A' PR '0'
>> [2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
>> controller:00A0 (prio 0)
>>
>>
>>
>> I have tried this with cape_universal=enable, as well as commented out(
>> simply removed the text ).
>>
>> william@beaglebone:~$ uname -r
>> 4.4.14-ti-r34
>> william@beaglebone:~$ cat /etc/dogtag
>> BeagleBoard.org Debian Image 2016-05-01
>> william@beaglebone:~$ dtc -v
>> Version: DTC 1.4.1
>>
>> So here is the funny part.
>>
>> william@beaglebone:~$ sudo config-pin overlay controller
>> [sudo] password for william:
>> Loading led-controller overlay
>>
>> william@beaglebone:~$ dmesg |grep controller
>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
>> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> [2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
>> 'controller' VER 'N/A' PR '0'
>> [2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
>> controller:00A0 (prio 0)
>> [ 1972.395048] bone_capemgr bone_capemgr: part_number 'controller',
>> version 'N/A'
>> [ 1972.395115] bone_capemgr bone_capemgr: slot #5: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [ 1972.526297] bone_capemgr bone_capemgr: slot #5: dtbo
>> 'controller-00A0.dtbo' loaded; overlay id #0
>>
>>
>>
>> Is this a known issue ? Or maybe I'm doing something wrong ? Maybe I need
>> a different board file loaded at boot ?
>>
>> william@beaglebone:~$ cat /boot/uEnv.txt
>> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>>
>> uname_r=4.4.14-ti-r34
>> #uuid=
>> #dtb=
>>
>> ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)
>>
>> ##BeagleBone Black: HDMI (Audio/Video) disabled:
>> dtb=am335x-boneblack-emmc-overlay.dtb
>>
>> ##BeagleBone Black: eMMC disabled:
>> #dtb=am335x-boneblack-hdmi-overlay.dtb
>>
>> ##BeagleBone Black: HDMI Audio/eMMC disabled:
>> #dtb=am335x-boneblack-nhdmi-overlay.dtb
>>
>> ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
>> #dtb=am335x-boneblack-overlay.dtb
>>
>> ##BeagleBone Black: wl1835
>> #dtb=am335x-boneblack-wl1835mod.dtb
>>
>> ##BeagleBone Green: eMMC disabled
>> #dtb=am335x-bonegreen-overlay.dtb
>>
>> cmdline=coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> #cmdline=ipv6.disable=1 quiet
>>
>> #In the event of edid real failures, uncomment this next line:
>> #cmdline=coherent_pool=1M quiet cape_universal=enable