[X]Assistant

[Redscorpio]

SoChip 8600/9800 device firmware

The topic discusses the issues of creating and modifying firmware on SoChip 8600/9800 devices and their analogues

Now the market has a lot of devices built on the basis of SoChip 8600/9800 and their analogues (e-books, mobile and stationary portable players). Unfortunately, the manufacturer did not open the SDK and the firmware of these devices is a “black box”. It is proposed in this topic to jointly collect information and develop techniques that will improve the firmware.
!!! AvailableDiPal SDK !!!

I. Attention. Important information for "experimenters"

1.If the device does not show signs of life after flashing or is cyclically overloaded (does not want to flash), do not panic:
- Instruction 1
- Instruction 2
- Instruction 3
2.It is strongly not recommended for repacking disk images to useWinimage. This may lead to the inoperability of the firmware. Use for exampleUltraISO. But it is most preferable to use the program.dragonfrom the "utility manufacturer" kit (see "Tools")
3.If you have problems with the firmware of your device and you want to use the help of members of the forum, use the programDebugview

Losber @ 12/10/2011, 17:46

Download DebugView and run it, let it work. Flush LiveSuit with a problem repackaged firmware, you get an error. Then go to the program DebugView, save to the file what happened and attach it in the message on the forum.

Ii. Analogs

SoChip SC8600 == BoxChip F15 == Teclast T7200
SoChip SC9800 == BoxChip F10 == Teclast T8100

Iii. Information- links to posts in the topic

1.Specifications:
1.1 SoChip SC9800 Specification
1.2 F16 Specification
1.3 F20 Specification
2.Core guideARM926EJ-S
3. Firmware file structure(further links)
4. The sequence of the start of the device
5. Work with language resources
6. "Student Computer" (H3 / H5)
7. Answers on questions:
- What is the core?
- What OS?
- Is it possible to install Android?
Once again about Android, againandstill
8. Instructions for beginners
9. Assigning drivers and system files in firmware
10. BMP file format in resource file
11. Reassigning device buttons in the keyboard driver
12. Reassigning the remote control buttons in the keyboard driver
13.Replacing drivers in firmware(1)and(2)
14. Instructions for editing executable files to run on another firmware
15. Abandoned project for SC8600 with sources
16. DWARF
17.Device diagrams(1), (2)and(3)
18. Samples of firmware demonstrating wits252 UI SDK
19. Identification of ARM chips
20.Sources of games for our devices(1), (2)and(3)
21. How to change Cyrillic text in applications.

III +. Additional Information

1. UCos GUI (?) Sources
2. UCos GUI SDK
3. BoxChip A10 processor sdk
4. Allwinner A10 Specification and Additional Information

Iv. Instruments- links to posts in the topic

1. A set of utilities from the manufacturer
- Instruction 1
- Instruction 2(creaturerootfs)
- Instruction 3(creatureramdisk.iso)
2. Sdkby dipal
3. imgRePacker- LiveSuit firmware unpacker / packager (* .img)
4. imgDecoder- decryptor / encryptor of LiveSuit firmware (* .img)
5. Program to facilitate editing touchtheme.bin
6. Building utilities for working with firmware
7. Original (Chinese) assembly of SoChip Modding Tools

Additions

7.1Alternativeazxmagic_add.exefromFlasher-11
7.2Alternativeazxmagic_del.exefromFlasher-11
7.3Alternativeverify_corr.exefromFlasher-11
7.4 GUIfromlosber

8. unPackerfromnullpix
9. GNU_readELF- tool for parsing ELF character information
10. AXF_beautification_tool- utility for working with graphic resources (in some * .axf and * .bin files)
11. PhoenixPro- A utility that allows you to simultaneously flash up to 127 devices (no more than 7 is recommended). As stated, when working simultaneously with 7 devices, firmware of about 100MB in size is loaded in 10s (the key is inside the archive).Again
12. Phoenixcard- utility to prepare microSD for automatic firmware.One more time withinstruction
13. LiveSuitin a convenient "package".Again
14. Drivers(32 and 64 bits) andagain
15. ARMu- A tool to view and edit the ARM binaries
16. SCelfAutoPatcher- program for automatic correction of addresses of imported functions in executable files (* .axf)
17. SYMTAB_extractor- program for extracting symbolic information from executable files (ELF)

V. Programs for devices on SC8600 / 9800 - links to messages in the topic

1. Game Console EmulatorSegafromDipal.
- Game collections(1)and(2)
2. Reg converter<->inifromlosber

Vi. useful links

1.Products webpageSoChip(eng.)
2.Products webpageSoChip(whale.)
3.Products webpageALLWINNER TECHNOLOGY(whale.)
4.Allwinner Pageon ARM website
5.Related forum onpleer.ru
6.Just interesting links fromlosber

