date:20191011

[beagleboard] Linux beaglebone 4.14.108-ti-r108, PWM mapping and write errors

2019-10-11 Thread Co M

 This is on BBB Linux beaglebone 4.14.108-ti-r108

On this new kernel I can see that cape_universal is being used in 
/boot/uEnv.txt so all, or quite of pwm's
are on in /sys/class/pwm/pwmchip#

Some of the pwms like GPIO 71 P8-46 used to be on  pwmchip6/pwm1 
but now exporting 1 > gpiochip6 says no device.

Based on this utility https://redypis.org/addons/bb_pins.php which uses the 
bash array from config_pin I can see
that p8_46 is on 0x3:ehrpwm2B which is EHRPWM2 (ePWM2) which is pwmchip6 
channel B
so export 1 (B) should work but now does not .

Furthermore more going to chips 6 folder and exporting 0 or un-exporting 
makes the gpio-6.0 going on and off which is fine, but
any attempt to write onto it fails

marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 10 ./duty_cycle 
10 ./duty_cycle
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 10 > ./duty_cycle 

-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 10 > enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 1 > enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ config-pin P8.46 pwm
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 1 > enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 0 > enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 0 > ./enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 1 > enable 
-bash: echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 1 ./duty_cycle 
1 ./duty_cycle
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ echo 1 > ./duty_cycle


marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ sudo echo 1 > enable 
[sudo] password for marius: 
echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ sudo echo on > enable 
echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ sudo echo default > 
enable 
echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ sudo echo okay > enable 
echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ sudo echo true > enable 
echo: write error: Invalid argument
marius@beaglebone:/sys/class/pwm/pwmchip6/pwm-6:0$ uname -a

Is there any updated information or I have to look into  the dts file and 
figure it out ? 
Is there any way to find the mapping from the sys filesystem between the 
KERNEL GPIO# --   PX.Y (rail name) and/sys/class/pwm/pwm-X.Y 

Thank you.

-- 
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/baaa91a8-b2c7-4274-a7c7-487cea1bb698%40googlegroups.com.

Re: [beagleboard] BeagleBone Black Pin Mode Configuration?

2019-10-11 Thread Ralph Stormer

*UPDATE:*

I have successfully loaded the pre-written NH7C *.dtbo* overlay onto the 
BBB. The problem I am now facing is compiling my own overlay, based on the 
NH7C for 24-bit color. When I run the *dtc *command, I always seem to get 
the error: Syntax error 5.1-9. FATAL ERROR.

I know I'm missing something, but haven't come across a solution yet. 

Note: I am doing this offline. I simply want to compile my own overlay, 
copy it into /lib/firmware and add the appropriate line within the 
/boot/uEnv.txt.

Any commands to fix this issue would be highly appreciated!

