[   32.277374]
do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600
[   32.286272] epc = 00401d51 in fast-gpio[400000+3000]
[   32.291364] ra  = 00401a89 in fast-gpio[400000+3000]
[   32.296408]
Segmentation fault

Is this a broken device? It's literally brand new, and isn't working!

Ω-ware: 0.1.7 b139

I'll have a google around as to how to roll back the firmware then!

Cheers.

In CLI do:

cd /tmp
wget http://repo.onion.io/omega2/images/omega2p-v0.1.6-b137.bin
sysupgrade omega2p-v0.1.6-b137.bin

Wait for the LED to turn off, then restart your Omega2p and wait several minutes while the LED blinks.

Many thanks for your help. You've saved me from pulling my hair out!

I'm also new on here. Is there a rep / thanks system on this forum?

on the lower right corner you have the quote link on the side of this you can ppls request up or downwote, see smal arrows. ... and you change the reputation of a person this way.

Thanks for the rollback tips @WereCatf - I may hang tight and wait for a firmware update to fix it.

On the plus side, I have a built and tested toolchain now! But of course the fast-gpio I compiled from source didn't work either.

1. Needs to be built specifically for the Omega2 processor which is different from the Omega1
2. The memory mapped GPIO registers are accessed as 32 bit values - the endian-ness of the Omega2 processor is different from the Omega1 and will need to be taken care of to check that it is appropriate in each case
3. Being a different processor, the memory mapping of the GPIO registers may well be different on the Omega2 and Omega1 and will need to be taken care of to check that it is appropriate in each case

Since I have some C/C++ code of my own for doing things similar to fast-gpio I will be looking at these issues in more detail when I have time

I haven't had time to look at things closely

I was just surmising about possible issues since I have some similar C/C++ code that I will need to review for the Omega2

Though I don't know how you can say:

Fast-gpio works just fine
if there are issues with KERNEL_DEVMEM not enabled - though I would concede that this is more a system issue rather than with fast-gpio
Though it does raise questions of how much actual testing has been done on the software released for the Omega2

• /dev/mem doesn't exist in the newer images and it's obviously needed in order to be able to access the GPIO-registers
• I have tested fast-gpio and it works fine in the images with /dev/mem
• I have looked at the source-code for fast-gpio

If you don't believe me, you're entirely free to check things yourself.

a link to the forum instead would be ok.

If it doesn't get lost in the numerous postings, it's a good idea ... for example a PINNED POST.

However, changelog files and man pages often list known issues, so I don't see anything wrong with a mention in the doc files, especially if it's the first place users should refer to first. Afterward, they get transferred from KNOWN ISSUES to TROUBLESHOOTING.

However, changelog files and man pages often list known issues,

If they are permanent that's ok. But a missing sd-card drivers for example don't have to be mentioned, because the drivers will be added and the error is gone ... why confuse ppl about something like this who not exists anymore (in near future)?!

If you have solutions for their problems post them on git-hub as pull request. If you really want you can also try to make your "Known issues" and propose as pull request. But don't for get to do the maintenance for this section. You will see it is a lot of work/time you will miss for other tasks

</end_of_discussion>
<start_doing_it>
Thats how opensource community works!
</start_doing_it>```

A known issues page and changelog is in the works!

Update: the firmware changelog and known issues listing is up! See the docs site: https://docs.onion.io/omega2-docs/firmware-reference.html

Will try to carve out time this week to look into this /dev/mem issue.

Thanks

Thanks