Author Topic: Dingoo A-380 Custom Firmware V2.11.09 "RetroDD" (Read 326247 times)

JammyDoger · « **Reply #600 on:** August 04, 2013, 01:59:47 pm »

Quote from: Alien Grey on August 03, 2013, 08:04:02 pm

VMLinux -> Dingux then press the A button.

It should boot the factory kernel. To go back to the Exmortis kernel select Reboot and press the A button.

That's it.

Ah ha, I get it now, don't know what was wrong with the Nintendo emulator but it seems fine now, must have just been something random.

Thanks for the help and keep up the good work

Alien Grey · « **Reply #601 on:** August 11, 2013, 05:34:56 pm »

It looks like I did screw up after all with the vmlinux files. It was the wrong kernel.

This is the right one and makes it possible to boot the factory: http://www.putlocker.com/file/6168FA626450714F

I'm sorry. I'm going to fix this in the emulator pack.

Note: Everyone who updated his Dingoo A-380 with CFW V2.09.02 "Exmortiis" before this post should replace the vmlinux files on his external MicroSD card with the files from this archive or it won't boot the factory kernel. Without the factory kernel you can't use the factory CPS1, CPS2, NEO-GEO and FinalBurn Alpha emulator and charging the battery is going to take twice as long.

Girl · « **Reply #602 on:** August 16, 2013, 06:37:45 pm »

Quote from: Alien Grey on August 11, 2013, 05:34:56 pm

It looks like I did screw up after all with the vmlinux files. It was the wrong kernel.

will this kernel work with the prototype A-380s ? The A380s that were sold very early to a few people and have different kernels than the normal A-380

if not ..

Quote from: Alien Grey on August 11, 2013, 05:34:56 pm

Everyone who updated his or her Dingoo A-380 with CFW V2.09.02 "Exmortiis" before this post should replace the vmlinux files on his or her external MicroSD card with the files from this archive or it won't boot the factory kernel.

if the vmlinux files you are telling people to update to does not work with prototype A-380s , would the "wrong" kernel, that takes twice as long to recharge, work with prototype A380 ?

sorry if this has been answered already, i'm just scared to upgrade because i've read the kernels are different in the older prototype A-380 handhelds

thank you so much for this custom firmware by the way you have helped bunches of people

dmitry_smagin · « **Reply #603 on:** August 16, 2013, 07:51:01 pm »

No, this firmware will not work on prototype which had nand-chip inside instead of later sd-cards. Nand-chip requires different kernel.

Alien Grey · « **Reply #604 on:** August 17, 2013, 01:02:20 pm »

Maybe a dual boot with the Dingoo A-320e Dingux firmware can be used on these prototypes. You shouldn't try it out without the original firmware files. You're going to need them as a backup to unbrick the console if it doesn't work.

Girl · « **Reply #605 on:** August 17, 2013, 04:34:27 pm »

aw bad news, well the reason i asked was because DingooLover directed me to your custom firmware

see?

Quote from: dingoolover on August 15, 2013, 09:03:57 pm

use this:

works like a dream

he might have misunderstood, or skipped over that i was asking about firmwares that work on the prototype models.. but hopefully there is a way to make it work on prototype versions like Alien Grey said

Quote from: Alien Grey on August 17, 2013, 01:02:20 pm

You shouldn't try it out without the original firmware files. You're going to need them

how do i get these original files ? do i just hook up the device to a PC and drag all of the A-380's folders somewhere safe? and if the device bricks, do i just remove the Dingux files from the device and drag the backed up files to the device again?

thank you so much i hope there's a way, ahhh ! i want to use your custom firmware like everyone else lol no fair!

Alien Grey · « **Reply #606 on:** August 17, 2013, 06:42:37 pm »

The manufacturer should release the firmware files and flashing tools.

It's possible that it works with the Dingoo A-320e flashing tools but you still need the firmware files to recover from a bad flash.

Alien Grey · « **Reply #607 on:** December 01, 2013, 02:59:25 pm »

I'm going to make some changes to the CFW to make it possible to start the emulators on the external MicroSD from dmenu.

I've currently added Atari 2600, Atari 7800, PC Engine, MAME and PSX.

What else should be added that you would like to start from dmenu?

AtariHERO · « **Reply #608 on:** December 02, 2013, 02:12:01 am »

Atari 8 / 5200 is a must too
Also we must wait for a probable Temper port

Alien Grey · « **Reply #609 on:** December 02, 2013, 06:55:27 am »

If there's going to be a Temper port than all I need to know is the folder and binary name.

We don't need to wait for that if we change the folder and binary name from dingux-hugo to those of Temper. We just need Slaanesh to confirm that there's going to be a Temper port.

Anyway I'm going to try to make submenus and add all the external emulators to dmenu. SDL Emulators has now been changed to CFW Emulators. SDL Games has been removed because it's no longer needed with the new kernel.

slaanesh · « **Reply #610 on:** December 02, 2013, 08:03:29 pm »

