|
|
Post by jj0 on Nov 23, 2020 16:16:11 GMT
Maybe I'm clutching at straws, but I'm wondering whether this might simply be a timing issue that could be fixed with a few pauses in the script. I can reliably get my PC to recognise my C64 Maxi as an Onda Tablet, and I can reliably run the boot.sh script without (apparently) producing any errors. It's just the next stage that doesn't work. On the one occasion that I was able to gain command line access, it was rock solid for several hours. So I doubt whether it's a power issue, at least for me. It could be, but it works for me ~9 out of every 10 times. When it doesn't work I can see on my UART connection (which btw are really useful and quite cheap and no soldering is required, did I mention this already? ;-)) that the kernel hangs for unknown reasons. But where would you want to see pauses in the script? |
|
|
|
Post by grasshopper on Nov 23, 2020 17:14:03 GMT
I don't know. As I said, I'm clutching at straws.
I've just had a look at the script again and notice that there are already a few sleep commands in it, although they don't run for very long.
Another possibility might be to remove the code that loads the nand module, and sets up the mass storage over USB. That code could then be put in a separate script that could be run by the user if required. That would eliminate the possibility of a clash between the virtual serial port and the mass storage over USB.
I might have a go myself once I've worked out how to repack the image.
|
|
|
|
Post by jj0 on Nov 23, 2020 20:28:33 GMT
I don't know. As I said, I'm clutching at straws. I've just had a look at the script again and notice that there are already a few sleep commands in it, although they don't run for very long. Another possibility might be to remove the code that loads the nand module, and sets up the mass storage over USB. That code could then be put in a separate script that could be run by the user if required. That would eliminate the possibility of a clash between the virtual serial port and the mass storage over USB. I might have a go myself once I've worked out how to repack the image. I still think it's the kernel crashing before even unpacking the initrd ramdisk init, but the more experimentation the better. I might use the recently released v10 to boot a kernel from USB instead of uploading it, or even put the rootfs on USB instead of using an initrd. To repack the initrd ramdisk from the directory where you unpacked it - I assume it's a subdirectory from the directory where you unpacked the nanda image, and where the zImage and bootimg.cfg are. find . | cpio -H newc -ov --owner root:root | gzip -9 ../initrd-mod.imgTo pack a new android nanda image first edit the bootimg.cfg and remove the 'bootsize' line. Then: cd ..
abootimg --create nanda-grasshopper -f bootimg.cfg -k zImage -r initrd-mod.imgAnd then... happy FEL testing ;-) |
|
|
|
Post by grasshopper on Nov 23, 2020 22:37:58 GMT
Thanks. You've actually preempted a question I had. I've been writing two scripts to automatically extract and insert the ramdisk files. The insert script was giving me an error message about the ramdisk being too big for the boot image. So I've now amended that script so that it deletes the 'bootsize' line. Both scripts now appear to be working, but are still a bit rough around the edges (see attached). |
|
|
|
Post by antjols1973 on Nov 24, 2020 13:48:55 GMT
I've taken instructions but unfortunately i'm still not able to boot into FEL mode using windows or linux I think I may have to bite the bullet and go the UART route. Would be good if someone could make a video to show the process and what exactly happens on windows once FEL mode has been activated...a little deflated but certainly not defeated...YET!!
|
|
|
|
Post by antjols1973 on Nov 24, 2020 14:06:22 GMT
In an ideal world it would be handy to be able to boot a firmware update on start up...
|
|
|
|
Post by jj0 on Nov 24, 2020 14:11:53 GMT
I've taken instructions but unfortunately i'm still not able to boot into FEL mode using windows or linux I think I may have to bite the bullet and go the UART route. Would be good if someone could make a video to show the process and what exactly happens on windows once FEL mode has been activated...a little deflated but certainly not defeated...YET!! Nothing much happens on Windows other than the drives appearing and the serial port appearing as per  Same in Linux of course. Did you try the v10 already, and did you see anything on the TV screen? |
|
|
|
Post by spannernick on Nov 24, 2020 14:30:13 GMT
Glad jj0 your using One Drive for the download, if you sync it with your Win10 VM then all you do is drop a new version in that folder and then delete the old one and One Drive will upload it for you..  Thats why the shear link is to the folder not the file, so I can update PCU and still use the same link. |
|
|
|
Post by antjols1973 on Nov 24, 2020 15:04:55 GMT
Hey Nick, unless im missing something v.10 was downloading as v.9 for me this morning...Im guessing you guys live in the UK, Im in OZ so we're in completely different timezones thus the staggered communication...little disheartened as i keep getting the same results...perhaps my img is completely destroyed as to the reason why its just not being read in FEL mode...I fail to understand what i am doing wrong...I've cracked and hacked many a system over the years from the nintendo Ds to the playstation classic but my one true passion the c64 seems way beyond my expertise...Iwish it was as easy as changing the power pack or replacing the VIC II chip like it was back in the good old days...
|
|
|
|
Post by antjols1973 on Nov 24, 2020 15:12:14 GMT
Again its a shame we dont have something as sophisticated as the Hakchi software for the nes/snes mini...If the PC communicates with the Maxi in the same way as it does those consoles surely its possible to do something similarly. I think you guys are amazing the support on this forum has been immense, and the development strides you have made so far have been great...keep up the good work!
|
|
|
|
Post by antjols1973 on Nov 24, 2020 15:15:08 GMT
BTW still showing as v.9 in one drive...
|
|
|
|
Post by jj0 on Nov 24, 2020 15:53:06 GMT
Again its a shame we dont have something as sophisticated as the Hakchi software for the nes/snes mini...If the PC communicates with the Maxi in the same way as it does those consoles surely its possible to do something similarly. I think you guys are amazing the support on this forum has been immense, and the development strides you have made so far have been great...keep up the good work! It's a shame it doesn't work for you - I don't understand why. Getting an UART would help in troubleshooting though you would not actually need the OTG mode to backup/restore your nand. Hakchi uses the same sunxi-fel protocol as sunxi-fel.exe does, so I'm not sure the results would differ. I still think it's something to do with the kernel crashing. But even if it would work straight away, my programming skills are not good enough to create a GUI user interface around it. And there's not as many people interested in the Mini/Maxi/VIC-20 as in the NES/SNES Mini unfortunately. I fixed the link to V10 now  . Oh, btw you guessed wrong, I don't live in the UK |
|
|
|
Post by grasshopper on Nov 24, 2020 17:22:05 GMT
Unfortunately, I'm also running out of ideas.
jj0, can you tell me where you got the rescue image from? Is it something you built yourself?
Thanks
|
|
|
|
Post by jj0 on Nov 24, 2020 19:07:24 GMT
Unfortunately, I'm also running out of ideas. jj0, can you tell me where you got the rescue image from? Is it something you built yourself? Thanks nanda-C64Maxi-Rescue-v8 is the normal nanda (=kernel + initial ramdisk) but with the ramdisk contents modified, for example the boot script (/init) changed to do the OTG stuff, + various commands added. It is actually a modified version of the ramdisk I created for the Mini FEL mode, with Maxi-specific things like the nand driver added. |
|
|
|
Post by spannernick on Nov 24, 2020 21:46:43 GMT
Unfortunately, I'm also running out of ideas. jj0, can you tell me where you got the rescue image from? Is it something you built yourself? Thanks Can you connect a UART..? you might be able to fix it if you add one and be able to diagnose what's wrong with it better, it might just be your game folder thats messed up. When you turn it on does the RGL THEC64 logo come up or is it just a black screen..? (If you have copied c64emu-pcu.rgl from PCU(to use joystick Swap) to the firmware and updated it to v1.4.2 and copied c64emu-pcu.rgl back to the firmware, it don't work with the new version of the carousel so will stop the carousel from loading up, you need to copy back thec64emu.rgl for v1.4.2 to the firmware to get the carousel working again.) |
|
|
|
Post by antjols1973 on Nov 25, 2020 2:07:57 GMT
haha I sit corrected JJ assumed you were in the UK...shame we're not next door as I'm sure you'd be able to fix my issue in a second ;P. Thanks for fixing the link to v.10 I'll give it another go tonight...have a great day/evening guys wherever you are in the world!
|
|
|
|
Post by jj0 on Nov 25, 2020 10:14:37 GMT
haha I sit corrected JJ assumed you were in the UK...shame we're not next door as I'm sure you'd be able to fix my issue in a second ;P. Thanks for fixing the link to v.10 I'll give it another go tonight...have a great day/evening guys wherever you are in the world! Well you can always send the PCB to me (in the Netherlands) and I can try to fix it but that may not be as satisfying as repairing it yourself ;-) |
|
|
|
Post by antjols1973 on Nov 25, 2020 11:05:18 GMT
Haha yes, it may have to come to that in the end  I tried v.10 little more details on the MAXI screen just hangs unfortunately starting the Kernal, certainly not being greeted with the neon flashing lights, which is a bummer. I bit the bullet this morning and have ordered a UART serial should be here in a week or so...fingers crossed it will bring me more joy! |
|
|
|
Post by spannernick on Nov 25, 2020 11:35:41 GMT
I live in the UK... |
|
|
|
Post by antjols1973 on Nov 25, 2020 11:42:21 GMT
I'm originally from North London Nick but been in Perth for well over 20Years now i suppose that makes me an aussie now!
|
|
|
|
Post by spannernick on Nov 25, 2020 11:46:10 GMT
|
|
|
|
Post by jj0 on Nov 25, 2020 12:13:25 GMT
And don't forget about the rubber band method if -like me- you abhor soldering. Just search the forum for rubber band and you will find it. |
|
|
|
Post by antjols1973 on Nov 25, 2020 12:21:37 GMT
No way Nick, I grew up in Edmonton, been a Spurs supporter all my life, doing alright this year...definitely using the rubberband method when the time comes...
|
|
|
|
Post by grasshopper on Nov 25, 2020 12:39:18 GMT
Unfortunately, I'm also running out of ideas. jj0, can you tell me where you got the rescue image from? Is it something you built yourself? Thanks nanda-C64Maxi-Rescue-v8 is the normal nanda (=kernel + initial ramdisk) but with the ramdisk contents modified, for example the boot script (/init) changed to do the OTG stuff, + various commands added. It is actually a modified version of the ramdisk I created for the Mini FEL mode, with Maxi-specific things like the nand driver added. Ah, OK. I presume the uboot image is not the stock one? Maybe that's the cause of the problem.
Hopefully when (if?) the source code arrives, it will be possible to build a new uboot image.
If you're using a modified stock nanda image, can you clarify why it's not possible to mount USB flash drives?
Thanks
|
|
|
|
Post by grasshopper on Nov 25, 2020 12:44:46 GMT
Unfortunately, I'm also running out of ideas. jj0, can you tell me where you got the rescue image from? Is it something you built yourself? Thanks Can you connect a UART..? you might be able to fix it if you add one and be able to diagnose what's wrong with it better, it might just be your game folder thats messed up. When you turn it on does the RGL THEC64 logo come up or is it just a black screen..? (If you have copied c64emu-pcu.rgl from PCU(to use joystick Swap) to the firmware and updated it to v1.4.2 and copied c64emu-pcu.rgl back to the firmware, it don't work with the new version of the carousel so will stop the carousel from loading up, you need to copy back thec64emu.rgl for v1.4.2 to the firmware to get the carousel working again.)
Hi Nick,
There's nothing actually wrong with my C64 Maxi. The reason why I want to get FEL mode working is so that I can backup and restore the stock firmware from/to bare metal. If I don't have that ability, then there's the danger I might do something stupid and brick my device.
|
|
|
|
Post by jj0 on Nov 25, 2020 12:46:15 GMT
nanda-C64Maxi-Rescue-v8 is the normal nanda (=kernel + initial ramdisk) but with the ramdisk contents modified, for example the boot script (/init) changed to do the OTG stuff, + various commands added. It is actually a modified version of the ramdisk I created for the Mini FEL mode, with Maxi-specific things like the nand driver added. Ah, OK. I presume the uboot image is not the stock one? Maybe that's the cause of the problem.
Hopefully when (if?) the source code arrives, it will be possible to build a new uboot image. U-boot is not stock, which may contribute to the issue. I've been thinking of using the stock one, haven't gotten around to it yet. Regarding the u-boot source code, don't hild your breath, for the Mini they crippled it (wrong nand driver) and it wouldn't build. Do you have a nanda backup that you could send me, maybe if I use your Maxi's kernel it makes a difference. Assuming it is different of course... |
|
|
|
Post by grasshopper on Nov 25, 2020 12:55:47 GMT
Ah, OK. I presume the uboot image is not the stock one? Maybe that's the cause of the problem.
Hopefully when (if?) the source code arrives, it will be possible to build a new uboot image. U-boot is not stock, which may contribute to the issue. I've been thinking of using the stock one, haven't gotten around to it yet. Regarding the u-boot source code, don't hild your breath, for the Mini they crippled it (wrong nand driver) and it wouldn't build. Do you have a nanda backup that you could send me, maybe if I use your Maxi's kernel it makes a difference. Assuming it is different of course...
That was quick! I was just editing my previous post when you replied. I was also going to ask you why it's not possible to mount USB flash drives given that you're using the stock image?
Also, I didn't realise you could gain access to the stock u-boot image. I thought it was located on a partition of the nand chip not covered by nanda and nandb.
With regards to the nand driver, is it actually necessary to rebuild it, given that you already have the pre-built binary as a separate module?
|
|
|
|
Post by jj0 on Nov 25, 2020 14:00:44 GMT
U-boot is not stock, which may contribute to the issue. I've been thinking of using the stock one, haven't gotten around to it yet. Regarding the u-boot source code, don't hild your breath, for the Mini they crippled it (wrong nand driver) and it wouldn't build. Do you have a nanda backup that you could send me, maybe if I use your Maxi's kernel it makes a difference. Assuming it is different of course...
That was quick! I was just editing my previous post when you replied. I was also going to ask you why it's not possible to mount USB flash drives given that you're using the stock image?
Also, I didn't realise you could gain access to the stock u-boot image. I thought it was located on a partition of the nand chip not covered by nanda and nandb.
With regards to the nand driver, is it actually necessary to rebuild it, given that you already have the pre-built binary as a separate module?
You can recover stock uboot from memory but then of course it's already loaded and might not work if run again. I have not booted it yet. The USB on the stock kernel via FEL fails probably due to the failure to reserve CMA memory and the subsequent dma failures etc. The nand driver module is for the kernel, so that is still usable but uboot has its own nand driver built-in. However in theory that is not needed if you want to boot a kernel from FEL. Unfortunately (so far) the nand driver module does not work with kernels from various Allwinner SDK's I have tried. That's why it would be nice to have the source or at least the kernel .config to match the kernels properties. So lots of avenues to explore... |
|
|
|
Post by grasshopper on Nov 25, 2020 14:32:47 GMT
I wonder whether the source code for the Capcom Home Arcade joystick has been released. It appears to use a board that is almost identical to the one in the C64 Maxi. So maybe that's the way forward.
As a bonus, it would potentially give us the means to play Capcom games on the C64 Maxi.
|
|
|
|
Post by grasshopper on Nov 25, 2020 14:45:14 GMT
|
|
Thats why the shear link is to the folder not the file, so I can update PCU and still use the same link.
. 
I tried v.10 little more details on the MAXI screen just hangs unfortunately starting the Kernal, certainly not being greeted with the neon flashing lights, which is a bummer. I bit the bullet this morning and have ordered a UART serial should be here in a week or so...fingers crossed it will bring me more joy! 