On Thursday, October 10, 2019 at 5:48:58 PM UTC-4, Ralph Stormer wrote:
>
> Robert,
>
> I would like to do this offline. What would I run after I copy it to 
> ./src/arm/? Also, which parts of the code do I need keep to avoid any 
> errors? The way I see it, my code would look something like this:
>
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
> #include 
>
> / {
>
> /*
> * Helper to show loaded overlays under: /proc/device-tree/chosen/overlays/
> */
> fragment@0 {
> target-path="/";
> __overlay__ {
>
> chosen {
> overlays {
> BB-BONE-NH7C-01-A0 = __TIMESTAMP__;
> };
> };
> };
> };
>
> /*
> * Free up the pins used by the cape from the pinmux helpers.
> */
> fragment@1 {
> target = <>;
> __overlay__ {
> P8_45_pinmux { status = "disabled"; }; /* lcd: lcd_data0 */
> P8_46_pinmux { status = "disabled"; }; /* lcd: lcd_data1 */
> P8_43_pinmux { status = "disabled"; }; /* lcd: lcd_data2 */
> P8_44_pinmux { status = "disabled"; }; /* lcd: lcd_data3 */
> P8_41_pinmux { status = "disabled"; }; /* lcd: lcd_data4 */
> P8_42_pinmux { status = "disabled"; }; /* lcd: lcd_data5 */
> P8_39_pinmux { status = "disabled"; }; /* lcd: lcd_data6 */
> P8_40_pinmux { status = "disabled"; }; /* lcd: lcd_data7 */
> P8_37_pinmux { status = "disabled"; }; /* lcd: lcd_data8 */
> P8_38_pinmux { status = "disabled"; }; /* lcd: lcd_data9 */
> P8_36_pinmux { status = "disabled"; }; /* lcd: lcd_data10 */
> P8_34_pinmux { status = "disabled"; }; /* lcd: lcd_data11 */
> P8_35_pinmux { status = "disabled"; }; /* lcd: lcd_data12 */
> P8_33_pinmux { status = "disabled"; }; /* lcd: lcd_data13 */
> P8_31_pinmux { status = "disabled"; }; /* lcd: lcd_data14 */
> P8_32_pinmux { status = "disabled"; }; /* lcd: lcd_data15 */
>
> P8_15_pinmux { status = "disabled"; }; /* gpmc_ad15.lcd_data16 */
> P8_16_pinmux { status = "disabled"; }; /* gpmc_ad14.lcd_data17 */
> P8_11_pinmux { status = "disabled"; }; /* gpmc_ad13.lcd_data18 */
> P8_12_pinmux { status = "disabled"; }; /* gpmc_ad12.lcd_data19 */
> P8_17_pinmux { status = "disabled"; }; /* gpmc_ad11.lcd_data20 */
> P8_14_pinmux { status = "disabled"; }; /* gpmc_ad10.lcd_data21 */
> P8_13_pinmux { status = "disabled"; }; /* gpmc_ad9.lcd_data22 */
> P8_19_pinmux { status = "disabled"; }; /* gpmc_ad8.lcd_data23 */
>
> P8_27_pinmux { status = "disabled"; }; /* lcd: lcd_vsync */
> P8_29_pinmux { status = "disabled"; }; /* lcd: lcd_hsync */
> P8_28_pinmux { status = "disabled"; }; /* lcd: lcd_pclk */
> P8_30_pinmux { status = "disabled"; }; /* lcd: lcd_ac_bias_en */
>
> P8_18_pinmux { status = "disabled"; }; /* lcd: enable */
>
> P9_14_pinmux { status = "disabled"; }; /* pwm: ehrpwm1a */
>
> P9_27_pinmux { status = "disabled"; }; /* ft5336: gpio3_15 */
> };
> };
>
>
> bb_lcd_lcd_pins: pinmux_bb_lcd_lcd_pins {
> pinctrl-single,pins = <
> /*LCD enable */
> BONE_P8_18 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpmc_clk_mux0.gpio2_1 */
>
> BONE_P8_45 (PIN_OUTPUT | MUX_MODE0) /* P8_45: lcd_data0.lcd_data0 */
> BONE_P8_46 (PIN_OUTPUT | MUX_MODE0) /* P8_46: lcd_data1.lcd_data1 */
> BONE_P8_43 (PIN_OUTPUT | MUX_MODE0) /* P8_43: lcd_data2.lcd_data2 */
> BONE_P8_44 (PIN_OUTPUT | MUX_MODE0) /* P8_44: lcd_data3.lcd_data3 */
> BONE_P8_41 (PIN_OUTPUT | MUX_MODE0) /* P8_41: lcd_data4.lcd_data4 */
> BONE_P8_42 (PIN_OUTPUT | MUX_MODE0) /* P8_42: lcd_data5.lcd_data5 */
> BONE_P8_39 (PIN_OUTPUT | MUX_MODE0) /* P8_39: lcd_data6.lcd_data6 */
> BONE_P8_40 (PIN_OUTPUT | MUX_MODE0) /* P8_40: lcd_data7.lcd_data7 */
> BONE_P8_37 (PIN_OUTPUT | MUX_MODE0) /* P8_37: lcd_data8.lcd_data8 */
> BONE_P8_38 (PIN_OUTPUT | MUX_MODE0) /* P8_38: lcd_data9.lcd_data9 */
> BONE_P8_36 (PIN_OUTPUT | MUX_MODE0) /* P8_36: lcd_data10.lcd_data10 */
> BONE_P8_34 (PIN_OUTPUT | MUX_MODE0) /* P8_34: lcd_data11.lcd_data11 */
> BONE_P8_35 (PIN_OUTPUT | MUX_MODE0) /* P8_35: lcd_data12.lcd_data12 */
> BONE_P8_33 (PIN_OUTPUT | MUX_MODE0) /* P8_33: lcd_data13.lcd_data13 */
> BONE_P8_31 (PIN_OUTPUT | MUX_MODE0) /* P8_31: lcd_data14.lcd_data14 */
> BONE_P8_32 (PIN_OUTPUT | MUX_MODE0) /* P8_32: lcd_data15.lcd_data15 */
>
> BONE_P8_15 (PIN_OUTPUT | MUX_MODE1) /* P8_15: gpmc_ad15.lcd_data16 */
> BONE_P8_16 (PIN_OUTPUT | MUX_MODE1) /* P8_16: gpmc_ad14.lcd_data17 */
> BONE_P8_11 (PIN_OUTPUT | MUX_MODE1) /* P8_11: gpmc_ad13.lcd_data18 */
> BONE_P8_12 (PIN_OUTPUT | MUX_MODE1) /* P8_12: gpmc_ad12.lcd_data19 */
> BONE_P8_17 (PIN_OUTPUT | MUX_MODE1) /* P8_17: gpmc_ad11.lcd_data20 */
> BONE_P8_14 (PIN_OUTPUT | MUX_MODE1)

Re: [beagleboard] BBONE-AI - Operating Temp Min & Max

2019-10-11 Thread William Hermans

I've just got my AI sitting in front of a 20" box fan(on low) I have
running 24/7 anyhow

debian@beaglebone:~$ uptime
 15:13:17 up 12 days,  9:30,  3 users,  load average: 0.23, 0.15, 0.10
debian@beaglebone:~$ cat /sys/class/thermal/thermal_zone*/temp
53400
53800
54600
53000
53800
Anyway, not sure what all the talk is about. It states plain as day on the
beaglebone.org "product" page that the board is prone to run hot . . .
.

On Thu, Oct 10, 2019 at 5:48 AM jonnymo  wrote:

> Thanks for the update.
>
> Yeah, I seen that Cape in a Jason vid and will be grabbing one when
> available.  There is someone on the element14 forums creating their own Fan
> cape as well.
>
> Cheers,
>
> Jon
>
> On Thu, Oct 10, 2019 at 3:17 PM Robert Nelson 
> wrote:
>
>> On Thu, Oct 10, 2019 at 10:11 AM jonnymo  wrote:
>> >
>> > Robert,
>> >
>> > Interesting.  There has been a ton of discussion regarding the heating
>> issue with the BB AI on the Element14 forums, however, in the end, the
>> BeagleBoard forum seems to be the location that is referenced for the final
>> say and info regarding this.  If Avent build the board, then they should
>> provide this information.   Thanks for the clarification.
>>
>> So Jason's been working on cpu setting:
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/commits/v4.14.x-ti
>>
>> Usually when users ask for the "Operating Temp Min & Max" values,
>> someone has to go dig thru all the components used on the board.. That
>> hasn't been done..
>>
>> > I've added the X-15 fan kit to my BB AI as is stated in the SRM and it
>> seems to stay around 40C during normal use.
>>
>> That one will work, it's noisy, i'm using a desk fan.. There is a 'fan
>> cape' coming..
>>
>> 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/CAG99bkrX%2BvTSonQJzArj12hCKdy_UEHth%3DySvKAD07FZ31WE6Q%40mail.gmail.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/CALHSORr1okfwqrCwjHozV_YKnFf9ixpsO6UsR4DuVcGhjzRWVw%40mail.gmail.com.

[beagleboard] Linux beaglebone 4.14.108-ti-r108, PWM mapping and write errors

Re: [beagleboard] BeagleBone Black Pin Mode Configuration?

Re: [beagleboard] BBONE-AI - Operating Temp Min & Max

3 matches

Site Navigation

Mail list logo

Footer information