|
|
Post by jj0 on Nov 25, 2020 16:00:15 GMT
The board is similar but the CHA used a modern mainline kernel and uses eMMC instead of the old-fashioned nand. So there's no driver for the Maxi's nand. But you can download one of the official images that should be available in the CapcomHomeArcade Reddit forum. Then you have to figure out how to run it on the Maxi, e.g. using my FEL uboot to run it from USB. Or solder on a mini SD-card slot maybe. Or convince the CHA binary to run on the Maxi's kernel. And then you will find out that the Maxi's 256MB of RAM don't make for a nice experience. But the other way around works quite well, running the Maxi's kernel and rootfs and Carousel on the CHA. |
|
|
|
Post by grasshopper on Nov 25, 2020 16:58:02 GMT
Well the CHA source code appears to includes config files and drivers for a wide range of boards. So I was hoping it might include files for the C64 Maxi board as it is part of the same family as the board used in the CHA device. But I don't know enough to really know what to look for.
Soldering on a mini SD card slot would be ideal. Unfortunately, unlike the CHA board, there doesn't appear to be an obvious place to solder on the socket.
|
|
|
|
Post by antjols1973 on Nov 26, 2020 10:37:54 GMT
I think potentially my issues stem from the lack of serial COM port connectivity my PC doesn't install the usbsys driver automatically like it should and I'm not able to find this driver online anywhere does anyone have an AIO com/lpt driver set for windows 10?
|
|
|
|
Post by jj0 on Nov 26, 2020 10:47:58 GMT
Well the CHA source code appears to includes config files and drivers for a wide range of boards. So I was hoping it might include files for the C64 Maxi board as it is part of the same family as the board used in the CHA device. But I don't know enough to really know what to look for. Soldering on a mini SD card slot would be ideal. Unfortunately, unlike the CHA board, there doesn't appear to be an obvious place to solder on the socket. Just in case you want to try an CHA image, some guy named @spannernick has collected a lot of them here. |
|
|
|
Post by jj0 on Nov 26, 2020 10:51:39 GMT
I think potentially my issues stem from the lack of serial COM port connectivity my PC doesn't install the usbsys driver automatically like it should and I'm not able to find this driver online anywhere does anyone have an AIO com/lpt driver set for windows 10? This USB CDC driver should work. |
|
|
|
Post by antjols1973 on Nov 26, 2020 11:49:45 GMT
Hi JJ I did check this link for a driver a few days a go but it states that if it doesn't install automatically then you need to contact the device manufacturer, I don't know if I'm missing something but I can't find a link to the driver on this page...
|
|
|
|
Post by spannernick on Nov 26, 2020 12:42:13 GMT
Well the CHA source code appears to includes config files and drivers for a wide range of boards. So I was hoping it might include files for the C64 Maxi board as it is part of the same family as the board used in the CHA device. But I don't know enough to really know what to look for. Soldering on a mini SD card slot would be ideal. Unfortunately, unlike the CHA board, there doesn't appear to be an obvious place to solder on the socket. Just in case you want to try an CHA image, some guy named @spannernick has collected a lot of them here. That's me..  I have 1000 GB on One Drive so thought it was a good idea, I was collecting files for CHA anyway and backing them up to One Drive... It's very rare someone else is call Spannernick, well I have never seen anyone with my name, maybe Spanner thats why I added my real name after it.. I called myself Spannernick on here cause I am called that on the Lemon 64 forums, so users would know I am the same person. |
|
|
|
Post by grasshopper on Nov 26, 2020 17:20:22 GMT
I've just had a go with version 10 of the rescue package. I'm now getting some debugging output on my monitor. It gets to a point where it says "Starting Kernel ..." and then crashes.
I've tried using a powered hub but that hasn't made any difference.
I also decided to have a go at building a new bootloader, but I'm not having much luck with that either. I've been following the instructions here: linux-sunxi.org/Retrieving_device_information#Using_FELwhen I type "sudo./sunxi-fel version" I get the following output: AWUSBFEX soc=00001680(H3) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000 That looks promising. However, when I type "sudo ./sunxi-fel read 0x42400000 0x82d0 boot1.header" I get the following output: usb_bulk_send() ERROR -7: Operation timed out
If I then type "sudo./sunxi-fel version" for a second time, I now get the following output:
usb_bulk_send() ERROR -7: Operation timed out
|
|
|
|
Post by jj0 on Nov 26, 2020 20:22:52 GMT
I've just had a go with version 10 of the rescue package. I'm now getting some debugging output on my monitor. It gets to a point where it says "Starting Kernel ..." and then crashes.
I've tried using a powered hub but that hasn't made any difference.
I also decided to have a go at building a new bootloader, but I'm not having much luck with that either. I've been following the instructions here: linux-sunxi.org/Retrieving_device_information#Using_FELwhen I type "sudo./sunxi-fel version" I get the following output: AWUSBFEX soc=00001680(H3) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000 That looks promising. However, when I type "sudo ./sunxi-fel read 0x42400000 0x82d0 boot1.header" I get the following output: usb_bulk_send() ERROR -7: Operation timed out
If I then type "sudo./sunxi-fel version" for a second time, I now get the following output:
usb_bulk_send() ERROR -7: Operation timed out
You are not initialising the system, a.o. not enabling the MMU so there is no memory mapped to 0x40000000 and above, only from 0 (?) onwards. If you look at my just now released an totally revamped v11 - which thanks to you reminding me now uses an almost stock 2011.09 u-boot - you'll see in the boot.sh that the Maxi needs to be initialised before you can use it: sunxi-fel -v -p spl ../boot/sunxi-spl.binThe sunxi-spl.bin is part of what u-boot builds in this case I took it from a 2020 version. But I hope the v11 finally works for you consistently now. |
|
|
|
Post by jj0 on Nov 26, 2020 20:36:21 GMT
Hi JJ I did check this link for a driver a few days a go but it states that if it doesn't install automatically then you need to contact the device manufacturer, I don't know if I'm missing something but I can't find a link to the driver on this page... Strange - on my newly installed Windows 10 I don't need to install a driver. Do you see it in the Device Manger and can you then have WIndows search for a driver? Otherwise you can try to find it by googling on 'windows 10 android CDC driver'? Or use the Ubuntu Live USB drive with the latest and greatest 'Once more onto the breach' v11. And remember (just in case) to get into FEL mode: - Start with an unpowered Maxi - Press and keep pressing the FEL-mode button - or remove the Maxi's red led form it's connector and connect it to the port/socket above (or below depending on your orientation) the FEL button (on the other side of the SBC). That way you are sure the FEL mode is being 'pressed' - Power on the Maxi by connecting the USB A to USB A cable to your laptop - Then run the script and if you think it is required connect power to the micro-usb socket |
|
|
|
Post by antjols1973 on Nov 27, 2020 3:08:19 GMT
I will try again with the latest and greatest v.11, I do have the usbser.sys file so not sure why its not opening the virtual serial port...hopefully will work tonight, if not the UART is on its way!!
|
|
|
|
Post by antjols1973 on Nov 27, 2020 10:45:40 GMT
Reading differently now but the Kernel still doesn't start up....Details below...
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -l
USB device 002:004 Allwinner H3 02c00081:15e04620:78970024:184506d3
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p spl ..\boot\sunxi-spl.bin
Stack pointers: sp_irq=0x00002000, sp=0x00005E08
MMU is not enabled by BROM
Generating the new MMU translation table at 0x00008000
=> Executing the SPL... done.
Setting write-combine mapping for DRAM.
Setting cached mapping for BROM.
Writing back the MMU translation table.
Enabling I-cache, MMU and branch prediction... done.
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p write 0x4a000000 ..\boot\u-boot-nanopi-mod-3.bin write 0x40007800 ..\boot\nanda-C64Maxi-Rescue-v11 write 0x43000000 ..\boot\script-maxi-full.bin
100% [================================================] 869 kB, 551.4 kB/s
100% [================================================] 15624 kB, 591.2 kB/s
100% [================================================] 49 kB, 440.5 kB/s
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p exec 0x4a000000
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>boot.cmd
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -l
usb_bulk_send() ERROR -7: Operation timed out
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p spl ..\boot\sunxi-spl.bin
usb_bulk_send() ERROR -7: Operation timed out
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p write 0x4a000000 ..\boot\u-boot-nanopi-mod-3.bin write 0x40007800 ..\boot\nanda-C64Maxi-Rescue-v11 write 0x43000000 ..\boot\script-maxi-full.bin
usb_bulk_send() ERROR -7: Operation timed out
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>sunxi-fel.exe -v -p exec 0x4a000000
usb_bulk_send() ERROR -7: Operation timed out
C:\Users\Home\Desktop\More C64Files\C64Maxi-VIC-20-FEL-rescue-boot-v11\windows>
|
|
|
|
Post by antjols1973 on Nov 27, 2020 15:21:58 GMT
Don't know if this helps at all but this is the information Device properties "Event" dialogue box, not sure what it all means but the device has not "migrated"
Device USB\VID_1F3A&PID_EFE8\5&6d49e1f&0&1 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_046D&PID_C219\5&6d49e1f&0&1
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(1)
Migration Rank: 0xF000FFFFFFFF0023
Present: false
Status: 0xC0000719
|
|
|
|
Post by spannernick on Nov 27, 2020 16:08:27 GMT
Don't know if this helps at all but this is the information Device properties "Event" dialogue box, not sure what it all means but the device has not "migrated" Device USB\VID_1F3A&PID_EFE8\5&6d49e1f&0&1 was not migrated due to partial or ambiguous match. Last Device Instance Id: USB\VID_046D&PID_C219\5&6d49e1f&0&1 Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da} Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(1) Migration Rank: 0xF000FFFFFFFF0023 Present: false Status: 0xC0000719 This not working would do my head in, jj0 needs a eureka moment I think.. it will come, keep trying and you never know one might work eventually. Its not working for me too but mine is THEC64 Maxi DIY(THEC64 Maxi PI, I don't like calling it that, it makes it sound like I am using a RPI in it, when I am not so THEC64 Maxi DIY sounds better and thats what it is, its a Do It Yourself THEC64 Maxi.. ) but still one of them might work with it, its just finding the right way for it to work and keep going... You will get it jj0 but I think is because some THEC64 Maxi's nanda is different so jj0 nanda will only work with his nandb from his THEC64 Maxi will not work will yours, he needs your nanda or find a maxi from the same run(built at the same time as each other), maybe this is were the label on the bottom of THEC64 Maxi will came in handy, what your number on it and if you can find a maxi with the next number below or above yours then that nanda might work from it, its finding the right nanda, I came up with is ideas by accident, when I made a imagefor my THEC64 Maxi DIY of THE VIC 20 firmware and found out that the nanda from THEC64 Maxi don't work with THE VIC 20 Firmware(nandb) So what's your number on the label under THEC64 Max and what your number jj0 and let see how far apart they are. |
|
|
|
Post by antjols1973 on Nov 27, 2020 16:17:39 GMT
Sounds like an incredibly long shot!! the serial # 00024695 for what good it will do...Will the UART make any difference?
|
|
|
|
Post by spannernick on Nov 27, 2020 16:26:18 GMT
Sounds like an incredibly long shot!! the serial # 00024695 for what good it will do...Will the UART make any difference? Yeah you be able to see better and it will give your THEC64 Maxi more power, I use my uart with my THEC64 Maxi DIY all the time now, and you can copy and paste the code from the screen in it and not have to type it in(that takes so long).. I still think its the nanda that don't work with your nandb. RGL did make different models of the THEC64 Mini even the EU one so they might of change the nanda in different runs of THEC64 Maxi, your number is big so its a newer version of THEC64 Maxi probably newer then jj0 THEC64 Maxi, the smaller the number the older THEC64 Maxi is. I think I am getting confused but can you boot your THEC64 Maxi and does The Carousel work..? looking in this thread it sounds like you can... thec64community.online/thread/703/restoring-original-firmwareIf so that means you could us PCUAE to get into THEC64-X Windows Mod and copy your nanda. I think as well if you install a official update from RGL on THEC64 Mini/Maxi/THE VIC/VC20 and you have changed the games in the firmware and the music then the update installs wrong(cause it don't have enough space to install the update cause of the games and wav file you have put on it) and makes the machine have a black screen and The Carousel stops functioning so the machine becomes as good as a "BRICK". ***WARRING TO ALL USERS***
PLEASE DO NOT USE THEC64 MAXI GAME TOOL TO FLASH GAMES IN TO ITS FIRMWARE, USE PCUAE INSTEAD NOW(its in my sig below), if you do you will never be able to update it until you put everything back to how the firmware was before. |
|
|
|
Post by antjols1973 on Nov 27, 2020 16:42:49 GMT
I think you're right nick, there is a definite conflict somewhere a long the line, RGL for all their good certainly did a number on us would be hackers that's for sure....Have a good day mate time for me to sleep!!
|
|
|
|
Post by spannernick on Nov 27, 2020 16:46:31 GMT
I think you're right nick, there is a definite conflict somewhere a long the line, RGL for all their good certainly did a number on us would be hackers that's for sure....Have a good day mate time for me to sleep!! OK Night, Night... don't let the bed bugs bite.. lol... |
|
|
|
Post by grasshopper on Nov 27, 2020 17:06:32 GMT
I had a go with version 11 of the rescue package and failed to get it working.
I've also just ordered a USB 2.0 A-Male to USB 2.0 A-Male connector to see if that helps. The cable I'm using is USB 3.0. I know it shouldn't matter but who knows.
jj0, can you tell me what sort of USB Hub you're using?
Thanks.
|
|
|
|
Post by jj0 on Nov 27, 2020 19:18:59 GMT
My Maxi is serial# is 00008170. My most setup is like this (HDMI is usually not connected):  So the USB 3 hub (I can't find the brand anymore) is connected directly to my laptop USB 3 port, and powers the Maxi and the serial2usb connector that's inside the Maxi. I think I can now reproduce the issue. As I have a serial2usb connected to the UART I usually go into FEL mode by holding 2 pressed in the terminal window and then powering on. However I now tried it with using the actual FEL button and surprise surprise my Maxi hangs too. I've also tried with first switching the Maxi on to the state that it waits for the power button, then keep the FEL button pressed and then also click the power button. This also gets the Maxi into FEL mode but it still hangs. So at least I now have something to go on. Feel free to vent some frustration about this towards me... |
|
|
|
Post by antjols1973 on Nov 28, 2020 0:11:10 GMT
Wow JJ I just assumed you were using the same method the you outlined to me to throw into FEL mode,hopefully now you know that it doesn't work using this method could be a game changer thanks again for all your hard work...
|
|
|
|
Post by antjols1973 on Nov 28, 2020 0:17:22 GMT
Hey Nick, thats effectively what I have at the moment... A BRICK... Im not able to boot into carousel mode, just get a black screen when turning on, I can use the reset function on it choose language, tv output but can't boot into either the carousel nor the classic mode just get a black screen with either option....
|
|
|
|
Post by spannernick on Nov 28, 2020 1:52:26 GMT
Hey Nick, thats effectively what I have at the moment... A BRICK... Im not able to boot into carousel mode, just get a black screen when turning on, I can use the reset function on it choose language, tv output but can't boot into either the carousel nor the classic mode just get a black screen with either option.... That sounds familiar, that was happening to me if I copied thec64emu.rgl over from PCU and then updated it, cause you can't use c64emu-pcu.rgl with v1.4.2 cause it don't work with it, they have added new stuff to the c64 emulator and carousel like the play and rewind buttons. Do you see the logo..? if you can bring up the display settings then the carousel is not working, so the file system is OK and Linux is working in the background so the file system is not damaged, its a file in there that stopping the carousel loading up, you will be able to get into it with the Uart connected to it and it will ask for log in, it could be c64emu.rgl stopping it loading, the user name is "root" and password is "chuckpeddle" It should say when you click on putty and then press return on the PC keyboard...
RedQuark
redquarktwo login:
Just use the user name "root" and password "chuckpeddle" to log in. |
|
|
|
Post by spannernick on Nov 28, 2020 13:27:06 GMT
Hey Nick, thats effectively what I have at the moment... A BRICK... Im not able to boot into carousel mode, just get a black screen when turning on, I can use the reset function on it choose language, tv output but can't boot into either the carousel nor the classic mode just get a black screen with either option.... If once you get a Uart, I can give you the commands to load PCUAE from putty to boot PCUAE then it will put Autoboot in the firmware then when you turn off and on again it will bypass the firmware and boot PCUAE only..? If Linux is working that all PCUAE needs to work, I be given you a way of starting the start.sh file that the fake update runs to boot PCUAE, PCUAE just need to be on a USB Stick plugged into it. PCUAE v1.20 will included The Carousel v1.4.2. I will test it on Putty and try and get PCUAE to run from command line for you.. |
|
|
|
Post by antjols1973 on Nov 28, 2020 14:08:30 GMT
That's brilliant Nick you're a good man just need that UART now and I can resurrect thins thing!
|
|
|
|
Post by jj0 on Nov 28, 2020 15:00:24 GMT
That's brilliant Nick you're a good man just need that UART now and I can resurrect thins thing! released, it works for me with FEL-mode via the hardware button. I hope it works for you and grasshopper and @spannernick (and anyone who wants to try) as well. |
|
|
|
Post by spannernick on Nov 28, 2020 16:24:23 GMT
That's brilliant Nick you're a good man just need that UART now and I can resurrect thins thing! Once you have booted up THEC64 Maxi and logged in... user: root password: chuckpeddle
RedQuark
redquarktwo login: root
Password:
login[161]: root login on 'ttyS0'
#
then plug your USB Stick with PCUAE in to one of the USB ports at the right side of the Machine, you should get...
[ 8430.090361] usb 3-1.4: new high-speed USB device number 5 using sunxi-ehci
[ 8430.268985] scsi1 : usb-storage 3-1.4:1.0
[ 8431.280463] scsi 1:0:0:0: Direct-Access Generic- USB3.0 CRW -SD 1.00 PQ: 0 ANSI: 4
[ 8431.972811] scsi 1:0:0:1: Direct-Access Generic- USB3.0 CRW -SD 1.00 PQ: 0 ANSI: 4
[ 8431.981523] sd 1:0:0:0: [sda] 7626752 512-byte logical blocks: (3.90 GB/3.63 GiB)
[ 8431.982630] sd 1:0:0:0: [sda] Write Protect is off
[ 8431.982643] sd 1:0:0:0: [sda] Mode Sense: 2f 00 00 00
[ 8431.983508] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 8432.000436] sda: sda1
[ 8432.023895] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 8432.047687] sd 1:0:0:1: [sdb] Attached SCSI removable disk
Then type:
# mount /dev/sda1 /mnt
or
mount /tmp/usbdrive/sda1
both work, then type:
# cd /mnt
# ./start.sh &
and PUCAE will boot up...
# --> Please Wait...
--> Mounting Loop Device
Start of sda1 partition: 1048576
loop device: /dev/loop0
Loading PCUAE... Please Wait...
Autoboot is checking if its in the firmware...
-->Yes, Autoboot is in the firmware already, all OK
killall: the64: no process killed
Volume Manager by pod
Keys are for volume up and down..
CTRL + theC64 key + F1 for Volume Up
CTRL + theC64 key + F3 for Volume Down
mount: mounting /tmp/pcu/Carousel_Games/Options/emulators/c64emu-pcu.rgl on /usr/lib/c64emu.rgl failed: No such file or directory
--> Mounting Controllers/Joystick Gamecontrollerdb Text File
killall: carousel-gamelist-selector.sh: no process killed
sh: -e: unknown operand
sh: -e: unknown operand
sh: x: unknown operand
sh: -e: unknown operand
sh: -e: unknown operand
sh: -e: unknown operand
sh: -e: unknown operand
Starting Carousel Gamelist Selector
|
|
|
|
Post by spannernick on Nov 28, 2020 17:57:52 GMT
That's brilliant Nick you're a good man just need that UART now and I can resurrect thins thing! released, it works for me with FEL-mode via the hardware button. I hope it works for you and grasshopper and @spannernick (and anyone who wants to try) as well. YES... FINALLY ... I knew you would do it...
Command Shell on /dev/ttyGS0
/ #
NAND ID: 0x00 0x00 0x00 0x00 0x00 - using /lib/modules/3.4.39/nand-Maxi-1.4.2.ko
Mass Storage over USB enabled for:
/dev/nanda (Type: Android Boot Image)
and
/dev/nandb (Type: Linux ext4 filesystem)
Command Shell over virtual serial port enabled.
Use your favourite disk image program to backup and/or restore nanda and/or nandb.
Once finished ensure you safely eject both Mass Storage devices from your PC before powering off TheC64 Maxi/THE VIC 20
|
|
|
|
Post by antjols1973 on Nov 29, 2020 7:02:07 GMT
Brilliant work JJ, you are an absolute genius!! I am now able to boot in FEL mode and the 2 usb drives are announced. I'm having a little bit of difficulty now locating suitable disc image software and an ext4 reader to view my files...I've been trying to using AOMEI Backupper to back up the disks but keep getting a back-up driver error, again frustrating to say the least and no doubt unrelated to your brilliant work but again a little help would be awesome...
|
|
|
|
Post by antjols1973 on Nov 29, 2020 7:44:53 GMT
So I'm able to access the folder structure on Nandb since installing the Ext2Fsd DRIVER, just wondering if it's normal the /usr/share/the64/games/ FOLDER is completely empty?
|
|
I have 1000 GB on One Drive so thought it was a good idea, I was collecting files for CHA anyway and backing them up to One Drive... 
