bone101 | Presentation web server written in bonescript

by jadonk JavaScript Version: 2.0.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | bone101 Summary

bone101 is a JavaScript library typically used in Internet of Things (IoT), Docker, Raspberry Pi applications. bone101 has no bugs, it has no vulnerabilities and it has low support. However bone101 has a Non-SPDX License. You can download it from GitHub.

Getting started information for [BeagleBone and BeagleBone Black] written in [BoneScript] The content here is presented by the default web server running with the demonstration Linux distributions provided on BeagleBone and BeagleBone Black. It is written in HTML and makes use of the BoneScript server running on the board and BoneScript JavaScript library running in these HTML pages.

Support

Quality

Security

License

Reuse

Support

bone101 has a low active ecosystem.

It has 47 star(s) with 78 fork(s). There are 16 watchers for this library.

It had no major release in the last 6 months.

There are 12 open issues and 5 have been closed. On average issues are closed in 257 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of bone101 is 2.0.1

Quality

bone101 has 0 bugs and 0 code smells.

Security

bone101 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

bone101 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

bone101 has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

bone101 releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bone101

Get all kandi verified functions for this library.

bone101 Key Features

No Key Features are available at this moment for bone101.

bone101 Examples and Code Snippets

No Code Snippets are available at this moment for bone101.

Community Discussions

Trending Discussions on bone101

PWM chip to pin mapping on BeagleBone Black (v4.14)

Why am I getting segmentation fault on Beaglebone Black when accessing GPIO2 and GPIO3 through kernel module?

QUESTION

PWM chip to pin mapping on BeagleBone Black (v4.14)

Asked 2019-Jan-18 at 01:03

There is very little information how to configure the Beaglebone for PWM on newer versions of the kernel. I followed the instructions from PWM on BeagleBone Black (v4.14) to interface with the PWM chips, but now I need to figure out the pin that each chip is connected to.

Based on the Cape Expansion Headers image in the BeagleBone Black documentation, I know:

EHRPWM0A = P9_22
EHRPWM0B = P9_21
EHRPWM1A = P9_14
EHRPWM1B = P9_16
EHRPWM2A = P8_19
EHRPWM2B = P8_13
ECAP0 = P9_42

When I run ls -lh /sys/class/pwm to see the available PWM interfaces I see:

...

ANSWER

Answered 2018-May-06 at 20:41

Page 184 of the TI AM335x and AMIC110 Sitara Processors Technical Reference Manual gives the memory map for the PWM chips:

PWM Subsystem 0: 0x48300000

eCAP0: 0x48300100

ePWM0: 0x48300200

PWM Subsystem 1: 0x48302000

eCAP1: 0x48302100

ePWM1: 0x48302200

PWM Subsystem 2: 0x48304000

eCAP2: 0x48304100

ePWM2: 0x48304180

The address of each PWM interface (posted in the question) contains the hardware address. Matching these addresses gives us:

EHRPWM0 (ePWM0) is pwmchip1
EHRPWM1 (ePWM1) is pwmchip3
EHRPWM2 (ePWM2) is pwmchip6
ECAP0 (eCAP0) is pwmchip0

Each EHRPWM chip has two PWM output channels, thus the A and B variants. They are exported by echoing a 0 or 1 to export. These channels must use the same frequency, but can have a different duty cycle.

Therefore, given this interface configuration, EHRPWM0A and EHRPWM0B are located at:

Source https://stackoverflow.com/questions/50204329

QUESTION

Why am I getting segmentation fault on Beaglebone Black when accessing GPIO2 and GPIO3 through kernel module?

Asked 2018-Jan-04 at 02:58

I have been attempting to get access to GPIO2 and GPIO3 on the beaglebone black through kernel module with no success. Every time I attempt to assign an output value to GPIOs 2 and 3 I get a segmentation fault.

The exact same code (with the appropriate pin assignment) works for GPIO0 and GPIO1.

I have attempted various pins on both P8 and P9 related to GPIO2 and GPIO3 with no success. On the flip side, the same exact code works for GPIO0 and GPIO1 with appropriate pin assignment.

For pin values I am using the official BBB manual. For appropriate I/O GPIO availability I am checking this diagram from beagleboard.com:

...

ANSWER

Answered 2018-Jan-01 at 21:45

The answer as to why your code is getting a segmentation fault is actually irrelevant, because, as a kernel module, it is misguided, needs to be tossed, and you need to rewrite it. Your module has absolutely no business trying to gain direct access to the "GPIO (control) registers", which are already owned by the pin-control (pinctrl) subsystem.

GPIO pins are a (generic) resource that the kernel manages. Would you write a driver that just starts using an arbitrary block of memory for its buffers?
Hopefully no, because memory is (another) resource managed by the kernel.
But your module is just wantonly using GPIO pins at its own whim!

Refer to the proper GPIO document for the exact Linux kernel version that you are using: Documentation/gpio.txt for version 3.8.13.

The available routines that your module can use include:

Source https://stackoverflow.com/questions/48045436

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install bone101

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: