Timeline for CM6533 USB-codec internal 8051 MCU
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 12 at 18:40 | comment | added | Justme | You need chip vendor support, such as data, libraries, the firmware may even be a precompiled object you can only link with your modifications, with some specific compiler, and full internal register set may not be available to you. It likely contains proprietary intellectual property that won't be given to you even if some company has it - they will likely not give out their IP to random hobbyists. | |
| Nov 12 at 15:12 | comment | added | SamGibson♦ | @Digger18 - Hi, IMHO this answer by Jeroen3 is the answer - you will need vendor support. If the vendor isn't answering you, then your project will not be successful. || I worked with a device that had internal firmware a while ago. Again, no public documentation was provided for that f/w. Vendor support was required in order to get the f/w source code (via a login to their website); they only qualified one obsolete compiler so we had to use that; the required docs were only released under NDA etc. || If you aren't some vendor's target market (i.e. $$$) they may ignore you :( | |
| Nov 12 at 13:28 | comment | added | Digger18 | I understand, but this vendor does not want to answer me. I already wrote to him. Maybe someone has worked with such a chip. | |
| Nov 12 at 7:44 | history | answered | Jeroen3 | CC BY-SA 4.0 |