strud
Creatures
Posts: 18
|
Post by strud on Jul 14, 2020 12:27:00 GMT
what version is the c64 Maxi on (v1.3.2), it works fine on TheC64 Maxi PI so it uses the same firmware..? My Maxi is running 1.3.2 but PCU 1.14a does not work. The same USB stick with same 1.14a files does work on my Mini.
I even have a second Maxi new-in-box so I tested with that one too. Firstly with its original firmware (1.3.0) then with updated (1.3.2).
Using the 2-button method with PCU 1.14a did not work on that Maxi either.
|
|
|
|
Post by megabit on Jul 14, 2020 14:03:49 GMT
The same for me, I have been trying since yesterday from version 1.13 to 1.14a on my MAXI and the two-button method does not work, neither for the carousel change, nor for XWM.
Obviously I also tried on an 8GB pen drive just formatted in FAT32, copying all the contents of the Zip file without changes and it doesn't work!
|
|
|
|
Post by spannernick on Jul 14, 2020 18:55:16 GMT
For the people that this does not work, are you using THEC64 Joystick or another joystick or controller..? I am trying to find out why its not working, when it works for me ok..?
The hard thing is I don't have a theC64 maxi to test it with, I have theC64 Maxi PI but should work if it works on theC64 Mini.
|
|
|
|
Post by babblebubble on Jul 14, 2020 19:46:33 GMT
For the people that this does not work, are you using THEC64 Joystick or another joystick or controller..? I am trying to find out why its not working, when it works for me ok..? The hard thing is I don't have a theC64 maxi to test it with, I have theC64 Maxi PI but show work if it works on theC64 Mini. Look at my Video: Only the original Maxi Joystick and my 16 GB USB-Stick was plugged in.
The two fire button method for XWM does not work. The menu button + fire 1 button for changing of the carousel does not work. Changing the carousel via the fake firmware update does not work, but this is expected with the a-version.
I wonder why you develop this project for a PI and then expect it to run on an original TheC64 Maxi. As is well known, the Maxi does not have a standard PI board, so I would suggest that you buy an unchanged TheC64 Maxi for this.
|
|
|
|
Post by frankybyte on Jul 14, 2020 19:49:40 GMT
unfortunately it definitely does not work with the MAXI
|
|
|
|
Post by jj0 on Jul 14, 2020 20:59:14 GMT
For the people that this does not work, are you using THEC64 Joystick or another joystick or controller..? I am trying to find out why its not working, when it works for me ok..? The hard thing is I don't have a theC64 maxi to test it with, I have theC64 Maxi PI but show work if it works on theC64 Mini.
The two fire button method for XWM does not work. The menu button + fire 1 button for changing of the carousel does not work. Changing the carousel via the fake firmware update does not work, but this is expected with the a-version.
I wonder why you develop this project for a PI and then expect it to run on an original TheC64 Maxi. As is well known, the Maxi does not have a standard PI board, so I would suggest that you buy an unchanged TheC64 Maxi for this.
Its not Raspberry Pi but an Orange Pi which is essentially the same hardware as a Maxi, running the Maxi firmware. So that is not an issue. For me the menu + fire 1 does work on the Maxi. To understand why it is not happening on your Maxi it would be nice if you could do a test, assuming you have UART access to the Maxi. With the PCU v1.14a running can you try the following commands via the UART? I'm showing them together with the results I have on my Maxi: # ls -l /dev/input/
total 0
crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 02:13 event1
crw-rw---- 1 root root 13, 66 Jan 1 02:13 event2
crw-rw---- 1 root root 13, 0 Jan 1 02:13 js0
crw-rw---- 1 root root 13, 1 Jan 1 02:13 js1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 mice
# /mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
CTRL-C
#
Or if not via the UART then via the normal X-Windows Mod. The script checks for buttons pressed via /dev/input/event1 and /dev/input/event2 but maybe it is different on your Maxi. This could be if other input devices are attached but from the video I think you only have the joystick attached? Thanks. |
|
|
|
Post by megabit on Jul 14, 2020 22:41:41 GMT
For the people that this does not work, are you using THEC64 Joystick or another joystick or controller..? I am trying to find out why its not working, when it works for me ok..? The hard thing is I don't have a theC64 maxi to test it with, I have theC64 Maxi PI but should work if it works on theC64 Mini. I confirm that I use the standard joystick of the MAXI and I have no other peripherals connected to the USB ports except the 8GB pen drive, of course! The carousel change with fake firmware works perfectly but the script of the two buttons does not. |
|
|
|
Post by babblebubble on Jul 14, 2020 22:54:01 GMT
Its not Raspberry Pi but an Orange Pi which is essentially the same hardware as a Maxi, running the Maxi firmware. So that is not an issue. For me the menu + fire 1 does work on the Maxi. To understand why it is not happening on your Maxi it would be nice if you could do a test, assuming you have UART access to the Maxi. With the PCU v1.14a running can you try the following commands via the UART? I'm showing them together with the results I have on my Maxi: # ls -l /dev/input/
total 0
crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 02:13 event1
crw-rw---- 1 root root 13, 66 Jan 1 02:13 event2
crw-rw---- 1 root root 13, 0 Jan 1 02:13 js0
crw-rw---- 1 root root 13, 1 Jan 1 02:13 js1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 mice
# /mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
CTRL-C
#
Or if not via the UART then via the normal X-Windows Mod. The script checks for buttons pressed via /dev/input/event1 and /dev/input/event2 but maybe it is different on your Maxi. This could be if other input devices are attached but from the video I think you only have the joystick attached? Thanks. Please give me detailed instructions. I managed to boot with X-Windows Mod.
I am not familiar with Linux, so I need detailed instructions.
I took photos from the screen.  As you can see, there is no input folder in the dev folder.
 All folders are empty, except the bin folder. In this photo you can see which files are in the folder. Here is the file "ls" as in your list "# ls -l / dev / input /". Since I do not want to destroy my TheC64 by executing a command, I ask you for the instructions which command I should execute! So from the beginning, from root@redquarktwo:/# As I wrote before, I only connected my USB stick and the normal maxi joystick, nothing else. |
