You are confusing the HAL driver with the Linux driver.

The entries in /sys/class/uio are created by the Linux driver which is
configured via device-tree.

The "loadrt" command loads the HAL driver which uses the uio device
nodes to talk to the PRU.

If you do not have any entries in /sys/class/uio, you have a problem
with either the kernel or device-tree.  You might closely monitor the
boot sequence with a serial console and make sure you're really using
the expected u-boot settings, kernel, and u-boot overlays.

NOTES:
* You can verify the live device-tree settings by walking /proc/device-tree

* You might want to make sure the boot loader installed to your eMMC
flash is current.  Older versions can cause problems with the new boot
loader scripts.  If you need to update, just use any current "flasher"
image (it doesn't really matter which one).

On 9/5/2018 10:43 PM, mugginsac wrote:
> Now I am more confused than ever. I have a working config for Xylotex.ini 
> and I can't even get it to run. (I don't even know how I ever got it to 
> run.)
> The test for /sys/class/uio/uio0 is in setup.sh (in the files for both 
> Xylotex and CRAMPS). It is before it even runs
> the config_pin command.
> The command
> loadusr -w ./setup.sh (This blows out because /sys/class/uio/uio0 is empty.
> is the first command in the CRAMPS.hal file.
> This is quite a bit before the command
> loadrt [PRUCONF](DRIVER) prucode=$(HAL_RTMOD_DIR)/[PRUCONF](PRUBIN) 
> [PRUCONF](CONFIG) halname=hpg
> 
> So how is the the pru driver supposed to ever get loaded and thus populate 
> /sys/class/uio/uio0????
> 


-- 
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