[VTC-mini,FW] Need suggestions

[Ferox]

Hello

Since the VTwo, we, owners of the VTC-mini, know that our box will no longer be supported by joyetech.

That's (part of) why I wrote a custom firmware for that box, derived from the guenuine.
You may look to ClockSelect/myevic repository on Github to see what I did.

I come to you to collect Ideas and suggestions to know (and maybe do) what a dream firmware should be.

Welcome.

 

[Ferox]

Thanks for those of you who made reports to help me close some bugs.

I commited an encoded version of the firmware, usable with the official updater.
Use the file bin/myevic_enc.bin of the repository.

The firmware file given by the box's virtual drive (see readme) is also encoded, so you can share it more easily.

 

[Ferox]

Some screenshots:

Mainview with real-time clock (remember it's an evic VTC, not VTwo):



Main view with analog clock:



Menu overwiew:



coils management:
You can edit coils value, reset the coil and lock its value.



Select the modes you use or not, so that you don't see useless modes any more when changing your ato:



Change the screen contrast:



Have a cool 3D spinning cube, just to say that box is yours:

 

[Ferox]

This firmware is now compatible with VTwo and VTwo mini.
It can also be uploaded with the official firmware updater.

 

[Ferox]

Direct link:
GitHub - ClockSelect/myevic: This is My eVic VTC Mini.

Should make things easier.

 

[Alexander Mundy]

I don't have one, but did want to say nice work. I assume you reversed it? What processor and did you hand decompile?

 

[MarkyD]

Very Nice! Well done, Ferox.

 

[MarkyD]

Tried a build on mint/rosa, installed arm gcc and libs, python-evic and the library from the nuvoton sdk, all installed without error. The build starts off fine and the first assembly file gets compiled, but then I get:

src/myprintf.c: In function 'my_doprnt':
src/myprintf.c:112:5: error: unknown type name 'uint32_t'
uint32_t n = va_arg( ap, uint32_t );
src/myprintf.c:112:5: error: unknown type name 'uint32_t'

Not sure what I'm missing, all the include files seem to be present and in paths pointed to by the -I directives given in the Makefile... any ideas?

 

[Ferox]

try adding a #include <stdint.h> on files showing this error

 

[Ferox]

I don't have one, but did want to say nice work. I assume you reversed it? What processor and did you hand decompile?

Processor is a Nuvoton M452 (ARM-Cortex M4), 128K ROM, 32K RAM.
Disassembled with IDA on PC. Cumbersome job, indeed.

 

[MarkyD]

Writing APROM image...OK

Excellent! The 2 files were myprintf.c and fbdata.c

 

[Ferox]

Your playfield is now opened ^^

 

[MarkyD]

Yes thank you its working now, Ive got it running on 2 VTC mini. I was reading the nuvoton docs and from your notes on the clock that the VTC mini is missing the 32khz oscillator (the docs say "its not soldered in" on this model). I wonder if its possible to add one, Ive never disassembled it, but sounds doable.

 

[Ferox]

The slot for the X32 is available, it's just empty.
Seems like you just have to buy the right crystal and sloder it in place.
I don't know if anybody tried this.

 

[Ferox]

If you do this, the firmware *should* detect it. Obviously, it's never been tested.

 

[MarkyD]

Yes I might give that a try at some point.

I suppose there are a few KB free memory still remaining, maybe some small screensavers are a possibility, like the 3d cube but as a screensaver. easy ones would be like a qix/wandering lines, a starfield, or a 3d math function plotter. If I code something up I will send you the patches or a pull request. Keep up the great work.

 

[Ferox]

The screen saver is the screen #60, drawn by ShowScreenSaver() func. You may add stuff in there among with a selection menu. Why not.

Edit: I made your life simpler. Check the lastest version.

 

[MarkyD]

I cloned it again, thanks for the include fixes and the addition of the screensaver menu... the cube looks great, I will try to add a couple more if I am able.
Of all my many types of mods, the little VTC keeps turning up to be so flexible/hackable, and from browsing around nuvoton, what a nice little ARM processor it has. Commendations to you for your fine disassembly and coding skill, thats a really nice piece of work there.

 

[MarkyD]

Found one small issue. I didnt make a github account yet so I'll post it here. When using 3 presses to select what is on the 3rd line, when either puff count or vape time is displayed (and blinking), a long press of the firebutton should zero whichever of these is selected.

 

[Ferox]

It's a long click on both + and - buttons.
It's the standard behavior.

I strongly encourage you to have a github account and work on a fork, it'll make things easier.