VII. Profile Topics

1. Effire ColorBook TR401
2. Effire ColorBook TR701
3. iconBIT HDB700LED
4. iconBIT HMP705HDMI
5. Lexand LT-115
6. Lexand LT-117
7. Ritmix RBK-430
8. Ritmix RBK-450
9. Ritmix RBK-470
10. Ritmix RP-400HD
11. Ritmix RP-430HD
12. Ritmix RP-500HD
13. Nexx NRM-51 LED
14. Teclast TL-C700
15. teXet TB-431HD
16. teXet TB-710HD
17. teXet TB-740HD
18. Wexler Book T7005

Please note:
1. Before asking questionsread the topic content(especially with messages on the links in the header)
2. Here are discussedgeneral questions onlycreate and modify firmware. For firmware specific devices, please contact the relevant forum topics.
3. Any useful information is welcome (will be filtered).
_"Cleaners"

Post has been editedRedscorpio - 17.03.13, 17:54

[- = Alex2 = -]

RedScorpio,
It is also in the archive, again

Attached files

OK - F02231414314A_Q101 + PhoenixCard.rar(13.67 MB)

[Redscorpio]

- = Alex2 = - @ 06/29/17, 17:48

OK - F02231414314A_Q101 + PhoenixCard

Firmware (old) format LiveSuit, such a utility PhoenixSuit "does not eat" (in such firmware a lot of encryption, work with which, apparently, "thrown" from the utility).
Use the LiveSuit utility

- = Alex2 = - @ 28.06.17, 09:18

LZ_F23_Q101 (2) -OK.img (4.59 MB)

Accordingly, the opposite situation - firmware (new) format PhoenixSuit. Most likely, the PhoenixCard utility does not "eat" such firmware.

I draw your attention to the fact that the theme is called "Firmware devices on the SoChip 8600/9800", and they (were) of the LiveSuit format (that is, the tools for them have always been the utilities LiveSuit and PhoenixCard).
I used to work with the firmware of a new generation only for imgRePacker (i.e. I did only unpacking / packing, without having such devices on hand).

Ps. It is surprising that different generations of firmware are used for one device.

[- = Alex2 = -]

So you can do this so that this firmware from phoenixsuite could be pushed into phoenixcard and made a firmware card?

[Redscorpio]

- = Alex2 = -,
Once again - there are no firmware for PhoenixSuit and for PhoenixCard

[vinni303]

Hello, I have been sitting for half a day. There is a GLOBEX Gu803T, I can’t find the firmware on it and the info itself, how can someone help me and stick my finger where it is. I will be very grateful. thank

[vadeus]

