|
|
Post by crispin on Oct 30, 2018 20:00:43 GMT
Sorry deerwings , I thought about modified one. my bad. |
|
|
|
Post by deerwings on Oct 30, 2018 21:41:22 GMT
Sorry deerwings , I thought about modified one. my bad. That's alright, I figured! Now that I have mine modified and working properly, I seem to be having trouble adding a game to the Carousel. I've got the vsf.gz image, I've got the art formatted correctly and the tsg file in the same place as the others and all files in their correct directories, but it's still not showing up on the Carousel. Did I miss a step? |
|
|
|
Post by darbyram on Oct 30, 2018 21:54:32 GMT
Sorry deerwings , I thought about modified one. my bad. That's alright, I figured! Now that I have mine modified and working properly, I seem to be having trouble adding a game to the Carousel. I've got the vsf.gz image, I've got the art formatted correctly and the tsg file in the same place as the others and all files in their correct directories, but it's still not showing up on the Carousel. Did I miss a step? Are all the files named correctly and are the same. i have made the mistake in the past, I had the config file .TSG rather than .tsg |
|
|
|
Post by deerwings on Oct 30, 2018 21:57:00 GMT
That's alright, I figured! Now that I have mine modified and working properly, I seem to be having trouble adding a game to the Carousel. I've got the vsf.gz image, I've got the art formatted correctly and the tsg file in the same place as the others and all files in their correct directories, but it's still not showing up on the Carousel. Did I miss a step? Are all the files named correctly and are the same. i have made the mistake in the past, I had the config file .TSG rather than .tsg Yes, they're all named correctly, and everything is actually lower case except for the first character T:Gyruss X:64,ntsc,truedrive,sid6581 D:en:With its notable cabinet art and a stereo sound system not yet commonly found in arcade games, Gyruss featured multiple innovations. Gyruss is also what is known as a 'tube shooter,' which is indicative of the player's viewpoint. Although somewhat abstract at times, Gyruss was programmed to depict the action in 3-dimensional graphics. First debuting in Japan in 1983, Gyruss was developed solely by Konami. D:fr:No French! D:de:Nein Deutsch! D:es:No Habla Espanol! D:it:No Scusa de Italia! A:Konami M:Masahiro Inoue E:shoot Y:1983 F:games/Gyruss.vsf.gz C:covers/Gyruss-cover.png G:screens/Gyruss-01.png G:screens/Gyruss-02.png J:1*:JU,JD,JL,JR,JF,EN,RS,SP,SP,Y,N,F7,JF |
|
|
|
Post by deerwings on Oct 30, 2018 22:01:50 GMT
Wait, weird, I just discovered it's hijacked the boxart from Cosmic Causeway now. Okay, this means there's some troubleshooting to do.
|
|
|
|
Post by darbyram on Oct 30, 2018 22:08:20 GMT
Wait, weird, I just discovered it's hijacked the boxart from Cosmic Causeway now. Okay, this means there's some troubleshooting to do. Very weird indeed, you using the usb method? |
|
|
|
Post by deerwings on Oct 30, 2018 22:19:39 GMT
I'm creating the files and then moving them onto the C64 itself.
|
|
|
|
Post by darbyram on Oct 30, 2018 22:25:36 GMT
I'm creating the files and then moving them onto the C64 itself. USB is far easier, but that's my personal preference. |
|
|
|
Post by deerwings on Oct 30, 2018 22:59:19 GMT
Figured out what it was, I was saving the .tsg in the wrong format. It was in Windows CR/LF format instead of Unix LF format. Now, to get the game to actually load!
|
|
|
|
Post by deerwings on Oct 30, 2018 23:34:55 GMT
Okay! So the solution is this:
In addition to make sure your art is in the correct format, make sure you also create your .tsg file with Notepad++ and make sure it's in Unix LF format, not Windows CR/LF format.
Also, .d64 images can be used. Just compress them as a .gz just like a vsf image. It's a pain in the butt to make a good .vsf image, when you can just compress the .d64 and it's still reasonably small.
Hope this helps!
|
|
|
|
Post by steeldust on Oct 31, 2018 20:03:18 GMT
Are all the files named correctly and are the same. i have made the mistake in the past, I had the config file .TSG rather than .tsg Yes, they're all named correctly, and everything is actually lower case except for the first character T:Gyruss X:64,ntsc,truedrive,sid6581 D:en:With its notable cabinet art and a stereo sound system not yet commonly found in arcade games, Gyruss featured multiple innovations. Gyruss is also what is known as a 'tube shooter,' which is indicative of the player's viewpoint. Although somewhat abstract at times, Gyruss was programmed to depict the action in 3-dimensional graphics. First debuting in Japan in 1983, Gyruss was developed solely by Konami. D:fr:No French! D:de:Nein Deutsch! D:es:No Habla Espanol! D:it:No Scusa de Italia! A:Konami
M:Masahiro Inoue
E:shoot
Y:1983
F:games/Gyruss.vsf.gz
C:covers/Gyruss-cover.png
G:screens/Gyruss-01.png
G:screens/Gyruss-02.png
J:1*:JU,JD,JL,JR,JF,EN,RS,SP,SP,Y,N,F7,JF
D:it:No Scusa de Italia! Please... "Non parlo Italiano" :-D |
|
|
|
Post by deerwings on Oct 31, 2018 23:30:33 GMT
D:it:No Scusa de Italia! Please... "Non parlo Italiano" :-D
I just threw what randomly came to my head that seemed funny to me at the time. 
|
|
|
|
Post by darbyram on Nov 7, 2018 19:47:44 GMT
Okay! So the solution is this: In addition to make sure your art is in the correct format, make sure you also create your .tsg file with Notepad++ and make sure it's in Unix LF format, not Windows CR/LF format. Also, .d64 images can be used. Just compress them as a .gz just like a vsf image. It's a pain in the butt to make a good .vsf image, when you can just compress the .d64 and it's still reasonably small. Hope this helps! |
|
|
|
Post by deerwings on Nov 7, 2018 20:02:05 GMT
.d64, .d81, .d82, .crt, .t64 and .tap images have been confirmed working, I've had some issues with .d71 so your mileage will vary, yes. But have to make sure that the Cover and Screen images are the correct screen resolutions as the Carousel is VERY picky. I recommend reducing the color size to 256 colors for the covers, or even 16 colors for the screenshots (I've had good success with reducing them to 16 colors) to minimize space. Most of my covers look great and they're around 4-8kb in size, while my covers are around 12kb or so.
|
|
|
|
Post by deerwings on Nov 9, 2018 21:40:07 GMT
So, I've discovered that WinVice 2.4 can automatically load file lists with a commandline switch, which allow you to have multiple images but keyed to a specific drive and then you just toggle through the images as needed.
Vice 2.4 can create a Flip List called <Gamename>.vfl and looks similar to below (Example is Buck Rogers):
So the trick will be to see if there is a way to force the C64 Mini's version of Vice to load a flip list and then try to figure out a way to get it to toggle between the images (Much in the way an SD2IEC would on a real C64). But I'm not sure how to get it to fake running an image and instead run something that will allow you to input switches.
Vice's files are located in /usr/lib/vice but none are marked executable. But since a .tsg file effectively must be passing the image name to a commandline somehow (eg. in the .tsg, passes F:games/GAMENAME.vsf.gz).
If we can figure out how to get Vice to run with switches (Unless it's been modified) on our own terms, it might be a step towards hacking in multi-disk games.
|
|
|
|
Post by darbyram on Nov 9, 2018 21:55:31 GMT
So, I've discovered that WinVice 2.4 can automatically load file lists with a commandline switch, which allow you to have multiple images but keyed to a specific drive and then you just toggle through the images as needed. Vice 2.4 can create a Flip List called <Gamename>.vfl and looks similar to below (Example is Buck Rogers): So the trick will be to see if there is a way to force the C64 Mini's version of Vice to load a flip list and then try to figure out a way to get it to toggle between the images (Much in the way an SD2IEC would on a real C64). But I'm not sure how to get it to fake running an image and instead run something that will allow you to input switches. Vice's files are located in /usr/lib/vice but none are marked executable. But since a .tsg file effectively must be passing the image name to a commandline (eg. in the .tsg, passes F:games/GAMENAME.vsf.gz). If we can figure out how to get Vice to run with switches (Unless it's been modified) on our own terms, it might be a step towards hacking in multi-disk games. Was thinking about this last night. If you look at these .tsg files  Then open each one and look how they differ.  |
|
|
|
Post by deerwings on Nov 9, 2018 22:13:28 GMT
Exactly, I was thinking about that, so I'm trying to figure out how it's doing it. I have a suspicion that the64 executable is actually a custom executable that seems to do Vice Functions on its own, and not just a Carousel and Front-end but I'm not sure how it works.
In the TSG there is an extra item I: that seems to tell it which image to load. But since it's a .crt, there's only one file but it's triggering something within that .crt to run a different portion of that game.
|
|
|
|
Post by darbyram on Nov 9, 2018 22:24:52 GMT
Exactly, I was thinking about that, so I'm trying to figure out how it's doing it. I have a suspicion that the64 executable is actually a custom executable that seems to do Vice Functions on its own, and not just a Carousel and Front-end but I'm not sure how it works. In the TSG there is an extra item I: that seems to tell it which image to load. But since it's a .crt, there's only one file but it's triggering something within that .crt to run a different portion of that game. yeah not sure myself. but the .crt contains 4 games. I:1=SUMMER-GAMES I:2=WINTER-GAMES I:3=WORLD-GAMES I:4=CALIFORNIA-GAMES Maybe there is a way somehow to make it work, maybe not. food for thought though |
|
|
|
Post by deerwings on Nov 9, 2018 22:41:47 GMT
I did a test with a .tsg to see if I could make it run a script out of curiosity, but what ended up happening is it went into the C64 Basic loader, and then attempted to load the name of the script as a filename, which of course failed. So the Loader is very, VERY carefully knit, it seems.
I was watching the console and what I think it's doing is quickly copying the image to a snapshot in /tmp/snapshot and then mounting the snapshot as a disk attached to drive 8, and then running the first program on the mounted image unless it's passed a filename it doesn't recognize as a disk format in which case it'll run that instead as a mounted file(I.E. a .prg). Not sure how that helps us, though, since the emulator is already running by this time and there doesn't seem to be any hotkeys within the emulator that it recognizes at this point.
|
|
|
|
Post by deerwings on Nov 9, 2018 22:43:20 GMT
|
|
|
|
Post by darbyram on Nov 9, 2018 22:53:13 GMT
Will have to connect my UART at some point, and watch the output when i am trying things. be great though to have this working.
|
|
|
|
Post by deerwings on Nov 9, 2018 23:29:23 GMT
After the 'DRIVE 8: RESET' is when I run the image from the64. Then all the output underneath is when it actually runs it, but then you can see when I terminate it.
|
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Nov 12, 2018 10:45:25 GMT
Hello I have a problem with the UART connection in the putty terminal. I cannot log in. I looks like i have no keyboard attached. No input is possible. I tried shift lock on/off, num lock on/off, ctrl-q, ctrl-x etc. No reaction So i interrupted the booting with "s" and created a new log in and a new password. Everything went ok. Keyboard input also.
But the next normal boot i had the same problem. Again no keyboard input possible, so i cannot log in.
Here is the boot sequence: ▒HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
current block is 2 and last block is 10.
current block is 3 and last block is 10.
current block is 4 and last block is 10.
current block is 5 and last block is 10.
current block is 6 and last block is 10.
current block is 7 and last block is 10.
sum=0x63c13c11
src_sum=0x63c13c11
The file stored in start block 2 is perfect.
Ready to disable icache.
Jump to secend Boot.
[ 0.178]
U-Boot 2011.09-rc1 (Apr 02 2018 - 11:17:04) Retro Games Ltd
[ 0.185]version: 1.1.0
[ 0.188]pmbus: ready
[ 0.293]PMU: AXP209
[ 0.296]PMU: AXP20x found
[ 0.299]PMU: bat ratio = 100
[ 0.302]after set, dcdc2 =1400mv
[ 0.306]PMU: dcdc2 1400
[ 0.308]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[ 0.316]after set, dcdc2 =1400mv
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.351]DRAM: 256 MiB
relocation Offset is: 05b19000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.591]fetch script data boot_disp.output_type fail
[ 0.596]fetch script data boot_disp.output_mode fail
[ 0.601]fetch script data boot_disp.auto_hpd fail
[ 0.606]lcd0_para.lcd_used=0
workmode = 0
[ 0.611]NAND: NAND_UbootInit
NAND_UbootInit start
NB1 : enter NAND_LogicInit
nand : get id_number_ctl fail, c0003
nand : get CapacityLevel fail, 4fb9e371
not burn nand partition table!
NB1 : nftl num: 1
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 0.889]sunxi flash init ok
fail to find part named env
Using default environment
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:3-
-name- -start- -size-
boot : 1000000 1000000
rootfs : 2000000 7000000
UDISK : 9000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_nand boot_normal
the part isn't exist
board_status_probe
[ 0.945]pre sys mode
[ 0.948]Hit any key to stop autoboot: 0
read boot or recovery all
[ 1.581]sunxi flash read :offset 1000000, 11549374 bytes OK
[ 1.596]ready to boot
[ 1.598][mmc]: MMC Device 2 not found
[ 1.602][mmc]: mmc not find,so not exit
NAND_UbootExit
NB1 : NAND_LogicExit
[ 1.606]
Starting kernel ...
[ 0.991739] rtc_hw_init(416) err: set clksrc to external losc failed! rtc time will be wrong
[ 1.001343] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.076967] [hdmi]hdmi module init
[ 1.082392] ##fb init:w=1280,h=720,fbmode=0
[ 1.099654] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.105818] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock
root=/dev/nandb
insmod nand.ko return 0
e2fsck /dev/nandb return 0
mount /dev/nandb return 0
[ 2.277490] sd 0:0:0:0: [sda] No Caching mode page present
[ 2.284159] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2.307571] sd 0:0:0:0: [sda] No Caching mode page present
[ 2.319265] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2.339135] sd 0:0:0:0: [sda] No Caching mode page present
[ 2.345305] sd 0:0:0:0: [sda] Assuming drive cache: write through
RedQuark One
redquarkone login:
I hope, one of the "linux professionals" here can help me with a solution.  |
|
|
|
Post by jj0 on Nov 12, 2018 12:55:02 GMT
Hello I have a problem with the UART connection in the putty terminal. I cannot log in. I looks like i have no keyboard attached. No input is possible. I tried shift lock on/off, num lock on/off, ctrl-q, ctrl-x etc. No reaction So i interrupted the booting with "s" and created a new log in and a new password. Everything went ok. Keyboard input also.
But the next normal boot i had the same problem. Again no keyboard input possible, so i cannot log in.
I hope, one of the "linux professionals" here can help me with a solution. I have this occasionally, usually when I power the board from my PC's USB port instead of from a powered USB hub. So now I connect a powered USB hub to my PC and use that to connect to and power the Mini. |
|
|
|
Post by deerwings on Nov 12, 2018 15:48:47 GMT
Hello I have a problem with the UART connection in the putty terminal. I cannot log in. I looks like i have no keyboard attached. No input is possible. I tried shift lock on/off, num lock on/off, ctrl-q, ctrl-x etc. No reaction So i interrupted the booting with "s" and created a new log in and a new password. Everything went ok. Keyboard input also.
But the next normal boot i had the same problem. Again no keyboard input possible, so i cannot log in.
I hope, one of the "linux professionals" here can help me with a solution. I have this occasionally, usually when I power the board from my PC's USB port instead of from a powered USB hub. So now I connect a powered USB hub to my PC and use that to connect to and power the Mini. Occasionally mine will crash my PC with a IRQL_NOT_LESS_THAN_OR_EQUAL or another blue screen that seems driver-related. It seems like your mileage may vary depending on what UART to TTY adapter you're using and its compatibility. I have mine with the single USB connection mod as per one of the other posts, but I'm considering installing a dedicated USB port just for the UART. |
|
|
|
Post by spannernick on Nov 12, 2018 22:29:51 GMT
Can the64 (UI)run snapshots,ask cos the disks can be saved as part of the snapshot,the games on the Carousel are snapshots,when you press fire on one it copies it to /tmp/snapshot file. then deletes it when you close the game.I can see it doing it when I try and run a game on the CB2 but it crashes.I wish I could make the64 on TheC64 Mini to crash then maybe a shell with come up on the screen.I don't know if it possible.If you could get into it and use a keyboard and a shell on your tV then you wont need the uart.
|
|
|
|
Post by deerwings on Nov 12, 2018 22:48:16 GMT
Unfortunately not directly. The The64 application does not run overtop a console, so it just hangs on screen until it's restarted or until the Mini is restarted. It would be nice if it would drop to a console but it's probably designed that way so that it keeps it as simple as possible. There is likely a way to boot directly into busybox.
The64 executable DOES run Vice snapshots as long as they're loaded into their carousel. I experimented with commandline options (e.g. the64 -autoload -8 /usr/share/the64/games/gamename.vsf.gz) but all it does is run another instance of the64 on top of itself. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Nov 12, 2018 23:18:43 GMT
Hello I have a problem with the UART connection in the putty terminal. I cannot log in. I looks like i have no keyboard attached. No input is possible. I tried shift lock on/off, num lock on/off, ctrl-q, ctrl-x etc. No reaction So i interrupted the booting with "s" and created a new log in and a new password. Everything went ok. Keyboard input also.
But the next normal boot i had the same problem. Again no keyboard input possible, so i cannot log in.
I hope, one of the "linux professionals" here can help me with a solution. I have this occasionally, usually when I power the board from my PC's USB port instead of from a powered USB hub. So now I connect a powered USB hub to my PC and use that to connect to and power the Mini.Ok, I tried this. But in my case it is the opposite. I took the power from my powered usb hub and had the problem. Now I use the "normal" usb connection at my notebook and I can log in now. Very good idea. Thank you very much. But i don't understand the reason why it is so. so what, problem solved.
|
|
|
|
Post by jj0 on Nov 20, 2018 23:01:43 GMT
Btw, to boot into the '#' prompt to modify the root password first time, instead of 'set nand_root /dev/sda' in uboot you can also do 'set console, ${console} ramfs' and then 'boot'. As it turns out the initial startup script of the Mini checks for the 'ramfs' parameter (standard Allwinner SDK script) to stop the boot process before loading the nand driver.
|
|
|
|
Post by beaps on Nov 21, 2018 1:15:45 GMT
If you're interested i shared my added games on Facebook Group. www.sendspace.com/file/h3ddycI added this to my C64 tonight and I have 2 issues. 1. I changed the original carosol music to .old and it gave me an error when I tried copying the ocean loader music so I have no music at all now. 2. When the Mini starts I have no input at all so I cannot navigate the carosol Any ideas Great work popcorn, have put this on mine and works a treat. though with the next update it will overwrite everything i have done to my mini. hopefully better things and ways will come along. |
|
Feb 5, 2024 14:16:57 GMT
Feb 5, 2024 14:16:57 GMT