|
|
Post by displacer on Feb 25, 2020 19:29:58 GMT
Hmm, you seem to have a different version of the mini source than I. The mini source I have doesn't have the Linux distro with it. Can you msg me a link to the mini source? All I have is the 3 repo's from Classicmods and none of them contain that folder Maybe you can upload only your Maxi linux kernel TGZ? That's definitely 100% open source and all I'm interested in at the moment anyway. The only Retro LTD file in it would be (versions of) their config. They gave me links to most of the software, including the Linux distro, but apparently it's not in the form you have, mine was links to download the entire repo of the files. Like I said, it's a mess but I have not found a config file for the kernel yet. There were no TGZ files... |
|
|
|
Post by jj0 on Feb 25, 2020 19:37:11 GMT
They gave me links to most of the software, including the Linux distro, but apparently it's not in the form you have, mine was links to download the entire repo of the files. Like I said, it's a mess but I have not found a config file for the kernel yet. There were no TGZ files... Ok, well good luck wit the archeological exercize! |
|
|
|
Post by displacer on Feb 26, 2020 14:00:41 GMT
I've about had it with this mess. If I don't make any headway I'll post the links for all the source code
|
|
|
|
Post by sharklodon on Mar 6, 2020 17:47:34 GMT
Hi jj0,
What standard bootable SD-card image for the Orange Pi to be flashed on the Orange Pi are you used?
Thanks,
|
|
|
|
Post by jj0 on Mar 7, 2020 14:09:11 GMT
Hi jj0, What standard bootable SD-card image for the Orange Pi to be flashed on the Orange Pi are you used? Thanks, If I remember correctly I used the Armbian one from the Orange Pi download page. But it doesn't really matter which one, as long as it boots on the Orange Pi model you are using. Of course I changed the uboot settings it to use a nanda copy as kernel and change to rootfs partition to the contents of nandb. |
|
|
|
Post by sharklodon on Mar 7, 2020 14:37:30 GMT
Hi jj0, What standard bootable SD-card image for the Orange Pi to be flashed on the Orange Pi are you used? Thanks, If I remember correctly I used the Armbian one from the Orange Pi download page. But it doesn't really matter which one, as long as it boots on the Orange Pi model you are using. Of course I changed the uboot settings it to use a nanda copy as kernel and change to rootfs partition to the contents of nandb. Thanks for your reply. Then, what are the following steps? I don't have high linux level to know how to add nanda as a kernel and how to change the rootfs partition with nandb. Regards,
|
|
|
|
Post by sharklodon on Mar 8, 2020 6:51:03 GMT
Hi jj0, I mean, I don't know how I can decode nanda and nandb files geenrated with TheC64 Carousel Game Tool (bin files) and copy on an Armbian image. Could you help me? Many thanks, |
|
|
|
Post by jj0 on Mar 8, 2020 12:02:17 GMT
Hi jj0 , I mean, I don't know how I can decode nanda and nandb files geenrated with TheC64 Carousel Game Tool (bin files) and copy on an Armbian image. Could you help me? Many thanks, Don't take this the wrong way but please don't reply to your own posts re-asking the same/a similar question, it comes across as impatient. Different people are in different timezones, I might or might not have seen your original post yet, I might be doing something else, etc etc. Also I believe you can find out a lot by reading/searching the forum and experiment. After all you can't go wrong, worst case is it doesn't work but then you can try again. Having said all that, here are the approximate steps: - nanda is/contains the Linux kernel packaged as Android bootimage, you can extract/manipulate it by using abootimg
- nandb is a copy of the root filesystem partition, in Linux you can mount it
- For the Orange Pi PC you need both nanda and nandb from the Maxi
- Take the Ubuntu Orange Pi PC legacy sdcard image from the Orange Pi download page and write it to an sdcard.
- The sdcard will have two partitions:
- the first one is a FAT partition. Copy your nanda.bin to this partition. You can remove the uImage file.
- the second one is the Orange Pi root filesystem ext4 partition. You need to overwrite this with the contents of nandb. The easiest way to do this is from a linux command prompt, in the directory where your nandb.bin is, with the sdcard as device mmcblk0:
[/code]The last two commands are to resize the filesystem to the size of the partition on the sdcard, otherwise it will think it's only 65MB as that's how big it is on the Maxi's NAND.[/ul][/li][/ul] - From Windows I'm not sure how you would do this
[/span][/span][/li][/ul] - Now you need to ensure that nanda.bin is used as kernel. Connect to the Orange Pi via it's serial port. Power it on and stop it to get into the u-boot prompt. Then type:
# setenv boot_normal fatload mmc 0:1 0x43000000 script.bin;fatload mmc 0:1 0x40007800 nanda.bin;boota 0x400078000
# setenv mmc_root /dev/mmcblk0p2
# saveenv
# reset
- If all is right the Orange Pi PC should now boot thinking it is a Maxi
Good luck 
|
|
|
|
Post by sharklodon on Mar 8, 2020 19:29:59 GMT
Hi jj0, Thanks for your reply. You're right, I'm very impatient. But I want to start as soon as possible!! ;-P I tryed with OrangePi_pc_ubuntu_xenial_server_linux3.4.113_v1.0 image, but I can't umount /dev/mmcblk0p2. Could you help me? Many thanks, |
|
|
|
Post by jj0 on Mar 8, 2020 19:43:09 GMT
Hi jj0, Thanks for your reply. You're right, I'm very impatient. But I want to start as soon as possible!! ;-P I tryed with OrangePi_pc_ubuntu_xenial_server_linux3.4.113_v1.0 image, but I can't umount /dev/mmcblk0p2. Could you help me? Many thanks, What's the error message you get? It could be that it is already unmounted in which case you can go ahead with the rest of the steps. |
|
|
|
Post by sharklodon on Mar 8, 2020 20:15:17 GMT
Hi jj0 , Thanks for your reply. You're right, I'm very impatient. But I want to start as soon as possible!! ;-P I tryed with OrangePi_pc_ubuntu_xenial_server_linux3.4.113_v1.0 image, but I can't umount /dev/mmcblk0p2. Could you help me? Many thanks, What's the error message you get? It could be that it is already unmounted in which case you can go ahead with the rest of the steps. This is the message:
root@OrangePi:/boot# umount /dev/mmcblk0p2 umount: /: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).)
And it's mounted:
root@OrangePi:/boot# e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.42.13 (17-May-2015)
/dev/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
Thanks,
|
|
|
|
Post by jj0 on Mar 8, 2020 21:05:05 GMT
What's the error message you get? It could be that it is already unmounted in which case you can go ahead with the rest of the steps. This is the message:
root@OrangePi:/boot# umount /dev/mmcblk0p2 umount: /: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).)
And it's mounted:
root@OrangePi:/boot# e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.42.13 (17-May-2015)
/dev/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
Thanks,
Have you booted from the sdcard on your Orange Pi? That would explain things. You have to do all the steps on a different device, or by booting the Orange Pi from a different sdcard. |
|
|
|
Post by sharklodon on Mar 8, 2020 22:38:42 GMT
This is the message:
root@OrangePi:/boot# umount /dev/mmcblk0p2 umount: /: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).)
And it's mounted:
root@OrangePi:/boot# e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.42.13 (17-May-2015)
/dev/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
Thanks,
Have you booted from the sdcard on your Orange Pi? That would explain things. You have to do all the steps on a different device, or by booting the Orange Pi from a different sdcard. Yes, I’m booting with the same sdcard that I’m trying to modify. I’ll try booting with another sdcard. Thanks a lot, |
|
|
|
Post by spannernick on Mar 9, 2020 14:47:01 GMT
If you don't have a nand on your Orange Pi PC H3(the Plus version has a nand) use a sd card reader to read the other sd card that your making the Maxi firmware on.
|
|
|
|
Post by spannernick on Mar 10, 2020 17:25:38 GMT
Have you booted from the sdcard on your Orange Pi? That would explain things. You have to do all the steps on a different device, or by booting the Orange Pi from a different sdcard. Yes, I’m booting with the same sdcard that I’m trying to modify. I’ll try booting with another sdcard. Thanks a lot, How did it go, did it work..? |
|
|
|
Post by sharklodon on Mar 11, 2020 21:10:01 GMT
Hi spannernick and jj0, Yes and no. Booting with another microsd, I've been able to copy nanda in boot partition (fat32) and I've extracted nandb to root partition (ext4), but I couldn't get it booted. I don't know how can I get into the u-boot prompt, for this reason, I tryed modifying uEnv.txt file or renaming nanda.bin file as uImage, but without exit. Example of uEnv.txt that I tried: bootargs=console=ttyS0,115200 disp.screen0_output_mode=EDID:1024x768p50 hdmi aload_script=fatload mmc 0 0x43000000 script.bin; aload_kernel=fatload mmc 0 0x48000000 nanda.bin;boota 0x48000000; uenvcmd=run aload_script aload_kernel Please, could you help me? Do you have any guide to know how can I get into the u-boot prompt? Many thanks, |
|
|
|
Post by jj0 on Mar 12, 2020 5:57:23 GMT
Hi spannernick and jj0 , Yes and no. Booting with another microsd, I've been able to copy nanda in boot partition (fat32) and I've extracted nandb to root partition (ext4), but I couldn't get it booted. I don't know how can I get into the u-boot prompt, for this reason, I tryed modifying uEnv.txt file or renaming nanda.bin file as uImage, but without exit. Example of uEnv.txt that I tried: bootargs=console=ttyS0,115200 disp.screen0_output_mode=EDID:1024x768p50 hdmi aload_script=fatload mmc 0 0x43000000 script.bin; aload_kernel=fatload mmc 0 0x48000000 nanda.bin;boota 0x48000000; uenvcmd=run aload_script aload_kernel Please, could you help me? Do you have any guide to know how can I get into the u-boot prompt? Many thanks, The commands you are using in your uEnv.txt are different from what I put in my earlier post, different load command and different addresses. Also instead of uenvcmd you need to use bootcmd I think. Also, how do you know whether the uEnv.txt is even used or not? <edit> I assume you are following the instructions from the OrangePi Wiki. This is fine, but then you need to install the u-boot-with-spl.bin (section 'Bootloader' on that page) from their instructions as well as it might be set up differently in how the kernel load scripts are setup. So you'd need to follow the instructions for 'B uilding UBOOT'. Which is great and you'll learn a lot but if you have hardly any Linux experience it might be a bit much. Best way is to get UART access so you can follow what's happening and change the settings. The UART pins are easily accessible, see linux-sunxi.org/Xunlong_Orange_Pi_PC. Of course I could also send you an u-boot-with-spl.bin that already has the right environment set up, but that would be cheating wouldn't it  . And even then UART access would be rather useful for troubleshooting. |
|
|
|
Post by sharklodon on Mar 13, 2020 19:43:49 GMT
Hi jj0, You are right and very smart!! ;-P I was trying to boot following the steps of Settingup without exit, because I don't have an USBTTL. I bought one from Aliexpress, but shipping process is very slow. Now, I created a boot.cmd file with the following: setenv boot_normal fatload mmc 0:1 0x43000000 script.bin;fatload mmc 0:1 0x40007800 nanda.bin;boota 0x400078000;mmc_root /dev/mmcblk0p2 And doing... mkimage -C none -A arm -T script -d boot.cmd boot.scr To generate boot.src file, but it doesn't boot yet. More ideas? Thanks and best regards, Shark |
|
|
|
Post by sharklodon on Mar 14, 2020 16:47:13 GMT
Hi jj0, I've continued trying and investigating... Without exit again!! With the boot.cmd that i put on my other post, it didn't boot, with a "boota unknown command" message, then I changed to bootz. Now script is running, but I get another error message: "SCRIPT FAILED".  boot.cmd -> boot.scr: setenv bootargs console=ttyS0 root=/dev/mmcblk0p1 rootwait panic=10 ${extra} fatload mmc 0:1 0x43000000 script.bin fatload mmc 0:1 0x40007800 nanda.bin bootz 0x400078000 Do you know where is the issue? Thanks and best regards, Shark |
|
|
|
Post by jj0 on Mar 14, 2020 19:37:12 GMT
Hi jj0 , I've continued trying and investigating... Without exit again!! With the boot.cmd that i put on my other post, it didn't boot, with a "boota unknown command" message, then I changed to bootz. Now script is running, but I get another error message: "SCRIPT FAILED". boot.cmd -> boot.scr: setenv bootargs console=ttyS0 root=/dev/mmcblk0p1 rootwait panic=10 ${extra} fatload mmc 0:1 0x43000000 script.bin fatload mmc 0:1 0x40007800 nanda.bin bootz 0x400078000 Do you know where is the issue? Thanks and best regards, Shark Ok, so at least you're making some progress. Also, in case you didn't do this already (i can't quite make it out from the picture), do have your OrangePi connected to a monitor/TV and do you see u-boot output on the monitor/TV? In that case you can connect a USB keyboard to the OrangePi and type in u-boot commands so you wouldn't need the UART. Regarding the proper boot command, nanda is an Android boot image. The right uboot command to unpack and boot it in 'older' u-boot versions was 'boota'. In newer uboot versions the 'boota' command was replaced and the functionality was incorporated in the 'bootm' command. However that functionality needs to be specifically enabled at uboot compile time and quite often it isn't. So you could try 'bootm' instead of 'bootz',as 'bootz' won't work'. Overall the commands should then be: setenv bootargs console=ttyS0 console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
fatload mmc 0:1 0x43000000 script.bin
fatload mmc 0:1 0x40007800 nanda.bin
bootm 0x400078000I do notice that your uboot version is 2017.09. The one that is on the image that I used (OrangePi_pc_debian_stretch_desktop_linux3.4.113, see my earlier step-by-step post) is 2011.09. That one still uses the 'boota' command. So you might try to use that exact image if 'bootm' doesn't work. If you use that image and follow the step-by-step instructions it should really work. |
|
|
|
Post by sharklodon on Mar 17, 2020 7:54:47 GMT
Hi jj0,
I don't see any progress. When I boot with u-boot v2017-09-dirty image, I can't run nanda. Modifiying boot.scr as your las post refered, nanda loads in memory but kernel doesn't start. setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
fatload mmc 0:1 0x43000000 script.bin
fatload mmc 0:1 0x40007800 nanda.bin
bootm 0x40007800
_
Installing OrangePi_pc_debian_stretch_desktop_linux3.4.113 as you recommends me, I don't have u-boot control, and I can't change boot options (remember that I don't have a USB UART yet).
How can I make a legacy u-boot with nanda support? I've checked sunxi reference manuals but it's not clear for me.
Many thanks, Shark
|
|
|
|
Post by jj0 on Mar 17, 2020 10:48:14 GMT
Hi jj0 , I don't see any progress. When I boot with u-boot v2017-09-dirty image, I can't run nanda. Modifiying boot.scr as your las post refered, nanda loads in memory but kernel doesn't start. setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
fatload mmc 0:1 0x43000000 script.bin
fatload mmc 0:1 0x40007800 nanda.bin
bootm 0x40007800
_
Installing OrangePi_pc_debian_stretch_desktop_linux3.4.113 as you recommends me, I don't have u-boot control, and I can't change boot options (remember that I don't have a USB UART yet).
How can I make a legacy u-boot with nanda support? I've checked sunxi reference manuals but it's not clear for me.
Many thanks, Shark
I still see progress, your u-boot v2017-09-dirty screenshots show that the 'bootm' command supports Android images. But probably the kernel in nanda.bin needs some additional settings to boot that are not needed with the legacy uboot: setenv machid 1029
setenv bootm_boot_mode sec
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
fatload mmc 0:1 0x43000000 script.bin
fatload mmc 0:1 0x40007800 nanda.bin
bootm 0x40007800
Or if you are feeling adventurous you can hexedit the OrangePi_pc_debian_stretch_desktop_linux3.4.113 image and change the uboot environment directly to match the required settings. Or if you fell less adventurous you can replace the environment (on the SD-card) with this env.bin (1.41 KB) one that I copied from my image: First check if the uboot environment is at the same place as mine: # echo `dd if=../OrangePiPC_C64Maxi.img bs=1 skip=17366980 count=25`
25+0 records in
25+0 records out
25 bytes copied, 0,000234257 s, 107 kB/s
bootcmd=nand read 5000000
If you see the 'bootcmd=nand read 5000000' then it's probably the same (this is the first text in the environment) so then replace it with mine: # dd if=env.bin of=/dev/mmcblk0 bs=1 skip=skip=17366980You have to rename your nanda.bin to nanda for it to work as that's the name I used. |
|
|
|
Post by sharklodon on Mar 17, 2020 20:13:43 GMT
Hi jj0, I tryed to modifiy boot.scr file as you proposed. Now, it seems that it boots ok but when the boot finishes, the screen apears completly in black. Then, I changed to install OrangePi_pc_ubuntu_xenial_desktop_linux3.4.113_v1.0.img with env.bin, and I got same issue, black screen. But in this case, I can't see the u-boot process.   At this moment, I feel very hopeless. Could you share your OrangePiPC_C64Maxi.img to check if the issue is in my image?
Many thanks, Shark |
|
|
|
Post by spannernick on Mar 24, 2020 12:57:08 GMT
Mine (THEC64 Maxi Pi) boots but shows only a black screen if it don't get enough power from USB power(I have mine connected to my PC via a USB HUB and forget sometime to plug its power supply in) so make sure its gets the right power otherwise it will not boot the Carousel and you think their something wrong with it (It properly does this on the real thing too if THEC64 Maxi is based on a H3 SoC, Has anyone dared to take of the heat sink yet on THEC64 Maxi Logic board or can you see what Soc it is from Linux..?)
|
|
|
|
Post by sharklodon on Mar 26, 2020 9:16:19 GMT
Hi spannernick and jj0, I booted my Orange Pi "Maxi" with jj0's image. I don't understand why with my Ubuntu legacy image I can't do it. These days I won't have enought time to try more things because I'm studying a Master. I'll keep you advised with my updates. Thanks and best regards, Shark |
|
|
|
Post by spannernick on Apr 2, 2020 18:54:13 GMT
Can anyone see the code on the memory chip on TheC64 Maxi Main board..?
|
|
|
|
Post by commodorelikebefore on May 28, 2020 11:52:20 GMT
I'm wondering, is it possible to add a audio output to the board? Or is it only thru' the HDMI? Also wondering about it, is it so similar to the Orange Pi does that not have video output also on the audio connection? Does that mean the C64 might be able to output to a rca/s-video signal?
|
|
|
|
Post by spannernick on Oct 5, 2020 18:22:13 GMT
I wonder what BGE stands for, its on the board before the build date.. ?
|
|
|
|
Post by spannernick on Oct 5, 2020 18:26:46 GMT
I'm wondering, is it possible to add a audio output to the board? Or is it only thru' the HDMI? Also wondering about it, is it so similar to the Orange Pi does that not have video output also on the audio connection? Does that mean the C64 might be able to output to a rca/s-video signal? I do not know, probably they removed all that when Koch Media redesigned the board for THEC64 Maxi/Capcom Home Arcade, have a look at the schematic of the OPIPC board. |
|
|
|
Post by spannernick on Oct 6, 2020 0:17:25 GMT
The Capcom Home Arcade has a USB Board in side it, it connects to the joysticks and buttons and then connects to the CHA Board, it uses the same USB chips from THEC64 MS Joystick.. "GH001" chips same as in the C64 MS Joystick, CHA has 8 buttons and one stick for one player and for two player, the same, THEC64 MS Joystick has one stick and 8 buttons too - 2 fire's, 2 triangle buttons and 4 buttons for A B C and Menu, TheC64 MS Joystick works on the CHA all buttons work but there are just in the wrong place, That why it works on the CHA, it shears components with the C64 Maxi... This is a picture of the Bluetooth board that you replace the USB Board in the CHA with but it uses the same "GH001" chips as THEC64 Micro Switch Joystick.  THEC64 Micro Switch Joystick and you can see "GH001" chip  |
|
. And even then UART access would be rather useful for troubleshooting.
