Latest images
2 issues;
- When a new firmwire (name is different from the old one) is upload to the mcu, circuit is not set as changed, and may cause work lost when quit ( Since there's no save confirmation ). It have caused some trouble while I was debugging multiple mcus.
- Add mcu's id and type to the "Firmwire uploaded to" message instead just the mcu type. It helped me make sure the mcu has the correct hex.
BTW:
- There should be a way to show a mcu's current firmware filename, or list of mcus and their firmware filenames, even just after the circuit is loaded. It's useful to debug circuit that has multiple mcus.
- Minor issue: Change component's id won't set circuit as changed ( and not undoable).
- When a new firmwire (name is different from the old one) is upload to the mcu, circuit is not set as changed, and may cause work lost when quit ( Since there's no save confirmation ). It have caused some trouble while I was debugging multiple mcus.
- Add mcu's id and type to the "Firmwire uploaded to" message instead just the mcu type. It helped me make sure the mcu has the correct hex.
BTW:
- There should be a way to show a mcu's current firmware filename, or list of mcus and their firmware filenames, even just after the circuit is loaded. It's useful to debug circuit that has multiple mcus.
- Minor issue: Change component's id won't set circuit as changed ( and not undoable).
- Attachments
debugger.zip - You don't have permission to download attachments.
- (1 Kb) Downloaded 1 times
