do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600

[Chris Stratton]

@Jo-Kritzinger said in do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600:

@Chris-Stratton Thanks for clearing that up Chris. Where is the devmem tool?

It's usually provided as part of busybox, if it is present in the build I'd expect it to be in the path by default, it may well be in /sbin or another usual location for binaries. If it is provided by busybox then the devmem file entry will probably just be a simlink to the busybox executable and busybox devemem ..... may also work.

[Jo Kritzinger]

@Chris-Stratton I did a find / -name devmem which resulted in zero hits. I don't know (yet - new to linux world) how to make a custom build and that's why I asked @Lazar-Demin to include it in the build. I'd be grateful if you could guide me how to add it myself.

[WereCatf]

@Jo-Kritzinger Basically, you need someone to provide you with the LEDE SDK or you need to compile LEDE yourself in order to be able to configure custom settings for busybox and to compile it with them. Or, you can hope for the Onion-devs to include devmem in their images and just grab the version I compiled at https://dl.dropboxusercontent.com/u/11811685/omega2-stuff/devmem as a temporary solution.

[Jo Kritzinger]

@WereCatf So a wget into /tmp folder and a opkg install? I'll give it a go, thank you.

[WereCatf]

@Jo-Kritzinger It's not even an opkg-package, it's just a raw executable. Give it executable permissions with chmod u+x devmem and run it with ./devmem

[Jo Kritzinger]

@WereCatf Thank you @WereCatf

[Chris Stratton]

@WereCatf said in do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600:

@Jo-Kritzinger It's not even an opkg-package, it's just a raw executable. Give it executable permissions with chmod u+x devmem and run it with ./devmem

Is that actually a fully busybox common executable? It certainly seems to contain strings that would make sense in other tools like ping, but still probably a quick pragmatic solution.

[WereCatf]

@Chris-Stratton Yes, it's just busybox. Jo wanted devmem and this was the easiest and quickest way.

[luz]

@Lazar-Demin said here:

We're getting a better handle on the remaining shipments and the customer support backlog so we'll be spending more time actually making the Omega better in March. We hear what you guys are saying in terms of the community working the make the firmware better, so we will be open sourcing the firmware sometime in March as well

Great to hear that!

Don't forget to have a look at the githup PR's

Thank you all for your continued patience and support for a young company

I sympathize with your situation, It's always difficult to choose between urgent and important when there's too much to do.
I just think keeping the enthusiasm in the community for doing things with the Omega2 going is important. So making sure those that are willing to invest a lot of time are not blocked standing before closed source doors for too long is also important.

[Jo Kritzinger]

@luz With you on this one.