|
|
|
Post by spannernick on Jul 15, 2020 0:03:31 GMT
Its not Raspberry Pi but an Orange Pi which is essentially the same hardware as a Maxi, running the Maxi firmware. So that is not an issue. For me the menu + fire 1 does work on the Maxi. To understand why it is not happening on your Maxi it would be nice if you could do a test, assuming you have UART access to the Maxi. With the PCU v1.14a running can you try the following commands via the UART? I'm showing them together with the results I have on my Maxi: # ls -l /dev/input/
total 0
crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 02:13 event1
crw-rw---- 1 root root 13, 66 Jan 1 02:13 event2
crw-rw---- 1 root root 13, 0 Jan 1 02:13 js0
crw-rw---- 1 root root 13, 1 Jan 1 02:13 js1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 mice
# /mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
CTRL-C
#
Or if not via the UART then via the normal X-Windows Mod. The script checks for buttons pressed via /dev/input/event1 and /dev/input/event2 but maybe it is different on your Maxi. This could be if other input devices are attached but from the video I think you only have the joystick attached? Thanks. Please give me detailed instructions. I managed to boot with X-Windows Mod.
I am not familiar with Linux, so I need detailed instructions.
I took photos from the screen. As you can see, there is no input folder in the dev folder.
All folders are empty, except the bin folder. In this photo you can see which files are in the folder. Here is the file "ls" as in your list "# ls -l / dev / input /". Since I do not want to destroy my TheC64 by executing a command, I ask you for the instructions which command I should execute! So from the beginning, from root@redquarktwo:/# As I wrote before, I only connected my USB stick and the normal maxi joystick, nothing else. Oh I think I see why it has no input folder or events, I couldn't get the joystick BTNs from THEC64 Maxi Pi, it couldn't find any inputs when I ran evtest so that maybe why its not working, I used theC64 Mini to scan for the buttons on the joystick with X-Windows Mod. |
|
|
|
Post by tng1701e on Jul 15, 2020 8:03:17 GMT
I am using the original joystick that came with the MAXI.
|
|
|
|
Post by spannernick on Jul 15, 2020 10:54:08 GMT
so the people that the 2 buttons don't work don't have /dev/input/ folder so don't have the files it needs to it knows what buttons are pressed.
crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 02:13 event1
crw-rw---- 1 root root 13, 66 Jan 1 02:13 event2
crw-rw---- 1 root root 13, 0 Jan 1 02:13 js0
crw-rw---- 1 root root 13, 1 Jan 1 02:13 js1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 mice
so you need them files for the buttons to work, I need to make some code to copy that folder the your firmware so it checks if you have the folder or not.
jj0 is that why, it is not working for them..?
if the input folder is there in jj0 thec64 maxi and not in others, that means RGL must of removed it.
My THEC64 Maxi PI is a copy of the first version that came out and it works so the firmware is missing files that why it don't work..
|
|
|
|
Post by jj0 on Jul 15, 2020 12:15:23 GMT
so the people that the 2 buttons don't work don't have /dev/input/ folder so don't have the files it needs to it knows what buttons are pressed. crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 02:13 event1
crw-rw---- 1 root root 13, 66 Jan 1 02:13 event2
crw-rw---- 1 root root 13, 0 Jan 1 02:13 js0
crw-rw---- 1 root root 13, 1 Jan 1 02:13 js1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 miceso you need them files for the buttons to work, I need to make some code to copy that folder the your firmware so it checks if you have the folder or not. jj0 is that why, it is not working for them..? if the input folder is there in jj0 thec64 maxi and not in others, that means RGL must of removed it. My THEC64 Maxi PI is a copy of the first version that came out and it works so the firmware is missing files that why it don't work.. No, you're jumping to conclusions.  . The fact that there are no /dev/input/event* entries in the X-Windows Mod is because the /dev/input directory is not properly linked to the original /dev/input directory on the Maxi rootfs. So it just means that (in the current version) of the X-Windows Mod you can't see the joysticks. frankybyte If you replace the start.sh of the X-Windows Mod with this start.sh (1.34 KB) and try again then ' ls-l /dev/input' should have some files and ' evtest' should give some useful information. |
|
|
|
Post by frankybyte on Jul 15, 2020 12:43:27 GMT
I have exchanged the start.sh, and then tried it on the Maxi. During the firmware update the C64 restarts and X-Windows Mod does not start. The maxi always restarts, in the Retro-Games Screen
I still have a USB stick with TheC64-X-Windows v2, it will start.
What do you need for information ?
|
|
|
|
Post by frankybyte on Jul 15, 2020 13:00:40 GMT
when I copy the rootfs.img into the main directory, xWindows
but only this, nothing else will work
in your start.sh
the path is not adjusted at all
# Image is mounted read-only to prevent corruption
mount -o ro /mnt/rootfs.img /tmp/chroot
|
|
|
|
Post by jj0 on Jul 15, 2020 13:10:37 GMT
when I copy the rootfs.img into the main directory, xWindows
but only this, nothing else will work
in your start.sh
the path is not adjusted at all
# Image is mounted read-only to prevent corruption
mount -o ro /mnt/rootfs.img /tmp/chroot
Are you changing the start.sh of PCU or for the original X-Windows Mod? It should be for the original X Windows Mod. |
|
|
|
Post by frankybyte on Jul 15, 2020 13:26:23 GMT
I wrote.
PCU
look at the attached picture above
|
|
|
|
Post by jj0 on Jul 15, 2020 13:31:12 GMT
I wrote. PCU look at the attached picture above I wrote that you need to change the start.sh on the original X-Windows Mod, so why are you changing it on PCU? |
|
|
|
Post by frankybyte on Jul 15, 2020 13:33:34 GMT
because I'm stupid  you told me to read properly I'll do it right now. |
|
|
|
Post by frankybyte on Jul 15, 2020 13:42:34 GMT
|
|
|
|
Post by ecstaticax on Jul 15, 2020 14:06:46 GMT
Hi, I copied the content of the latest archive. I run it, but then I only have a few games and when I try to load the other letters, it always load a few “A” named games. What may I have missed?
Regards
|
|
|
|
Post by jj0 on Jul 15, 2020 14:27:37 GMT
Thanks  So there are a lot of entries. Can you also run 'evtest'? That will show what each entry is for. |
|
|
|
Post by frankybyte on Jul 15, 2020 14:30:24 GMT
"evtest"  can you please explain to me exactly what it is you want me to do |
|
|
|
Post by spannernick on Jul 15, 2020 15:04:07 GMT
"evtest" can you please explain to me exactly what it is you want me to do Run evtest in x- windows mod in a terminal # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]: then pick a device number,one of thec64 Joysticks..? |
|
|
|
Post by frankybyte on Jul 15, 2020 15:36:03 GMT
|
|
|
|
Post by frankybyte on Jul 15, 2020 16:11:05 GMT
|
|
|
|
Post by jj0 on Jul 15, 2020 17:57:02 GMT
Ok, thanks. That explains things. The script looks for /dev/event1 and /dev/event2 as the joysticks. However: - Shame on me , I didn't have the keyboard attached to my Maxi and from your picture the keyboard is discovered before the joysticks so it gets assigned to /dev/event1 and /dev/event2
- You have a USB wireless receiver attached that gets /dev/event3
- And the joystick is given /dev/event5 which is never looked at by my script
So I just have to be a bit more clever in detecting the button presses. On the PCU USB sticvk Can you replace the "Carousel_Games\Games\Z_Other_Scripts\switch-games.sh" script with switch-games.sh (4.45 KB) This new version tries every /dev/event* unitl one of them has the buttons pressed. I tested this on my Mini and Maxi. spannernick if this works for frankybyte (and anyone else who wants to test) the please add it to PCU. I will then also send you an updated start.sh for PCU. |
|
|
|
Post by spannernick on Jul 15, 2020 17:59:43 GMT
Do you have 3 THEC64 joysticks..? event:1,2 and 5..? My C64 Maxi PI don't have the input folder too but the 2 button method works fine so what stopping it working on others THEC64 Maxi..? Can't it can find the right button on the Joystick, it has event1 and event2 that the buttons use. /mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_TRIGGER
JOY1_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_THUMB
JOY1_BT2=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_TRIGGER
JOY2_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_THUMB
JOY2_BT2=$?You can see theses are the fire buttons. So why is it not working for you... EDIT I see you have added a * to so its looking for any device attached like a wild card.. |
|
|
|
Post by frankybyte on Jul 15, 2020 18:07:23 GMT
which start.sh should I use ? 14, 14a ??
@ spannernick
couldn't this be better explained in your description on the first page?
14 = Maxi for
14a = Mini with 2 Botton Menu..
or how about 14,14a?
|
|
|
|
Post by jj0 on Jul 15, 2020 18:11:19 GMT
which start.sh should I use ? 14, 14a ?? Good question, I lose track.... I think 14a is the one where the 2-button switch is enabled. |
|
|
|
Post by jj0 on Jul 15, 2020 18:12:50 GMT
which start.sh should I use ? 14, 14a ??
@ spannernick
couldn't this be better explained in your description on the first page?
14 = Maxi for
14a = Mini with 2 Botton Menu..
or how about 14,14a?
Well if this works there is no reason for different versions for Maxi and Mini, only for 'with X-Windows Mod' and 'without X-Windows Mod' |
|
. The fact that there are no /dev/input/event* entries in the X-Windows Mod is because the /dev/input directory is not properly linked to the original /dev/input directory on the Maxi rootfs. So it just means that (in the current version) of the X-Windows Mod you can't see the joysticks.
