Author Topic: PAP KIII: Chinese PMP with Dingoo Software  (Read 20827 times)

rpgbeater

  • *
  • Posts: 11
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #30 on: October 24, 2017, 02:58:49 am »
Wait... so PAP KIII Plus is the newer model of PAP KIII.... but what is PAP KIIIS ?
Handhelds: GBC, GBA SP, DS, DSi, O3DS, N3DS Xl, PSP 3000, PSP Go, Dingoo A320, Dingoo A330, Gemei A330.

Consoles: Wii, PS3, 360.

nchaaa

  • Posts: 1
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #31 on: October 24, 2017, 10:59:41 am »
Hi everyone,

I purchased one of this PAPKIIIS and tried to reflash the FW with an updated one found on a youtube link.. Now the device does not even boot.

Does anyone can help me here ?

I am using SW like Win32DiskImager to write the SDcard of the device


dmitry_smagin

  • *
  • Posts: 420
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #32 on: October 24, 2017, 12:05:59 pm »
Kiii and K3S are not compatible on firmware level (they do on software though). KIII has jz4755 and 480x272 screen, and K3S has jz4760 soc and 800x480 screen.
You'll have to find an original firmware image, sorry for that.
GCW-Zero prototype, Dingoo a320, Ritmix rzx-50, Dingoo a380, Xperia Play

Jellyfish

  • *
  • Posts: 10
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #33 on: October 25, 2017, 12:55:35 am »
Found this link https://drive.google.com/file/d/0B-ww3BA7Ea62RVNBWGdNUVA4SUk/view shared by a guy named Matt Larose on youtube at https://www.youtube.com/watch?v=z84FyAnq8U4. I haven't downloaded it myself 'cause it would be pretty much useless to me. The comment says it is a 'newer' firmware for the PAP KIII device.
Good luck gentlemen and ladies  ;)

Update: Unfortunately I have been unable to mess with mine (it just came earlier today) due to my inabilty to locate a Windows 10 compatible USB driver.
« Last Edit: October 25, 2017, 06:47:19 am by Jellyfish »

dmitry_smagin

  • *
  • Posts: 420
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #34 on: October 25, 2017, 09:17:38 am »
Update: Unfortunately I have been unable to mess with mine (it just came earlier today) due to my inabilty to locate a Windows 10 compatible USB driver.

The link above is for internal sd-card, you don't need a usb driver. Insert this card to your laptop and write the image directly to it.
GCW-Zero prototype, Dingoo a320, Ritmix rzx-50, Dingoo a380, Xperia Play

Jellyfish

  • *
  • Posts: 10
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #35 on: October 26, 2017, 02:04:22 am »
Did that. Popping in the firmware-flashed SD and booting it up has no visible effect.
What now?

Jack83

  • *
  • Posts: 91
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #36 on: October 30, 2017, 09:54:31 am »
I just ordered a "PAP KIII" and got a "PAP KIIIS" in a "PAP KIII Plus" package :'( The new screen of the KIIIS is really bad and the emulators run either in a tiny window or streched to 16:9 fullscreen. Argh!
I made a backup of internal sd card and can upload the image if someone is interested.

Tools like the dinguxcommander http://beyondds.free.fr/index.php?Dingoo-dinguxcommander do work and I looked around. There are scripts to put the display in a "a320" mode. This results either in a stretched image or the small in the middle, meaning this function is not part of the emulators. I tried to exchange the build in emulators with other versions, but the partition is mounted read-only. Is there any way around that? Is it possible to access the running device from a PC? I would like to poke around  ;D

SashaX

  • *
  • Posts: 14
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #37 on: October 31, 2017, 05:39:26 pm »
I have the PAP KIII PLUS.
Its possible to run emulators of the dingoo A380 then? Or to flash te PAP to a Dingoo A380?

Im new at it, the gadget arrived today.

Best regards

algorithm

  • *
  • Posts: 99
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #38 on: November 01, 2017, 12:04:59 am »
Right, I decide to order this device a few days ago from amazon..    https://www.amazon.co.uk/gp/product/B072ZP9HMY/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

According to the screenshots, it seemed to be the Pap Kiii Plus.   When it arrived, here are the pictures of the box and manual..




Could it be a Pap III plus?  Lets see..





According to a few other forums which I had visited, it seems to match the firmware that's on some of the PAPKIII Plus devices so all seems well.   However, I decided to open up the device and below are the findings.


Battery is removable and the high capacity variant so all is well here..


CPU is the Jz4760 which is used on both the Pap KIII Plus and Pap KIIIS.. We know that the above is definitely not a standard Pap KIII