vinni303,
Effire ColorBook TR701 - Firmware (Post Vovanchikus # 36607481)

[vadeus]

palmel89,
Moved toNoname

[Alex19911607]

Guys. Urgently need help !!! There is a tape recorder mystery mdd 7100 after unsuccessful flashing from a flash drive a white screen and that's it. Can I flash it somehow?

[vadeus]

Alex19911607,
In the cap is the first spoiler.

[Makoto9505]

People help, you need firmware on hamy 4. Everything that I have already tried, is not sewn.
Here is the firmware log

[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end
[1728] IN 1
[1728] PnpFelIn current m_tools_if is NULL
[1728] itemLen = 13187.
[1728] ================= sys_config =================
[1728] dram->reallen = 0x8000
[1728] ——— sys_config ———
[1728] sys_config_t_size = 0x1364
[1728] version = 0x100
[1728] magic = 20090319
[1728]
[1728] magic = SYS_PARA
[1728] ver = 256
[1728] enable_erase_nand = 0
[1728] enable_jtag = 0
[1728] ————— epos_para —————
[1728] chip = 0
[1728] pid = 0
[1728] sid = 0
[1728] bid = 0
[1728] target.debugenable = 0
[1728] usrcfg [0] = 0
[1728] usrcfg [1] = 0
[1728] usrcfg [2] = 0
[1728] usrcfg [3] = 0
[1728] usrcfg [4] = 0
[1728] usrcfg [5] = 0
[1728] usrcfg [6] = 0
[1728] usrcfg [7] = 0
[1728] usrcfg [8] = 0
[1728] usrcfg [9] = 0
[1728] usrcfg [10] = 0
[1728] usrcfg [11] = 0
[1728] usrcfg [12] = 0
[1728] usrcfg [13] = 0
[1728] usrcfg [14] = 0
[1728] usrcfg [15] = -2147483648
[1728]
[1728] ————- dram_para ——————
[1728] base = 0x80000000
[1728] size = 64
[1728] clk = 120
[1728] access_mode = 0
[1728] cs_num = 1
[1728] ddr8_remap = 0
[1728]
[1728] sdr_ddr = 1
[1728] bwidth = 16
[1728] col_width = 10
[1728] row_width = 13
[1728] bank_size = 4
[1728] cas = 3
[1728]
[1728] p1_para->Battery_cap = 2200
[1728] p1_para->Discharge_current_rate = 0
[1728]
[1728]
[1728] —------------- boot_extend ----------------—
[1728] sys_config_para->vol_threshold = 3500
[1728]
[1728]
[1728] —-------- product_para —————
[1728] magic = (null)
[1728] ver = 0
[1728] size = 0
[1728] magic =
[1728] magic =
[1728]
[1728] ——-------- part_para —————
[1728] ////////// max part number is 14., configured part is 2.
[1728] mbr_size = 1024
[1728] part_num = 2
[1728]
[1728] [part0]
[1728] lenhi = 0
[1728] lenlo = 136960
[1728] classname = DISK
[1728] name = ROOTFS
[1728] user_type = 0
[1728] ro = 0
[1728]
[1728]
[1728] [part1]
[1728] lenhi = 0
[1728] lenlo = 1360
[1728] classname = DISK
[1728] name = SYSDATAFS
[1728] user_type = 0
[1728] ro = 0
[1728]
[1728]
[1728] —-------- down_para —————
[1728] ///////// max downLoad items is 14., configured downLoad is 1.
[1728] down_num = 1
[1728]
[1728] [download_para0]
[1728] part_name = ROOTFS
[1728] pkt_name = ROOTFS_000000000
[1728] verify_file = VERIFY_000000000
[1728] encrypt = 0
[1728]
[1728]
[1728] —-------- fex misc -------
[1728] restore = 0
[1728]
[1728] ============================================
[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end
[1728] down and run fes1-1
[1728] down and run fes1-2
[1728] update dram size 64 to 64
[1728] INFO: Simple Test for Dram is OK.
[1728] fes-1: 64
[1728]
[1728] INFO: dram initialize successful
[1728]
[1728] INFO: run fes2
[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end
[1728] OUT 1
[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end
[1728] IN 1
[1728] SourceCodePage = 1251
[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end
[1728] Erase device
[1728] ^^ Locale string of Russian_Russia.866 is supported.
[1728] File Size High is 0X0Bytes, Low is 0X8383400Bytes.
[1728] ID = 1, fes_thread (): —120—
[1728] enable_erase_nand = 1
[1728] PANIC: tools_scan_nand (): nand_connect_info is invalid
[1728] ERR: ID = 1, fes_thread, step 120 faield
[1728]
[1728] INFO: ID = 1, update failed
[1728]
[1728] Update failed: 0x120 УІ�УК§ ° Ь1
[932] msg: 537
[932] Device change WM_DEVICECHANGE
[932] WM_DEVICECHANGE end

But the screen boards

Attached images

[Toliksol]

People, found the SDK for the chips F1C100A Melis OS

Maybe there is something useful in it to unzip the file melis100.fex?

F1C100-SDK.rar(66.03 MB)

[yaroshenkoalexandr]

After an unsuccessful firmware, the Qumo Libro Lux II (Processor F1 E200) turned out to be reanimated in the following way.

1) Disassembled the device.
2) unsolder plus battery.
3) On the computer, launched the Live Suite and selected the firmware.
4) I pressed the button to switch to the firmware mode (in my case (Return)) without releasing it connected to USB and without releasing the key pressed the second battery wire. The device has switched to firmware mode.

In theory, you can sew without a battery, but I immediately soldered before confirming the firmware, and there should be enough power from USB.

[crywed]

Oh, I found a dusty TeXet TB-431HD, with version 1.0 (there was a whistling usb port at one time).
I downloaded the firmware from the off site and decided to flash the old man under win 10 x64 and, accordingly, got a brick.

I tried to restore according to Instruction 1, but I did not succeed in anything until I noticed that win 10 did not force the driver without a digital signature.
After rebooting in the driver signature disabling mode, I installed them and updated according to the instruction No. 1 to version 1.6. YUSB whistling stopped.

So, on modern OS everything is also sewn.

[diviniti40]

Tell me there is an opportunity to remake the MSU for the programmerstm32 + mcu + 测试 + 18-09-13.rar(65.58 KB)

[aex.mitr]

Friends, health to all! Ai Nid HELP: rolleyes: .I have a Prestigio PER3764 e-book with a screen hanging on the desktop (where you can choose settings, recent books, etc.) When you disable the screen loop and the battery is disconnected, nothing happens. When trying to flash (all three ways from the manual), the sound of the device being connected is heard and immediately disconnected. Your opinion ? Throw out or try to stir up something else? : thank_you: o.O

[Flabunny]

For the sake of interest, I'm trying to revive the old Explay M25 player on the F15 chip.
I asked again - the player started up, but the process of calibrating the touchscreen did not go beyond the calibration process! I poke on the left upper cross - a right upper cross appears, but how many do not stick at it - zero reaction (although the text in the center flashes).
Hence the question: how to edit the firmware soso that when starting the calibration of the wheelbarrow was skipped? Or howedit the calibration itself? Or how else can this be fixed?
I disassembled the firmware, but I don’t know where to edit it.

The root of the firmware dump:

I translated the player to DebugMode by editing the line in sys_config.fex - now when connecting, you can see 2 new system partitions. Maybe they need to get to where and fix something?

Root of the first section:

The contents of the single "reg" folder in the second section:

Just at least stick your nose in the right direction.

UPDATE 1:Disassembled rootfs ->in the reg / settings directory, I replaced the files adjust.reg and adjust.bak with copies of language.reg and language.bak (xs, as it occurred to me, just an intuition) ->gathered rootfs ->I collected the IMG file and requested ->lo and behold The player turned on and did not offer to calibrate the wheelbarrow!But the tach is now wildly crooked and you have to tap at all, not where the interface element is!

I decided to tinker with the file adjust.reg, but I can not convert it to ini. If you start the reg2ini application that was previously adapted according to the instructions on the player itself (changed fm.axf), then just a blank desktop background and no conversion takes place. The line is not at hand there is something to use the SDK and put in the broke (although, at one time I even fell in love with Arch).So how else can you convert .reg to .ini and back?

UPDATE 2:fiddling with sys_config.fex and decided to fill in the original adjust.reg and adjust.bin and lo and behold - I was able to calibrate! And the touch is quite accurate and everything works! I reloaded the original firmware and was able to calibrate again! Straight miracles.
Now this player no longer has any sports interest in me, so this is the last entry in the logbook.

Post has been editedFlabunny - 31.01.19, 20:08

[losber]

[email protected], 15:09

People, found the SDK for the chips F1C100A Melis OS

The Chinese have conceived to create their own 'Raspberry Pi' and revive excitement. Do single-board computers on old chips with the core ARM926-ejs, with Linux and Melissa aka LicheePi Nano: rolleyes:http://debugdump.com/
From there, there is also a newer Melis SDK for the F1C100s. Unsuccessful assembly in pictures herehttps://debugdump.com/t_1823.html
The position of Allwinner is the same - they will not open the source of Melis. All they give is an SDK for application development. The kernel, the drivers are closed. You can try to gut pre-assembled kernel and drivers from the SDK to the IDA. Or pull out a new kernel and drivers in their old firmware from the new SDK.
Last year, they planned to release patches for the Linux kernel for suniv platforms (F1C100, etc.).

SdkC100s_PubRelease_V1.0_20170522.zip(123.04 MB)


allwinner_melis_config.pdf(171.83 KB)

Allwinner_F1C600_User_Manual_V1.0.pdf(9.69 MB)

F1C100s_Datasheet_V1.0.pdf(1007.56 KB)

е…Ё еї— C100-MP5 еЋџзђ† е›ѕ .pdf(221.01 KB)

F1E200_Datsheet_V1.pdf(766 KB)

F1C600_Datasheet_V1.0.pdf(1.47 MB)

Lichee_nano.pdf(630.23 KB)

[losber]

FlaBunny @ 01/30/19 19:35

Hence the question: how to edit the firmware so that when launching the calibration of the wheelbarrow is skipped? Or how to edit the calibration of the wheelbarrow itself? Or how else can this be fixed?

I apologize for not getting an answer on time.
That's right, you need to change adjust.reg / adjust.ini
The easiest way through RegEditor

Download:RegEditor.rar(297.21 KB)

Mirror:RegEditor.rar

He is in Chinese, but working with him is simple. Run in compatibility mode with Windows Vista.
In the folder with the unpacked program there is an example directory 'reg' with the structure and content from one real firmware. You need to delete its contents in the folder with the program, and place the contents of the firmware there.
After that, it is possible, but not necessary, to create a copy of the default.lrp file and, if necessary, edit it, or use it, but edit it, if necessary.
Optionally, you need to change what is in quotation marks in the string, that is, the path to the 'reg' directory with content from the firmware. By default, changed to a relative path, i.e. search for a directory in the program folder.

rootpath = ". \\ reg",

All that is needed is to expand the structure in the tree on the left before the file adjust.reg by executing double clicks, and also double-click to change the value to 0.
Changes are saved on the fly. Just close the program and copy the modified file.

Screenshots

Post has been editedlosber - 22.02.19, 22:20

[Inter_CitySat]

People, and here a question the Texet TB840HD device on SoChip? And another question is if the device on Sochip is possible for him to create firmware based on Windows CE, I have it in the BIN format and programs for creating and installing.