Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Sinovoip's Banana Pi M1+ #337

Closed
malkusch opened this issue Apr 24, 2017 · 2 comments
Closed

Support Sinovoip's Banana Pi M1+ #337

malkusch opened this issue Apr 24, 2017 · 2 comments
Assignees
Labels

Comments

@malkusch
Copy link

@malkusch malkusch commented Apr 24, 2017

The statically linked Banana Pro wiringpi library doesn't work with Banana Pi M1+. This is no surprise as the BPI-M1+ uses a different pin numbering. However it took me some time to understand that and also to find a solution. So I like to abuse this issue mainly for documentation:

Until pi4j supports a further platform which is linked against BPI-WiringPi you can still use Pi4j with the Banana Pi M1+.

@savageautomate
Copy link
Member

@savageautomate savageautomate commented Aug 7, 2017

@malkusch,

UPDATE
I have just added experimental support for the Sinovoip BPI series "BananaPi" variants.

COMMIT: 92f0658

This is included in the the latest 1.2-SNAPSHOT build now.

Please note that I do not have any of these devices so I'm not able to really test it.
I have included a new "bpi" platform that you have to choose when starting your program.

        // ####################################################################
        //
        // since we are not using the default Raspberry Pi platform, we should
        // explicitly assign the platform as the Sinovoip BPI platform.
        //
        // ####################################################################
        PlatformManager.setPlatform(Platform.BPI);

STATUS:

Feel free to start testing it and report back any issue .. or better yet submit pull requests with fixes.

Thanks, Robert

@savageautomate savageautomate self-assigned this Sep 5, 2017
@savageautomate
Copy link
Member

@savageautomate savageautomate commented Jan 15, 2021

Closed.

As of Pi4J v2.x, board/platform expansion will provided via pluggable modules and support for specific platforms beyond the RPI is outside of the scope of the Pi4J project. We had to make this change because supporting and testing 'N' number of board variants became impossible for a small volunteer team to keep up with. Moving forward, Pi4J will provide the core framework and infrastructure and if someone wants to create drivers for alternate platforms/boards, they will be able to do that and maintain it separately from the Pi4J codebase.

Pi4J v2 also does not mandate/assume an implementation like WiringPi.

See: https://v2.pi4j.com/documentation/architecture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.