I haven't worked with the HPS GPIO pins on the DE0-Nano, just logic
implemented in the FPGA fabric.  But on the BeagleBone and other ARM
systems I have worked with, bus errors when accessing hardware
generally means that the hardware has not been enabled (taken out of
reset and assigned a clock).

The easiest way to "activate" the GPIO hardware is to export the GPIO
pin(s) you are trying to use:

https://www.kernel.org/doc/Documentation/gpio/sysfs.txt

...although you can also do this with kernel code, device tree
entries, a U-Boot script, etc.

On 7/7/2017 8:21 AM, Sebastian wrote:
> Ok thanks a lot, yes than is the question for us how to access the existing 
> GPIO 
> using the pre-built image we have burned. Do you know where we can get these 
> information?
> 
> Am Freitag, 7. Juli 2017 13:04:08 UTC+2 schrieb Schooner:
> 
>     If you want to know how to access the existing GPIO using the pre-built
>     image you have burned, that is a completely different question.
>     It is a matter of asking the right one.
> 
>     I have 2 machines using DE0-NANO + 7i76 boards providing multiple axes and
>     full GPIO from the 7i76,
>     and one XYZ milling machine just using the DE0-NANO to provide 3 axis
>     hardware stepping and encoder on one header
>     and using the GPIO bank through a breakout board on another.
> 
>     On 07/07/17 11:17, [email protected] <javascript:> wrote:
>>     The image is made with the FPGA programmed to emulate a Mesa 5i25 / 7i76 
>> -
>>     7i77 FPGA combo
>>
>>     If you want to experiment addressing GPIO in some other way, using
>>     another.rbf file, use one of the Altera images
>>
>>     On 07/07/17 10:02, Sebastian wrote:
>>>
>>>     Hello,
>>>
>>>
>>>     our task is to build a CNC milling machine with X,Y,Z-axis on the
>>>     DE0-NANO board form Altera with machinekit. We use this Image:
>>>     
>>> _http://deb.machinekit.io/uploads/de0-nano/debian-8.5-console-armhf-2017-02-14/_
>>>     
>>> <http://deb.machinekit.io/uploads/de0-nano/debian-8.5-console-armhf-2017-02-14/>.
>>>     Our main problem is that every time we try access to the GPIO's over a
>>>     C-program we get the same Error “Bus Error“.Our question is, is there a
>>>     Demon who don't let us access to the GPIO's or what kind of mistake we
>>>     made. On the fpga is a .rbf file that we have generate with Quartus 
>>> where
>>>     we can access to the GPIO's over PIO's. We have test that with a
>>>     C-Program on the from Altera provided Console Image:
>>>     http://www.terasic.com/downloads/cd-rom/de0-nano-soc/linux_BSP/
>>>     <http://www.terasic.com/downloads/cd-rom/de0-nano-soc/linux_BSP/>
>>>
>>>     -- 
>>>     website: http://www.machinekit.io blog: http://blog.machinekit.io 
>>> github:
>>>     https://github.com/machinekit
>>>     ---
>>>     You received this message because you are subscribed to the Google 
>>> Groups
>>>     "Machinekit" group.
>>>     To unsubscribe from this group and stop receiving emails from it, send 
>>> an
>>>     email to [email protected] <javascript:>.
>>>     Visit this group at https://groups.google.com/group/machinekit
>>>     <https://groups.google.com/group/machinekit>.
>>>     For more options, visit https://groups.google.com/d/optout
>>>     <https://groups.google.com/d/optout>.
>>
>>     -- 
>>     website: http://www.machinekit.io blog: http://blog.machinekit.io github:
>>     https://github.com/machinekit
>>     ---
>>     You received this message because you are subscribed to the Google Groups
>>     "Machinekit" group.
>>     To unsubscribe from this group and stop receiving emails from it, send an
>>     email to [email protected] <javascript:>.
>>     Visit this group at https://groups.google.com/group/machinekit
>>     <https://groups.google.com/group/machinekit>.
>>     For more options, visit https://groups.google.com/d/optout
>>     <https://groups.google.com/d/optout>.
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email 
> to [email protected] 
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
> 


-- 
Charles Steinkuehler
[email protected]

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to