And what do we have here?   Motherboard markings showing PAP_K3S_V3_DDR_V2.0....
So it seems as if it is really a PAPK3S but using some modified firmware that's usually available for the PAP KIIIPlus (Super Game Firmware LN430)

Now time for some of my other findings.

On some PAPKIII devices, you can update the firmware by placing specific files on the root of the SD, then going into system settings and updating.   This model does not allow this.   

However, it is possible to boot the Device into Bootloader/Flash mode by the following..

Turn off device.  Remove its connection from PC (USB).
Connect USB
Hold Down Start Key and Hold down the power button for a few seconds.
Windows should detect and install the drivers.   (On my windows 10 machine, it seems to have automatically loaded the JZ4760 Boot driver, but on second attempt I had to disable device signing on windows and point it to the JZ4755 boot driver (Found with the Ingenix Flash tools).    I attempted to flash the RZX 50 firmware to it (I knew it wont work, just wanted to see if it would flash, but to no avail)

Ofcourse I made a backup of the MicroSD card in the device.  It seems pretty much like a raspberry PI in that the whole firmware is on the MicroSD.  (As long as you have made a backup with win32diskimager or similar, the device should be able to recover from a brick by writing this backup back to the microsd)

Ofcourse new firmware can also be written by obtaining or creating images that can be written to microsd too.

In order to view file contents on Windows 10 (Roms etc) many people have had some issues.    The solution that works 100% is to do the following

Turn device off and unplug from usb.
Plug it back to usb
Then turn on the handheld.   After a few seconds, it will detect and allow you to view the contents of the Fat32 Partition.

I have also experimented in running opendingux applications (With the .dge extension)  Some run well no issue  (E.g Atari Lynx Emulator and Vice (C64 Emulator)

There are a few that run in a smaller screen size which also then brings me to the point of the screen resolution of this device..  If it is a Pap KIIIS, It would have 800x480 resolution or similar..    For the 320x240 dingoo apps which do not scale,  it filles 2/3rds of the screen horizontally  (320 pixels on a 480 pixel viewport?)  which may indicate that the resolution of my device is actually 480x272 (Which then would indicate its not a PAP KIIIS?)

For the Price, Cant really complain.  Gameboy advance games seem to run pretty well on it actually.   I have found issues with audio grating (Maybe audio buffer size too small?).    Unfortunately even in pixel perfect mode (1:1) it does not seem to give silky smooth scrolling  (Regardless if its via TV-Out or built in screen).  I Know some handhelds have unusual screen hz rates (57hz etc).

.APP files do not seem to run on this firmware.  (Would have been nice to try out 7 days and some 3d games on it, but nothing at the moment..)


« Last Edit: November 01, 2017, 12:11:03 am by algorithm »

dmitry_smagin

  • *
  • Posts: 420
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #39 on: November 01, 2017, 12:50:02 pm »
Thanks for the photos, @algorithm, very informative!
The screen is indeed 480x272, hence the model is K3 plus and not K3S. The pcb is the same for both models, however (why not?). K3S has additional frame around the screen like here: https://ru.aliexpress.com/item/3-5-Portable-Handheld-Game-Console-64BIT-PAP-KIIIS-Games-Perfectly-support-CP-GBA-format-games/32809608119.html

The question remains, how much ram it has? Most probably 64Mb but 128Mb also possible.

Could you run an attached file dmesg.txt (rename it to dmesg.dge before)? It will dump dmesg output to log.txt. Could you post its contents on pastebin.com ?
GCW-Zero prototype, Dingoo a320, Ritmix rzx-50, Dingoo a380, Xperia Play

Jack83

  • *
  • Posts: 91
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #40 on: November 01, 2017, 04:33:31 pm »
Hey @algorithm,
nice findings. It seems you got the same device as me. I executed demesg and I add the info from my device.
Mounting the appfs rw was quite easy with "/bin/mount -o remount,rw /dev/mmcblk0p2 /usr/mtdblock3"
and I managed to change some of the default emulators. The emulator dge can simply be replaced with a script with the same name.

I downloaded a "local pack" from http://dingoo.a320.free.fr/local-pack-opendingux.php and all games and some emulators are running. The dge of most games has to be started trough dinguxcommander to work. Its quite fun to play Doom and Duke3D on the device.

Executing "echo 1 > /proc/jz/lcd_a320" will put the video output into the center.

I tried to fire up the old toolchain for opendingux to compile dmenu for the higher res display, but it seems that I'm a little late to the party and the sources can not be compiled without problems on newer systems without problems.
Compiling worked at the end, but without a terminal its hard to say why it crashes/does only display a black screen.

Is it possible to use the "usb network" I read about in the context on opendingux on this device? I could not find any guide to set it up or if its possible.

Code: [Select]
Linux version 2.6.31.3 ([email protected]) (gcc version 4.3.3 (GCC) ) #64 Fri Feb 17 17:20:13 CST 2017
Jz47XX Floating coprocessor work on 32*32bit mode
console [early0] enabled
CPU revision is: 2ed0024f (Ingenic JZRISC)
FPU revision is: 00770100
CPU clock: 528MHz, System clock: 264MHz, Peripheral clock: 132MHz, Memory clock: 132MHz
JZ4760 Lepus board setup
Power Management for JZ
Determined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
User-defined physical RAM map:
 memory: 08000000 @ 00000000 (usable)
Zone PFN ranges:
  Normal   0x00000000 -> 0x00008000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00008000
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat 8044a400, node_mem_map 81000000
  Normal zone: 256 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 32512
Kernel command line: mem=128M console=ttyS1,57600n8 ip=off rootfstype=ext3 root=/dev/mmcblk0p1 ro
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
Memory: 125056k/131072k available (2937k kernel code, 5840k reserved, 1397k data, 156k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:256
Console: colour dummy device 80x25
console handover: boot [early0] -> real [ttyS1]
Calibrating delay loop... 421.06 BogoMIPS (lpj=2105344)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
jz_platform_init
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
jz_i2c0 jz_i2c0.0: JZ4760 i2c bus driver.
jz_i2c1 jz_i2c1.1: JZ4760 i2c bus driver.
mmc0: No card detect facilities available
mmc0: new high speed SDHC card at address aaaa
JZ mmc0 driver registered
mmc1: new high speed SDHC card at address 0007
JZ mmc1 driver registered
musb_hdrc: version 6.0, pio, otg (peripheral+host), debug=0
jz4760: Normal mode.
do_otg_id_pin_state: id pin val 0
******* jz_musb_set_vbus:189 DEV
jz_musb_set_vbus:OTG_ID=1
jz4760: Disable USB PHY.
musb_hdrc: ConfigData=0x12 (UTMI-8, HB-ISO Rx, SoftConn)
musb_hdrc: MHDRC RTL version 2.0
jz_vbus_hotplug: Registered.
musb_hdrc musb_hdrc.0: USB OTG mode controller at b3440000 using PIO, IRQ 21
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
Total 8MB memory at 0x4800000 was reserved for IPU
Total 8MB memory1 at 0x5000000 was reserved for IPU
Total 8MB memory2 at 0x5800000 was reserved for IPU
fuse init (API version 7.12)
msgmni has been set to 244
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler cfq registered (default)

 43CPT80-40 REST ...
jz4760fb_map_smem 720 573
jz4760fb_map_smem 720 573
page count is 9
LCDC: PixClock:12000000
fb0: jz-lcd frame buffer device, using 2048K of video memory

 43CPT80-40 lcd ...
JZ4760: Char device core registered.
init rda5807p
JZ4760b SAR-ADC driver registered
JZ4760: Virtual Driver of TCSM registered.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS1 at MMIO 0x0 (irq = 4) is a 16550A
brd: module loaded
loop: module loaded


gc0309 i2c init

gc0309_power_down


 my704 i2c init

hi704_power_down
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
first get battery value is 4160
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
usbmon: debugfs is not available
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008
g_file_storage gadget: Number of LUNs=2
jz4760: Disable USB PHY.
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.31.3 musb-hcd
usb usb1: SerialNumber: musb_hdrc.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
jz4760: Enable USB PHY.
jz-gpio-keys: scan interval 20ms
input: JZ GPIO keys as /class/input/input0
drivers/input/keyboard/common_wireless_pad.c 601 elan_pad_init
kernel : keypad register success!
i2c /dev entries driver
mmcblk0: mmc0:aaaa SU04G 3.69 GiB
 mmcblk0: p1 p2 p3 p4
mmcblk1: mmc1:0007 SD16G 14.4 GiB
 mmcblk1: p1
=====>enter init_dlv
register codec 8025bac0
===>enter init_jz_i2s
JZ I2S OSS audio driver initialized
TCP cubic registered
NET: Registered protocol family 17
scan sensor:gc0309
gc0309_power_up
---- gc0309 read is 160
gc0309_power_down
scan sensor:hi704
gc0309_power_down
hi704--- ------------------------------------------hi704_sensor_probe

hi704_power_up
Read i2c device 0x30, nack or abort, ret=-1
hi704--- ---------------------------hi704 sensor read is 255
hi704_power_down
now we has:
gc0309_power_down
sensor_name:gc0309 id:0
default is gc0309
CIM--- get new page!
CIM--- get_max_mem_size
CIM--- preview size = 600KB
CIM--- capture size = 600KB
mem_size=3600K
order=10
jz cim preview info vaddr = 0x86000000 paddr = 0x6000000 mem_size = 0x384000
Virtual Driver of JZ CIM registered
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly on device 179:1.
Freeing unused kernel memory: 156k freed
Warning: unable to open an initial console.
no hp sound/oss/jz4760_dlv.c 1965 hp_ack_timer
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on mmcblk0p3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
JZ DLV: Close REPLAY
volume is 3
JZ DLV: Close REPLAY




algorithm

  • *
  • Posts: 99
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #41 on: November 01, 2017, 06:59:16 pm »
I ran the dmesg.dge file (text file renamed to dge to enable the script to run) and the log file created seems identical to your one (Attached)

One more thing to note is that its possible to also stretch the display to use the full size of the 480x272 (Instead of having the opendingux games in 320x200 non scaled) by the following..

#!/bin/sh
echo 2 > /proc/jz/lcd_a320

This script is also inside the dmenu folder called "A320_zoom_in.sh",  there are also some other scripts there too.  (I noticed there is also an update folder somewhere on the device

Note that the display settings are persistant (thankfully) until reboot.  However running other scripts for the display zoom in/out after running one previously seemed to corrupt the display until it was rebooted again

There are a few programs that use the native 480x272 screen.   Those that I have tried that have worked is the Atari lynx handy emulator as well as the Vice (C64) emulator - For vice, you would need to select 480x272 (enter it under display settings in the vice menu)

One other note.. Is it possible that the PAPKIIIS motherboard is identical to the PAPKIIIPlus, only with a 800x480 screen and different firmware  (Motherboard markings show PAPK3S on my device)  Seems the firmware I saw on a few youtube videos used another menu system for rom selection for the PAPK3S


« Last Edit: November 01, 2017, 07:07:10 pm by algorithm »

algorithm

  • *
  • Posts: 99
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #42 on: November 01, 2017, 10:57:58 pm »
One other thing I found is that its possible to flash within the device using the update tool

You need the following files

appfs.ext3
configfs.ext3
mbr-uboot-msc.bin
rootfs.ext3
uimage

place them on the root of the microsd

then run dingoocommander and go into the /boot/local/apps/ folder

execute the update tool.

It will then flash the above files and if everything goes well, will mention that 5 files have been successfully flashed and to press reset to continue

Ofcourse the flash resulted in a brick (as I was using a ritmix rzx dump) I guess it could not initialise the components as they differ (e.g lcd etc)

Thankfully the device is unbrickable, so will put the original 4gb sd image back on






dmitry_smagin

  • *
  • Posts: 420
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #43 on: November 02, 2017, 07:52:58 am »
Thanks for the info.
So, it's confirmed that pap kiii plus has jz4760 at 528MHz with 128Mb of RAM, 480x272 lcd and legacy dingux inside.

Good news:
you can use it as a replacement for a320/a380/rzx50 as it's software compatible
it's slightly faster than a320 (408-420MHz max overclocked) and a380/rzx50 (432Mhz) and has more RAM (vital for mame and fba emulators)

Bad news:
jz4760's new features are not used (mips32r2 hardfloat and new ipu)
with proper firmware it could be made gcw-zero compatible on software level (except open gl es), but alas, there's no one to try
GCW-Zero prototype, Dingoo a320, Ritmix rzx-50, Dingoo a380, Xperia Play

djlunchbox

  • Posts: 2
Re: PAP KIII: Chinese PMP with Dingoo Software
« Reply #44 on: November 06, 2017, 11:13:12 pm »
Hello,

So i've purchased one similar to the one algorithm posted. So far i love it. I've been able to load games via SD card slot and adding ROMs myself. So far it's great. I didn't know how to make other neo geo games work because i didn't know what .FBA extension was but have since found where to convert my ZIP files to FBA.

So it seems to be able to handle CPS and CPS II games well but has anyone tried CPS3 or any MAME roms that I guess can be played via FB Alpha since I think that's the emulator? Also how about anything above Samurai Showdown 2? I'm planning to convert some ROMS from my raspberry pi to see about playing them here but if anyone has tried please let me know. I'm also going to wipe the card and load only games i want as well as replace some suspect ROMS as well as ROMS from CPS/NeOGeO i do not play to free up memory and add more Master System and game gear ROMS.

I'm not well versed in all the programming stuff but can anyone do a very newb explanation on how to possibly change the emulators to make it work better? or if someone can make a new image of the SD card with better emulators? The GB one seems to cause a crackling noise.

Also can the screen be swapped out? mine has a vertical line running on the left side of it. It's not bad but wondering if the swap is easy and what screen i can use? Thanks for any help!

 

Post a new topic