search

ClockSelect / aegis

Aegis Legend custom firmware
GNU General Public License v3.0
16 stars 1 forks source link

PCB shots #1

Open detonation opened 3 years ago

detonation commented 3 years ago

Hi, Just saw your note. I have a dead Aegis Legend motherboard laying around and a microscope. What do you need?

ClockSelect commented 3 years ago

Hello !

Thank you very much for your reply. Unfortunately I abandoned the Aegis project, due to hardware defects of the e-cig itself. It has been badly designed and has hardware flaws that can not be handled by an open-source firmware, even if the genuine firmware works fine. I'd like to write a real open-source firmware for people to design their own cigs, but for this I think I should move to other processors such as STM32. For now, I'm out of this world, but it is still a project I keep in my mind. If you know people engaging this way, please let me know; I'll be really happy to support them.

Thank you again Kind regards,

ClockSelect

;

On Mon, Aug 2, 2021 at 6:18 AM Detonation @.***> wrote:

Hi, Just saw your note. I have a dead Aegis Legend motherboard laying around and a microscope. What do you need?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ClockSelect/aegis/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZQDGSNY3BFRKL7LG6DQB3T2YL7ZANCNFSM5BL5GMXA .

detonation commented 3 years ago

Aww, I'm sorry to hear that's how things ended up, but I appreciate you getting back to me so quickly. The idea of a ground-up open source vape sounds amazing. I'll keep an eye out for others interested. I did want to say thank you for MyEvic, I ran it for many years and it never let me down.

Take care and thank you again

bm16ton commented 1 year ago

Hello good sir! Very cool work. I dont vape but sumone gave me a "dead" aegis (batterys where just shot) and I like to tinker with old/broken tech. Took me forever just to find out which chip it was running should have just googled it instead swd, but alas. So anyway I have openocd patched up, I assume it just takes bins like most mcu's the openocd patches give a file type option so Im leaning that way. No makefile here so I assume something like kiel is being used? Im not a great programmer but A lot of things in here that wont compile with a Makefile/gnu gcc, silly things like mismatched casts, static/inlines trying to be shared out of its file etc. I assume those fancy pay for ide's account for that. Any chance they can export the code in a makefile gcc friendly way? Thus far I havent been able to get anything on the screen, its possible Im flashing it wrong. Lots of MCU's have little quirks for flashing and no documentation came with the openocd patches. I dont have a nulink but various other programmars, and they seem like they are working so im leaning more towards issues with the code (probly my "fixes"). I think a tiny little board with buttons screen, buck/boost is very cool and useful. As for the hardware issues you mentioned Im all ears, always open to info that can help, and save me time. Very cool project and even tho If I do make it work it wont be as a vape. I will have a good ez gcc/makefile and uploader package available in the end, so hopefully that could help others also just starting with nuvoton chips.Also my (at least it was havent checked since firmware flashing fiasco) would enumerate as a hid device when attached with + held down, Google refused to tell me anything about a hid uploader, wondering if you have an app for that? also curious what you used to flash it? Im only interested in open-source tools, so fingers crossed. Thank you again this was unbelievably helpful, christ the pinout alone is worth hours of time!