BCM2835 support?

[courageon]

Is there support for the BCM2835 based io? I've got a PI-B revision (one of the first) and I'm getting the "This module can only be run on a Raspberry Pi!" exception when I try to import the module.
running "cat /proc/cpuinfo" gives these hardware specs for my Pi (if that is helpful):
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 697.95
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7

Hardware : BCM2835
Revision : 0002
Serial : 0000000024e08e00

When looking through the source for this project I noticed hard-coded values for the broadcom module "BCM2708". Are there forks for the 2835?

Thanks!

[courageon]

Forked it, got it working...
https://github.com/courageon/RPIO

[metachris]

This repository is open for someone else to take over maintenance. Interested?

[DEvil0000]

I said it once again. I would like to do this and spend some time - this said I may not be the guy having time to have a close look within a week.I also have just a limited set of PIs: old 1 rev (0x3), new 1 revisions , b+, zero, 3 Von meinem Samsung Gerät gesendet.

…

-------- Ursprüngliche Nachricht -------- Von: Chris Hager <[email protected]> Datum: 26.02.2018 13:09 (GMT+01:00) An: metachris/RPIO <[email protected]> Cc: Subscribed <[email protected]> Betreff: Re: [metachris/RPIO] BCM2835 support? (#104) This repository is open for someone else to take over maintenance. Interested? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/metachris/RPIO","title":"metachris/RPIO","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/metachris/RPIO"}},"updates":{"snippets":[{"icon":"PERSON","message":"@metachris in #104: This repository is open for someone else to take over maintenance. Interested?"}],"action":{"name":"View Issue","url":"#104 (comment)"}}}

[courageon]

I'd be down for taking some ownership. Like @DEvil0000 though, I too have a limited set of PIs, just some first gen Bs and a PI 3. But I really like the idea behind this library, super clever trick for getting an awesome PWM out of the PI.

[metachris]

👍

what do you think would be good next steps for improving this repo? i'm open to adding new people as maintainers and move the RPIO pypi project to a common space.

[courageon]

Well, tbh I think trying to create a "common" base with https://github.com/xinkaiwang/rpio-pwm would be useful (since that's how I got this one working again, at least on my PI). Consolidate the low level code and branch for the python and node versions. I can reach out and ask if that's something @xinkaiwang would like to do. Keeping in mind some of that code was also borrowed from other repos, so that spider-webs very quickly.

Past that I think just testing would be the next big steps, but I think that's more on the community since this is an open sourced effort. I've been looking for an excuse to get another PI3, so I can definitely take on some testing with that one :)

[Yackou]

Sorry for pitching in late, but have you looked at @JamesGKent repo or mine, and at pull request #100 ?

It seems several people have been looking at RPIO and ended up fixing the same board and kernel support issues over and over, so committing those fixes would definitely be helpful. As I said some months earlier, I don't think I'd be up for maintaining the repo all by myself, but I'd certainly be willing to participate and help move things forward.

[DEvil0000]

I did not have a close look at forks till now.

I think there are some steps needed next:

1. adding 2-5 guys to do get this back running
2. get low level code nice, clean and shiny
3. merge the improvements and fixes starging with the issues most people face
4. maybe split python wrapping to a second repo

I think its not too much work to get it mostly straight again. As soon as some people are on board we should have a quick discussion or meeting to figure out details.

[JamesGKent]

i think the biggest thing to start with would be merging some fixes for the newer cpus. but ultimately i think we need to implement the following:

• interpret serial number according to rpi foundation guidance to determine base address for peripherals
• implement checking to ensure dma channel being used is not being used by other processes

and nice to haves:

• in the event that a board is not supported directly we could add functions to specify the base address/any other addresses manually
• simple pwm functions to control a pin pulsing at a certain frequency and duty cycle (start/stop/set duty/set freq etc)

[DEvil0000]

@metachris so how do you want to proceed on this?

[DEvil0000]

I think last time I was reading the code was at about 0.7.X
I was never a fan of the python coupling and build process. Somehow its nice but in some ways its coupled to close and to pythonish.
However I think you @metachris should point out whats the official difference between master and v2 branch and why there is a v2 branch. Also when you should use the v2 branch - or just eliminate the need of the v2 branch and merge back to master.
Beside this you should merge compatibility from PR #82 (better the JamesGKent v2 branch) or others (maybe ealier ones) doing the same thing. (Or pick the best and merge the rest)
I would like to help and invest some of my time but you did not give me access till now and I do not want to see the work ending up in another PR which is never getting merged.

[DEvil0000]

@metachris you asked now the third time for help/someone to take over but everytime you ignore all replies. Here are some people willing to help out so why do you ignore it/them and ask again one year later?
Thats quite annoying...