Okay, it’s been a while, since I made any (real) progress on the issue, but now, well, there’s at least something to show.
I happened to be an idiot and spent a few days trying to crack a CRC-16 with a non-standard polynome, and didn’t see that it was a plain sum of the payload bytes. Afterwards, stuff was quite trivial and the protocol – simple as hell. Right now I wrote some quick and dirty parsers in bash and lua to get me the mcudb out of KEIL CDB file processed with ‘strings’. Right now it’s just a plain lua table dump, that can be updated with info extracted from a keil cdb file or by hand. Kind of slow, but for this purpose I think it’s ok for now.
Anyway, my ‘proof-of-concept’ code already does the basic things like getting and partially decoding the info packet:
[necromant@lamia stcdude]$ ./stcdude -d ./mcudb/stc12x.lua -p /dev/ttyUSB1 -i
STC ISP Tool. (c) Necromant 2012
Using mcudb file: ./mcudb/stc12x.lua
Loading mcudb ./init.lua
Done with result 0
Loading mcudb ./mcudb/stc12x.lua
Done with result 0
Using /dev/ttyUSB1 @ 19200
fd is 3
Waiting for an infopacket from MCU...
--- 8< ---
Part name: STC12C5A32S2
Magic bytes: D170
IRAM size: 256 (0x100) bytes
XRAM size: 1024 (0x400) bytes
IROM size: 32768 (0x8000) bytes
Tested ops: FixMe: implement reading of tested ops
Description:
8051-based microcontroller with 1T(1-clock) High-Speed Core,
Dual DPTR, 36-44 I/O Lines, 2 Timers/Counters, 2 PCA Timers,
Alternative build-in oscillator,
Independent Baud Rate Generator, Programmable Clock-Out,
32K bytes flash ROM, 1280 bytes data RAM,
On-chip EEPROM, 2 UARTs, WDT, ISP/IAP, A/D, CCP/PWMm
--- 8< ---
Further stuff is still work-in-progress, diggings showed up, that there might be at least 3 different variations of the ISP protocol, so we're far from full-blown support. But since most things stay the same, after the initial skeleton is ready, adding support for further variations should be straightforward.
For those who want to try out this stuff, grab your copy at my github.
Hello. I just wanted to let you know I think it is great you are taking on this task. I am finding the STC chips to be an excellent value and generally easy to work with (good performance and reasonably straightforward architecture). However, that terrible VB ISP upload software is by far the biggest drawback to using these chips. I can’t understand why STC does not document the protocol (or at least provide support for other OSes than ancient Windows versions). However, it sounds like you are making some really good progress. I will try to test it out on my STC12C5A62S2 chip sometime soon. Best of luck on your continued success!
1 Floor.I want to tell you.are you concentrate about the STC MCU table.
if you are very serious.that you can discovered:
In fact,if you add up EEPROM and FLASH ‘s size.and it is 62kB.
So,STC12C series MCU ‘s grade is soft-partition.
that is why STC do not open the protocol .