|
Hi,
I have been running RIDE for several years, and have just downloaded the BN-746 release with the latest patch.
Unfortunately, I have run into new problems not present before and have recognized that old problems has not been fixed:
1.
When editing in the code editor window, the display stops to update itself after a while when using delete or backspace. The edited line has to be selected with the mouse, or scrolled beond the screen limits and back to be updated.
The editor has to be restarted for the problem to dissapear.
2.
When debugging, integer values are displayed as chars and a value of 255 for instance is displayed as 0x0 and a value of 256 is shown as 0x0.
I have also had problems with displaying arrays correctly.
3.
I have stopped using local variables, and declare all variables as global because of trouble using both stacked and non-stacked local variables.
4.
I have specified no XRAM in the linker, and not to use external stack, but still the application stops at several movx instructions when using sprintf(..) for instance. I also see in the map file that 256 byte xram is required for the application, which is to be run at an Atmel AT89S4051 which does not support the movx instruction.
I am running a Intel Centrino Dual Core processor with XP pro, but that should not have anything to do with the above mentioned problems I believe.
I hope these issues will be solved,
Steinar
[%sig%]
|
Hello, about your remarks:
1. It has been reported that using Adobe Reader plugins from Ride could interfer with Ride editor, so if you are viewing PDF files from Ride, please try disabling the plugin by unchecking the option : Project|Options|Environment|Editor|Documentations|Open as an MDI child.
2. We will check that. Could you explain more precisely your problem with arrays?
3. What is the 'trouble' you are talking about ? Can you give or send me an example ?
4. What is the memory model in the compiler options ? If you don't want to use XDATA, it should be 'compact' or smaller. 'Small' or 'Tiny' would fit your requirements.
Best regards,
Lionel
2. and 3. could be caused by the selection of the format. Use OE(2) in Options|Project|RC51|Object
Francis
Hello,
The problem is that only the first character is shown for the array, and the unsigned integer is not shown properly. The local variables are shown at first, but after a while of debugging the project local variables are not shown anymore.
I have also had problems with miscalculation when using local variables in earlier projects, and had to stop using them.
I tried to follow Francis advice and changed to the OE(2) debug format, but the problem was still present. I have earlier removed such problems (temporarily) by deleting all the non .c/.h/.prj files in the project folder before rebuilding all the project files, and I did that also with this project. The problem to be solved, but normally comes back after a while of debugging. I will send you the entire project folder when the problem comes back.
I am however using the small model, and zeroed out all xram fields in the project options, but still the sprintf(...) stops at several movx instructions when placing read/write breakpoint at the xdata address named _XSTK0 (0x0).
Thanks for your quick reply (!!)
[%sig%]