I'm not planning on a Temper port at the moment, as after the MAME4ALL port for A380 I'm doing MAME4ALL for GCW0.

Now about the A380:

Is Dingux addressing the full 64MB? Or is that 2nd 32MB useless?
With 64MB, Mortal Kombat should be working, however I am getting out of memory errors.
Also, is there a swap file? Can we enable that through the CFW?

AtariHERO · « **Reply #611 on:** December 02, 2013, 10:58:09 pm »

Quote from: slaanesh on December 02, 2013, 08:03:29 pm

I'm not planning on a Temper port at the moment, as after the MAME4ALL port for A380 I'm doing MAME4ALL for GCW0.

Now about the A380:

Is Dingux addressing the full 64MB? Or is that 2nd 32MB useless?
With 64MB, Mortal Kombat should be working, however I am getting out of memory errors.
Also, is there a swap file? Can we enable that through the CFW?

ds_magin implemented swap / vmemory tricks on Sdl Fba, larger than 64 mb games work

slaanesh · « **Reply #612 on:** December 02, 2013, 11:20:38 pm »

I've done the same now... Enabling a swapfile.

However, can anyone answer if A380 Dingux actually uses the entire 64MB ram?

slaanesh · « **Reply #613 on:** December 03, 2013, 04:16:10 am »

Also is there any chance of adding an option to enabled TELNET and FTP?
Ie. Switch between USB Driver and TELNET/FTP - that would be super handy for development.
Getting a telnet to the machine would make it awesome!

The software to do this - I assume - must already be there? ie. A320 Dingux can do this.

dmitry_smagin · « **Reply #614 on:** December 03, 2013, 04:45:05 am »

Quote from: slaanesh on December 02, 2013, 11:20:38 pm

I've done the same now... Enabling a swapfile.

However, can anyone answer if A380 Dingux actually uses the entire 64MB ram?

Dingoo a380 uses full 64Mb. In case with FBA, sometimes it needs more ram for unzipping. I'd recommend replacing all malloc() to a wrapper function which uses memory mmap'ed earlier. See here: https://github.com/dmitrysmagin/fba-a320/blob/master/src/sdl-dingux/cache.cpp
These routines are modified from gp2x version which has a weird memory layout (upper uncached 32mb are not visible to the kernel). You know that better than me probably.

As for telnet/ssh, there's no problem enabling usb-gadget driver module while compiling the kernel. I just didn't test this feature, because I used uart for debugging.

Alien Grey · « **Reply #615 on:** December 03, 2013, 07:18:32 am »

Houston, we've got a problem.

We've got to many emulators to add to dmenu that it doesn't load it anymore.

There's probably to many items for one submenu. It won't be possible to start OhBoy, dingux-np2 and VMUDingoo from dmenu. If this is a problem than they can still be added but than others have to be removed.

Alien Grey · « **Reply #616 on:** December 03, 2013, 08:27:55 am »

Quote from: d_smagin on December 03, 2013, 04:45:05 am

As for telnet/ssh, there's no problem enabling usb-gadget driver module while compiling the kernel. I just didn't test this feature, because I used uart for debugging.

How do you enable it?

If it makes it easier for debugging and it's possible to add this feature than why not add it for the next CFW release?

slaanesh · « **Reply #617 on:** December 03, 2013, 09:14:27 am »

I have an easier method still, using a swapfile.

for example to start mame i use the following script:

Code: [Select]

if [ ! -e ./swapfile ]; then
    dd if=/dev/zero of=./swapfile bs=1024 count=65536
fi
mkswap ./swapfile
swapon ./swapfile
exec ./mame.dge

Do you use "buildroot" to make the kernel?

dmitry_smagin · « **Reply #618 on:** December 03, 2013, 09:38:10 am »

No, I build kernel separately from here:
https://github.com/dmitrysmagin/a380_kernel, branch: jz-2.6.32

I don't remember for sure, but these two options must be on (=m) to enable serial over usb
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_SERIAL is not set

It was real pain to upgrade from 2.6.24 to 2.6.32, because it's a really dirty chinese code. In fact, everything should be redone from scratch, but I don't have much time and will to go on with kernel right now.

Thanks for the hint with system swap. It seems I reinvented the bicycle.

Btw, even with swap some encrypted roms (mslug3&4) won't start because it takes forever to uncrypt because of the swap.

slaanesh · « **Reply #619 on:** December 03, 2013, 10:11:46 am »

Is there no way to increase the CPU speed? I have been looking at the kernel code, specifically:

https://github.com/dmitrysmagin/a380_kernel/blob/jz-2.6.32/arch/mips/jz4750d/cpufreq.c

The maximum clock seems to be set from u-boot. Can this be some how tweaked or configurable from the outside world?

Author Topic: Dingoo A-380 Custom Firmware V2.11.09 "RetroDD" (Read 326247 times)

Alien Grey (OP)

Alien Grey (OP)

Alien Grey (OP)

Alien Grey (OP)

Alien Grey (OP)

Alien Grey (OP)

Alien Grey (OP)