|
|
Post by spannernick on Dec 30, 2018 11:30:28 GMT
When I use the uart I did use the rubber band but if you keep the pins in uart cable you don't need it,just stick the 3 pins in there and move the cable until you see the red Led on Thec64 Mini come on and your uart is connected..  and remember make sure your uart is at 3.3v not 5v and RX is the same,otherwise it will blow the uart on TheC64 Mini but you probably know that.. |
|
|
|
Post by spannernick on Dec 30, 2018 11:54:47 GMT
1728_____28_-rwxr-xr-x_____1_root_______root___________27454_Jan__1__2000_____WEST-BANK.vsf.gz 1729_____36_-rwxr-xr-x_____1 root_______root___________36152_Jan__1__2000_____JUMPMAN-JUNIOR.vsf.gz 1724______4_-rwxr-xr-x_____1 root_______root____________1444_Jan__1__2000_____WEST-BANK.tsg 1725______4_-rwxr-xr-x_____1 root_______root____________1651_Jan__1__2000_____JUMPMAN-JUNIOR.tsg 1726_____20_-rwxr-xr-x_____1 root_______root___________17774_Jan__1__2000_____WEST-BANK-cover.png 1727_____12_-rwxr-xr-x_____1 root_______root___________12195_Jan__1__2000_____JUMPMAN-JUNIOR-cover.png 1730______4_-rwxr-xr-x_____1 root_______root____________3367_Jan__1__2000_____WEST-BANK-01.png 1731______4_-rwxr-xr-x_____1 root_______root____________2704_Jan__1__2000_____WEST-BANK-02.png 1732______4_-rw-r--r--_____1_root_______root____________1509_Jan__1__2000_____JUMPMAN-JUNIOR-01.png 1733______4_-rw-r--r--_____1_root_______root____________1539_Jan__1__2000_____JUMPMAN-JUNIOR-02.png I think that all of them.. |
|
|
|
Post by spannernick on Dec 30, 2018 12:23:28 GMT
Just made a quick video showing FEL MODE booting,got to edit it and I upload later today on Youtube.
|
|
|
|
Post by spannernick on Dec 30, 2018 12:47:41 GMT
I was wondering.. can you get it to auto mount nandb to mnt so I can just connect straight to the network and FTP from my PC and then browse to the games folder in Filezilla..? Yes you can get it to automount nandb but I left it out on purpose because I want people to do it consiously. However it is very easy to add if you use the scripts option on a USB drive. You need to create a 'scripts' folder on the USB drive and then create a linux-type text file (so only line-feeds at the end of a line, no carriage returns), e.g. 'S01mount-nandb'. Then edit it to contain: . script_helper
echo "${clr_grn}Script $0"
echo "${clr_grn}Loading NAND driver"
insmod -f /opt/nand.ko
if [ -b /dev/nandb ]
then
echo "${clr_grn}Mounting C64 Mini rootfs /dev/nandb on /mnt"
mkdir /mnt
mount /dev/nandb /mnt
if [ $? -eq 0 ]
then
echo "${clr_grn}Mount /dev/nandb to /mnt OK"
else
echo "${clr_red}Mounting failed (error $?)"
fi
else
echo "${clr_red}/dev/nandb not found (error $?)"
fi
If you then boot with the FEL method and the USB stick inserted it will run this script and mount /dev/nandb to /mnt. Just found out something.. if you don't have a button for FEL,open TheC64 MIni and unplug the red Light and plug it into the FEL connector and then plug Micro usb in and bingo you are in FEL Mode.. it has the same header pins. Cool man, using the LED plug for this is genius! I copied 2 games to the games folder via ftp and they are not showing up but I do have 84 + 65 = 149 games in there.. is that why,I copied all the right files but no show so in there is 151 games now but only 149 are showing in the Carousel..? Not sure. You could check if the 'the64' program shows any error messages, kill it first with 'killall the64' (I do this twice) and then from the command prompt run 'the64' manually. I made a file called S01mount-nandb and put the code it,it was a .txt file and remove .txt from it and put it on my USB and in the scripts folder but it not running the script and not mounting nandb..?? what am I doing wrong..? |
|
|
|
Post by jj0 on Dec 30, 2018 16:04:40 GMT
1728_____28_-rwxr-xr-x_____1_root_______root___________27454_Jan__1__2000_____WEST-BANK.vsf.gz 1729_____36_-rwxr-xr-x_____1 root_______root___________36152_Jan__1__2000_____JUMPMAN-JUNIOR.vsf.gz 1724______4_-rwxr-xr-x_____1 root_______root____________1444_Jan__1__2000_____WEST-BANK.tsg 1725______4_-rwxr-xr-x_____1 root_______root____________1651_Jan__1__2000_____JUMPMAN-JUNIOR.tsg 1726_____20_-rwxr-xr-x_____1 root_______root___________17774_Jan__1__2000_____WEST-BANK-cover.png 1727_____12_-rwxr-xr-x_____1 root_______root___________12195_Jan__1__2000_____JUMPMAN-JUNIOR-cover.png 1730______4_-rwxr-xr-x_____1 root_______root____________3367_Jan__1__2000_____WEST-BANK-01.png 1731______4_-rwxr-xr-x_____1 root_______root____________2704_Jan__1__2000_____WEST-BANK-02.png 1732______4_-rw-r--r--_____1_root_______root____________1509_Jan__1__2000_____JUMPMAN-JUNIOR-01.png 1733______4_-rw-r--r--_____1_root_______root____________1539_Jan__1__2000_____JUMPMAN-JUNIOR-02.png I think that all of them.. Looks OK to me. So must be the max games limit that you mentioned. |
|
|
|
Post by jj0 on Dec 30, 2018 16:18:23 GMT
Yes you can get it to automount nandb but I left it out on purpose because I want people to do it consiously. However it is very easy to add if you use the scripts option on a USB drive. You need to create a 'scripts' folder on the USB drive and then create a linux-type text file (so only line-feeds at the end of a line, no carriage returns), e.g. 'S01mount-nandb'. Then edit it to contain: . script_helper
echo "${clr_grn}Script $0"
echo "${clr_grn}Loading NAND driver"
insmod -f /opt/nand.ko
if [ -b /dev/nandb ]
then
echo "${clr_grn}Mounting C64 Mini rootfs /dev/nandb on /mnt"
mkdir /mnt
mount /dev/nandb /mnt
if [ $? -eq 0 ]
then
echo "${clr_grn}Mount /dev/nandb to /mnt OK"
else
echo "${clr_red}Mounting failed (error $?)"
fi
else
echo "${clr_red}/dev/nandb not found (error $?)"
fi
If you then boot with the FEL method and the USB stick inserted it will run this script and mount /dev/nandb to /mnt. Cool man, using the LED plug for this is genius! Not sure. You could check if the 'the64' program shows any error messages, kill it first with 'killall the64' (I do this twice) and then from the command prompt run 'the64' manually. I made a file called S01mount-nandb and put the code it,it was a .txt file and remove .txt from it and put it on my USB and in the scripts folder but it not running the script and not mounting nandb..?? what am I doing wrong..? Hard to say. - Is it a linux-type text file or Windows-type? You have to save it as linux, so no 'carrier returns' at the end of the line.
- Do you see the script being found and announced, like '/etc/init.d/S99exec_usb_scripts: Found script: /mnt/scripts/S01mount-nandb'
- Do you see any error messages
- If you've booted into FEL mode, can you manually mount the USB drive to /mnt and execute the script?
- Can you attach the script to your post?
- Maybe try with a simple script first?
|
|
|
|
Post by amigasubwaycrew on Dec 30, 2018 16:27:08 GMT
Many thanks for this, and one question..... USB 3.0 UGreen LAN Adapter didnt work on Mini, because my C64 displays root@c64mini ():/#
..or is there a way to add a driver for this?!?! >> Im not a Linux Guru, so i think i must order a usb2.0 adapter tomorrow
|
|
|
|
Post by spannernick on Dec 30, 2018 18:13:09 GMT
|
|
|
|
Post by jj0 on Dec 30, 2018 19:03:53 GMT
Many thanks for this, and one question..... USB 3.0 UGreen LAN Adapter didnt work on Mini, because my C64 displays root@c64mini ():/#
..or is there a way to add a driver for this?!?! >> Im not a Linux Guru, so i think i must order a usb2.0 adapter tomorrow
I might be able to add it. When you have it inserted can you do an 'lsusb' to show the ID/description and also a 'dmesg'? You could also try to log out ('exit' or 'CTRL-D') and login again? Sometimes if it takes a long time to get a DHCP IP address the prompt is already there and will show an empty IP address. |
|
|
|
Post by FaberfoX on Dec 30, 2018 20:08:02 GMT
Thanks for reporting back. It looks like the nand in your Mini isn't supported by the nand driver from 'my' European fw_1_2_0 nand.ko. At least I can't find the nand ID (0x9b 0xf1 0x0 0x1d 0x9b 0xf1) in the nand.ko. I guess it's an ATO AFND1G08U3. It could be yours is a newer version or there's a difference between PAL and non-PAL versions. Can you show: - Your firmware version and build date, mine are theC64-1.2.0-argent from 19-12-2018 20:22:40.
- A picture of your NAND chip, or just provide the text that's on the chip?
- If you happen to also have an UART connected a copy of all NAND-related boot or 'dmesg' output. Or the entire text.
I'ts a bit of a catch-22, to make this 'no UART required' work with this NAND chip I'd need a copy of the /lib/modules/3.4.39/nand.ko driver if the one I have doesn't support the nand chip. And currently the only way to get it is for someone to attach a UART (rubberbanding, not necessarily soldering), do the 'boot to RAMFS trick' and copy the nand driver and post it/send it to me to add. Of course once you have the nand driver you can use it yourself straight away from a USB drive.  Totally correct, I'm attaching a picture of the NAND and of my nand.ko. Using it I was able to mount /dev/nandb.  Sorry I didn't catch the firmware version and build date, don't have an USB-UART so I used a Raspi 3, if it's on a file let me know which one and I'll get that, otherwise, a few hours from now I'll hook it to the Raspi again. Attachments:nand.ko.zip (485.94 KB)
|
|
|
|
Post by amigasubwaycrew on Dec 30, 2018 21:31:05 GMT
Many thanks for this, and one question..... USB 3.0 UGreen LAN Adapter didnt work on Mini, because my C64 displays root@c64mini ():/#
..or is there a way to add a driver for this?!?! >> Im not a Linux Guru, so i think i must order a usb2.0 adapter tomorrow
I might be able to add it. When you have it inserted can you do an 'lsusb' to show the ID/description and also a 'dmesg'? You could also try to log out ('exit' or 'CTRL-D') and login again? Sometimes if it takes a long time to get a DHCP IP address the prompt is already there and will show an empty IP address.
Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 005 Device 002: ID 04f2:1125 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 1.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub |
|
|
|
Post by jj0 on Dec 31, 2018 12:16:43 GMT
I might be able to add it. When you have it inserted can you do an 'lsusb' to show the ID/description and also a 'dmesg'? You could also try to log out ('exit' or 'CTRL-D') and login again? Sometimes if it takes a long time to get a DHCP IP address the prompt is already there and will show an empty IP address.
Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 005 Device 002: ID 04f2:1125 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 1.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub From the output 'Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet' your USB network adapter should is an ASIX and should be supported already by the driver that's included. So I'm not sure why you don't see an IP address. The included driver is quite old so maybe a newer version is needed. What happens if you do a: - Check on your router if there has been an IP address assigned to the adapter?
- CTRL-D to logout and then login again. Does the prompt show an IP address?
- ping to your router's IP address? E.g. 'ping 192.168.1.1' but replace the IP address with your router's address. Or 'ping 139.59.181.200' which is retrogames.biz
- ifconfig eth0
- dmesg | grep usb
- dmesg | grep eth
|
|
|
|
Post by jj0 on Dec 31, 2018 12:50:10 GMT
Thanks for reporting back. It looks like the nand in your Mini isn't supported by the nand driver from 'my' European fw_1_2_0 nand.ko. At least I can't find the nand ID (0x9b 0xf1 0x0 0x1d 0x9b 0xf1) in the nand.ko. I guess it's an ATO AFND1G08U3. It could be yours is a newer version or there's a difference between PAL and non-PAL versions. Can you show: - Your firmware version and build date, mine are theC64-1.2.0-argent from 19-12-2018 20:22:40.
- A picture of your NAND chip, or just provide the text that's on the chip?
- If you happen to also have an UART connected a copy of all NAND-related boot or 'dmesg' output. Or the entire text.
I'ts a bit of a catch-22, to make this 'no UART required' work with this NAND chip I'd need a copy of the /lib/modules/3.4.39/nand.ko driver if the one I have doesn't support the nand chip. And currently the only way to get it is for someone to attach a UART (rubberbanding, not necessarily soldering), do the 'boot to RAMFS trick' and copy the nand driver and post it/send it to me to add. Of course once you have the nand driver you can use it yourself straight away from a USB drive. Totally correct, I'm attaching a picture of the NAND and of my nand.ko. Using it I was able to mount /dev/nandb. Sorry I didn't catch the firmware version and build date, don't have an USB-UART so I used a Raspi 3, if it's on a file let me know which one and I'll get that, otherwise, a few hours from now I'll hook it to the Raspi again. Thanks for providing your nand.ko. It's the same as mine from firmware 1_2_0, except that there is support for 2 ATO nand chips added. So I'll use yours for the next update of the kernel/ramdisk. If you can show your firmware version (from the Carousel menu) that would be interesting. |
|
|
|
Post by amigasubwaycrew on Dec 31, 2018 15:03:29 GMT
Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 005 Device 002: ID 04f2:1125 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 1.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub From the output 'Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet' your USB network adapter should is an ASIX and should be supported already by the driver that's included. So I'm not sure why you don't see an IP address. The included driver is quite old so maybe a newer version is needed. What happens if you do a: - Check on your router if there has been an IP address assigned to the adapter?
- CTRL-D to logout and then login again. Does the prompt show an IP address?
- ping to your router's IP address? E.g. 'ping 192.168.1.1' but replace the IP address with your router's address. Or 'ping 139.59.181.200' which is retrogames.biz
- ifconfig eth0
- dmesg | grep usb
- dmesg | grep eth
bought today an usb2.0 lan adapter - and now it works - so its indeed a usb3.0 problem |
|
|
|
Post by spannernick on Dec 31, 2018 15:39:17 GMT
The script is still not mounting nandb,I made it in Notepad++ and pick Unix script file here is the script,I just remove .bash at the end of the name of the file. Attachments:S01mount-nandb (432 B)
|
|
|
|
Post by spannernick on Dec 31, 2018 16:40:23 GMT
I just tested on my TheC64 Mini without a uart and it works copied all the games from the US version via FTP and the games play fine so 149 games is the limit you can have on the Carousel.NO its 150 thanks Popcorn |
|
|
|
Post by darbyram on Dec 31, 2018 17:32:33 GMT
I just tested on my TheC64 Mini without a uart and it works copied all the games from the US version via FTP and the games play fine so 149 games is the limit you can have on the Carousel. Get more with USB though ;-) |
|
|
|
Post by FaberfoX on Dec 31, 2018 21:39:26 GMT
Thanks for providing your nand.ko. It's the same as mine from firmware 1_2_0, except that there is support for 2 ATO nand chips added. So I'll use yours for the next update of the kernel/ramdisk. If you can show your firmware version (from the Carousel menu) that would be interesting. Build theC64-1.2.0-shield
Build date 19-12-2018 20:24:17
jj0 , my intention is to keep my mini physically intact, so I'm looking for a way to enter FEL without drilling a hole on it. From what you've gathered so far, do you think this will be possible? My guess is this would be easy flashing a new nanda but I'm not sure if that would mess with future updates. For now, I plan to get a reed switch and tape it to the left side of the mini, that way I can keep it untouched and FEL boot by placing a magnet close to it on the outside 
Edit: Sent you a PM.
|
|
|
|
Post by jj0 on Dec 31, 2018 21:46:30 GMT
Thanks for providing your nand.ko. It's the same as mine from firmware 1_2_0, except that there is support for 2 ATO nand chips added. So I'll use yours for the next update of the kernel/ramdisk. If you can show your firmware version (from the Carousel menu) that would be interesting. Build theC64-1.2.0-shield
Build date 19-12-2018 20:24:17
jj0, my intention is to keep my mini physically intact, so I'm looking for a way to enter FEL without drilling a hole on it. From what you've gathered so far, do you think this will be possible? My guess is this would be easy flashing a new nanda but I'm not sure if that would mess with future updates. For now, I plan to get a reed switch and tape it to the left side of the mini, that way I can keep it untouched and FEL boot by placing a magnet close to it on the outside
Yes, I've replaced nanda as test, but I'm not quite happy with the result yet. It will be safer than changing the nandb. For FEL mode the reed switch sounds cool. You could also put a button in place of the red power LED. |
|
|
|
Post by johno75 on Jan 2, 2019 8:31:29 GMT
Worked a treat for me. I downloaded the uart mod game pack that’s linked to on here and used the copy game script and it copied them all over automatically and all works.
Is there an easy way to create the game files and screens etc needed or is there anywhere I can request games in the format/files needed to copy across? There’s only a few games I’d want like manic miner and a few others.
|
|
|
|
Post by jj0 on Jan 2, 2019 11:02:19 GMT
Worked a treat for me. I downloaded the uart mod game pack that’s linked to on here and used the copy game script and it copied them all over automatically and all works. Is there an easy way to create the game files and screens etc needed or is there anywhere I can request games in the format/files needed to copy across? There’s only a few games I’d want like manic miner and a few others. The easiest way is probably to load the game once from USB, start it on the Mini and then make a snapshot. Then you can find the snapshot and screenshots in a '.THEC64SAVE' folder (subfolder <GAMENAME>). You still have to make the .tsg game description file and a cover .png. You might not need a snapshot, I've read somehere that other formats (e.g. .D64) work as well. |
|
|
|
Post by popcorn on Jan 2, 2019 12:20:14 GMT
I copied 2 games to the games folder via ftp and they are not showing up but I do have 84 + 65 = 149 games in there.. is that why,I copied all the right files but no show so in there is 151 games now but only 149 are showing in the Carousel..?
I had the original 64 games + 84 added games + basic + hall-of-fame = 150 items, everything showing. So i flashed the new 1.2.0 firmware that added Galencia.. everything's well but the 150 items were the same and no Galencia showed. Then i renamed the THE64-HALL-OF-FAME.tsg to THEC64-HALL-OF-FAME.old to remove it from the list and... TADAAA! Galencia popped up! 150 items (intended as 150 .tsg files in the "/usr/share/the64/games" folder) is the current limit. |
|
|
|
Post by jj0 on Jan 6, 2019 10:59:17 GMT
I've updated some stuff:- Updated nand.ko driver to the version in C64 Mini firmware 1_2_0-shield (adds ATO NAND support). Thanks FaberfoX !. This is a bit of a pain, as the firmware updates apparently don't update the nand.ko driver. While this is logical (the nand.ko that's already on the device obviously supports the NAND chip on the device) it means that if newer Mini's have differnet NAND chips then I need some kind soul the send me their nand.ko to support it.
- Added driver for USB2Ethernet ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet Devices. amigasubwaycrew , this should support your USB 3.0 adapter now, if you feel up to it can you let me know if it works?
- Changed music player from mpg123 playing mp3's to sidplay2 playing sid files
- Minor changes to example scripts
- Minor changes to /etc/inittab
- Changed prompt to show full path
First post is updated with the link to the updated zipfile.
|
|
|
|
Post by amigasubwaycrew on Jan 8, 2019 17:45:41 GMT
I've updated some stuff: - Updated nand.ko driver to the version in C64 Mini firmware 1_2_0-shield (adds ATO NAND support). Thanks FaberfoX !. This is a bit of a pain, as the firmware updates apparently don't update the nand.ko driver. While this is logical (the nand.ko that's already on the device obviously supports the NAND chip on the device) it means that if newer Mini's have differnet NAND chips then I need some kind soul the send me their nand.ko to support it.
- Added driver for USB2Ethernet ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet Devices. amigasubwaycrew , this should support your USB 3.0 adapter now, if you feel up to it can you let me know if it works?
- Changed music player from mpg123 playing mp3's to sidplay2 playing sid files
- Minor changes to example scripts
- Minor changes to /etc/inittab
- Changed prompt to show full path
First post is updated with the link to the updated zipfile.
|
|
|
|
Post by mobluse on Jan 18, 2019 22:12:19 GMT
I got FEL mode working on my global model with silver sticker (made a hole in the sticker). I used Windows 10 with x86-64. First I tried it on a Raspberry Pi 3B with Raspbian. I also installed in Raspbian (sudo apt-get install sunxi-tools) and changed one script so that it used the installed tools (removed './'), but it didn't help. I have an x86 computer (Eee PC 900) with Lubuntu 18.04, but the Linux tools might not work on that because they are x86-64. Maybe it's possible to make a version that uses the sunxi-tools from the distro (i.e. that also works with x86 and ARM CPUs).
My THEC64 MINI is normally 50 Hz, but when you run it in FEL mode it's 60 Hz. My screen could not adapt to that because now it seems to be locked to 50 Hz when I use the HDMI to VGA converter. The screen can handle other computers using 60 Hz, e.g. a Raspberry Pi Zero running Combian 64 using the same HDMI to VGA converter. Maybe you could send some other EDID over HDMI when using the FEL mode. It was good there was sound, otherwise I might have given up, when there was no picture.
When I used another screen it worked, but the picture is too much up and to the left, and even if I move it back using maximum vertical and horizontal settings, I miss the top and left of text.
I also noticed that when I run 'less' it only uses the top left corner.
It seems to be using C64 colors and fonts in Linux, which is a nice touch!
After booting you don't use the microUSB connector. Maybe one could have a terminal emulator (e.g. PuTTY) connected to that somehow.
I have one question: How long do you need to hold the button pressed in order to have FEL mode?
|
|
|
|
Post by jj0 on Jan 19, 2019 10:23:32 GMT
I got FEL mode working on my global model with silver sticker (made a hole in the sticker). I used Windows 10 with x86-64. First I tried it on a Raspberry Pi 3B with Raspbian. I also installed in Raspbian (sudo apt-get install sunxi-tools) and changed one script so that it used the installed tools (removed './'), but it didn't help. I have an x86 computer (Eee PC 900) with Lubuntu 18.04, but the Linux tools might not work on that because they are x86-64. Maybe it's possible to make a version that uses the sunxi-tools from the distro (i.e. that also works with x86 and ARM CPUs). My THEC64 MINI is normally 50 Hz, but when you run it in FEL mode it's 60 Hz. My screen could not adapt to that because now it seems to be locked to 50 Hz when I use the HDMI to VGA converter. The screen can handle other computers using 60 Hz, e.g. a Raspberry Pi Zero running Combian 64 using the same HDMI to VGA converter. Maybe you could send some other EDID over HDMI when using the FEL mode. It was good there was sound, otherwise I might have given up, when there was no picture. When I used another screen it worked, but the picture is too much up and to the left, and even if I move it back using maximum vertical and horizontal settings, I miss the top and left of text. I also noticed that when I run 'less' it only uses the top left corner. It seems to be using C64 colors and fonts in Linux, which is a nice touch! After booting you don't use the microUSB connector. Maybe one could have a terminal emulator (e.g. PuTTY) connected to that somehow. I have one question: How long do you need to hold the button pressed in order to have FEL mode? Thanks for the feedback and the suggestions. I'm glad the music served some purpose other than just entertainment and that you like the colours. On using native sunxi-fel if available, good idea, I'll add a check to that in the next release, whenever it comes . On the videomodes, the video mode used is hardcoded in the script.bin. I use a script.bin that sets 1920x1080x60Hz. As you point out, this is not suitable to all TV's monitors. You can experiment with different settings (using sunxi-fexc for the sunxi-tools and this info on display modes). I've attached a script.bin for 1920x1080x50Hz that might solve your issue. You could also try to use the tool from here to set the video mode to 1920x1080x50Hz (hdmi mode 9). On less using only a top left part of the screen. This has to do with how many columns and rows it thinks it has. If you use 'stty rows <xx> cols <yy>;reset' .e.g 'stty rows 50 cols 132;reset' you can change this. On using the micro-USB connector, I would like to enable this as an OTG network device, as that would remove the need for people to use e.g. USB2Serial and USB2Ethernet adapters. But in the 3.4.39 kernel that I use I haven't succeeded in getting the required USB OTG mode to work. As I need to use the 3.4.39 kernel to be able to use the Mini's nand driver (as far as i can see Retrogames LTD have not included a working source for that in their open source release) it's currently not possible. But it is still in the back of my mind... On the FEL mode button press, it's almost immediate as soon as you switch on the Mini. |
|
|
|
Post by mobluse on Jan 19, 2019 13:33:00 GMT
Thanks, with the script-1280x1024x50Hz.bin my screen with 50 Hz works now, both when THEC64 MINI is in normal mode and in FEL mode, but in FEL mode I miss 1.5 characters to the left. When in FEL mode the screen always displays a message that moves to all places of the screen:
"
Input Signal Out of Range
Change Settings to 1280x1024 - 60Hz
"
The screen is an HP Compaq LA1951g. I have tried to turn off all messages and stopped power saving in the screen settings (before it would turn off after a while with the message above). I can only access the screen settings when I run THEC64 MINI in normal mode.
When I run THEC64 MINI in normal mode it says when I show Information:
"
Current Settings:
H=38kHz V=50Hz
Recommended Settings:
1280x1024 - 60Hz
...
"
There is some difference between the signals in normal mode and FEL mode, since there is a constant message from the screen about signal out of range.
Maybe a script-1280x1024-60Hz.bin would help in my case, because it was perhaps the combination of wrong frequency and wrong resolution that led to a black screen after boot. The screen (not a TV) actually handles 60 Hz normally.
This seems to be my screen size:
stty rows 67 cols 112
|
|
|
|
Post by jj0 on Jan 19, 2019 14:54:12 GMT
Thanks, with the script-1280x1024x50Hz.bin my screen with 50 Hz works now, both when THEC64 MINI is in normal mode and in FEL mode, but in FEL mode I miss 1.5 characters to the left. When in FEL mode the screen always displays a message that moves to all places of the screen: " Input Signal Out of Range Change Settings to 1280x1024 - 60Hz " The screen is an HP Compaq LA1951g. I have tried to turn off all messages and stopped power saving in the screen settings (before it would turn off after a while with the message above). I can only access the screen settings when I run THEC64 MINI in normal mode. When I run THEC64 MINI in normal mode it says when I show Information: " Current Settings: H=38kHz V=50Hz Recommended Settings: 1280x1024 - 60Hz ... " There is some difference between the signals in normal mode and FEL mode, since there is a constant message from the screen about signal out of range. Maybe a script-1280x1024-60Hz.bin would help in my case, because it was perhaps the combination of wrong frequency and wrong resolution that led to a black screen after boot. The screen (not a TV) actually handles 60 Hz normally. Try the attached 1280x720x50Hxz one. This is the same mode that the Mini uses. The A20 SoC doesn't support a 1280x1024x60Hz setting on HDMI, only on VGA which the Mini doesn't have. With the attached script.bin if I have my Samsung monitor in 16:9 mode I miss 1.5 letters to the left in FEL mode. But if I switch the monitor to 'Fill screen' mode it scales the image so it fits OK. Note if the Mini's picture display OK that could also mean they use more 'safe one' and the actual graphics area they use is smaller than the 1280x720 that is sent to the disply. You could also try to experiment with fbset and monitor timings. Attachments:script.bin (50.12 KB)
|
|
|
|
Post by mobluse on Jan 19, 2019 16:22:02 GMT
This script.bin (1280x720-50Hz) works perfectly with my screen (HP Compaq LA1951g) and no characters are missing. Now I can also open the screen settings in FEL mode. Now the screen size is best set with (tested using nano):
stty rows 45 cols 75 ; reset
I think this script.bin should work well with other screens and TVs for the global THEC64 MINI.
I can switch back to normal mode using reboot and back again to FEL mode by shutting down and turning on with the sticker button pressed until I hear a beep in Windows, and then run boot.cmd in Windows 10. I don't have to change the screen between the different modes. The Power LED is off when I run in FEL mode.
|
|
|
|
Post by mobluse on Jan 19, 2019 20:13:59 GMT
I did stty rows 45 cols 75 ; resetand opened a few pages long program in the nano editor and scrolled down and up, and it became a mess on the screen. echo $TERM gives xterm-256color. The program I opened in nano was this Snake-game: wp.subnetzero.org/?p=269This program doesn't work with this FEL mode Linux in THEC64 MINI. Bash is probably not the real one. At least one should be able to edit it in Nano. Maybe I have forgotten to configure something. It could also be that the terminal emulation is not exactly xterm-256color. The file snake works in Raspbian Stretch and Lubuntu 16.04 on Raspberry Pi 3 and 2. Also this AWK-program does not work: hackaday.com/2016/01/15/wolfenstein-in-600-lines-of-code/This is probably because the AWK in Busybox is not Gawk. I thought it would be nice to show that you can develop games with Bash/Ash and Awk on THEC64 MINI. Of course you still need a PC to boot. If someone knows games that can be developed in Linux on THEC64 MINI, please give a hint where I can find them. |
|
and remember make sure your uart is at 3.3v not 5v and RX is the same,otherwise it will blow the uart on TheC64 Mini but you probably know that.. 
