Thank you Charles,
I am running the CRAMPS board on a A5C rev of BBB. Hence, I have only 2gb emmc.
I now understand why Robert had me erase the emmc on my A6 board.
As soon as I erased the emmc boot area, the /sys/class/uio/ directory was
populated during boot.
So now I got farther in the boot process but not yet success.
P9_25 is specified in setup.sh. So any idea why this error?
MACHINEKIT - 0.1
Machine configuration directory is
'/home/machinekit/machinekit/configs/ARM.BeagleBone.CRAMPS'
Machine configuration file is 'CRAMPS.ini'
Starting Machinekit...
rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0
--rtmsglevel=5 --usrmsglevel=5 --halsize=524288
rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
io started
<commandline>:0: Component 'iocontrol' ready
<commandline>:0: Program 'io' started
halcmd loadusr io started
Waiting for /sys/class/uio/uio0 OK
P9_25 pinmux file not found!
bash: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state: No such file or
directory
Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state
CRAMPS.hal:11: program './setup.sh' failed, returned 1
Shutting down and cleaning up Machinekit...
<commandline>:0: Realtime threads stopped
Cleanup done
Machinekit terminated with an error. You can find more information in the log:
/home/machinekit/linuxcnc_debug.txt
and
/home/machinekit/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
CRAMPS setup.sh
https://pastebin.com/7rKzPpzT <https://pastebin.com/7rKzPpzT>
CRAMPS.ini
https://pastebin.com/PsPP0YRt <https://pastebin.com/PsPP0YRt>
CRAMPS.hal
https://pastebin.com/KRer1BDi <https://pastebin.com/KRer1BDi>
CRAMPS linuxcnc.log
https://pastebin.com/cCre8Z30 <https://pastebin.com/cCre8Z30>
CRAMPSdmesg.txt
https://pastebin.com/ThYsK3Jr <https://pastebin.com/ThYsK3Jr>
> On Sep 6, 2018, at 6:58 AM, Charles Steinkuehler <[email protected]>
> wrote:
>
> 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 a topic in the Google
> Groups "Machinekit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/machinekit/XSxIKD_mi-s/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
--
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.
