Forum : ARM
| Post Information | Post |
|---|---|
|
April 3, 2007 - 10:26pm
|
Dear Sir, here there are some items that I would like to be explained/solved/included in next releases of RIDE. May be that for some of them I am wrong or I should ask to ST or GNU... 1. Why, during debugging, pressing STOP almost always carries the Disassembly window in front, instead of keeping the C source code window? 2. The TB Peripheral window in the Debugger is obsolete and doesn't show the correct registers for STR75x (may be other peripherals, too, need upgrade, but I have checked only some of them). 3. Only a few versions of STR75x family are shown in Options->Target 4. If I choose to have the map/list file in GCC, why don't add the map/list file in the project window for simple opening by double-click? 5. The font for some debugger windows is fixed (system font) and quite big. Global Symbols window uses another different font! 6. Why I cannot choose the background color for the editor (it is possible for the debugger!). After many hours looking a bright neon (the CCFL inside the monitor) my eyes could ask for a black background... 7. Line numbers in editor? 8. The STR75xFx0xxx.ld state 128k of FLASH instead of 64k. The 128k version should be STR75xFx1xxx.ld 9. Is it normal to wait 72 seconds to download a 50kbytes program in FLASH? Is there some workaround to speed up download? Enough for now, thank you for your attention Romano |
Hi,
Thank you for your feedback. Here are some answers:
1. When you press "STOP", you just interrupt the execution of the program where it is. Most of the time, the break happens on an assembler line. It is great luck to fall on a C line. We cannot cheat by displaying the C line if you are in the middle of executing it because the data would not be consistent. And we cannot step to the next C line because it could take much time and sometimes it's not even possible. (if, for example, you are executing a single-C-line loop on a variable that doesn't change)
2. We'll check that. Probably the view was just copied from STR71x and not checked properly.
3. 8. We are aware of this and plan to fix it in the very next release of RIDE.
4. Just right-click on the node (.c or .elf) and then select "view listing". The double-click is for opening the file itself (for source files) or for starting debug (for applications).
5. 6. 7. These will be handled in RIDE7, the next version of the IDE, which is due very soon, but which will NOT be in the next official release of RIDE. You are welcome to download and evaluate the beta version of RIDE7 from our website. And send us feedback. :) It only handles ST7 for now, but it allows to see what the IDE will look like. The ARM version (still beta) should be available in 1 or 2 months if all goes well.
9. For now, the only thing to do is to unselect the sectors that you don't use, if there are any. We are working on improving this programming time, but we don't expect it soon. Sorry.
Best Regards,
Vincent