Many thanks for your help , Janni !

Thanks for your answer .
You write times about erase and write operations : that is to say that it is necessary to erase data before writing it ?

Hello, I want to use PIC18FJ (Pic Clicker or pic18f27j13 or pic18f27j53) instead of the PIC18F2520 that I usually use. But there is no EEPROM memory in pic18fj chips. There is a Mikrobasic library for using flash memory to store data but I have not seen any informations about using it with pic18fj. ...

I had several times a problem with constant byte arrays in big codes. Access to array is ok in main program but fail in sub procedures (return nul values). When transferring the constant byte array into a variable byte array in the main program (same name) , it works . const MyData as byte[90]= (......

It seems to me that this bug occurs also for byte constant array when the code is big ....

Mikroelectronicas is it aware of this problem ? Do they will correct it ? Or is there any way to avoid optimisation bug ? It is really a problem for me, as my code is huge (hex file is about 55ko) , I can't change it as a blind man until it works. It it possible to download the old version without t...

I use a PIC18F2620 .
Could it makes a difference in compilation , depending on microcontroller type ?

I use Mikrobasic 6.4.0 .

Here is the complete code : program MyProject dim ADC0 as sbit at PORTA.0 sfr 'e ok Alim as sbit at PORTA.1 sfr 'so ok SelectMS as sbit at PORTA.2 sfr 'so ok RS as sbit at PORTA.3 sfr 'so ok Poussoir_Start as sbit at PORTA.4 sfr 'e pous_dec ok Poussoir_Stop as sbit at PORTA.5 sfr 'e poussoir ok RC5_...

Yes, I have initialize the Usart. I have remove it from the code to make it easier to read. Usart is working very well, no problem with it.

This problem also occur when making calculation in the code. Constant array gives a null value instead of the good one.

Hello, I have a very strange problem wich I track since several months about constant arrays ... When accessing to a constant array, it happens that changing sligthly a code gives different results . This code gives a wrong result : const AR as word[10] = (0,1,2,3,4,5,6,7,8,9) sub procedure UART_Deb...

Many thanks for this idea, it works ok !

Hello, I need a FOR-NEXT structure with variable limits. dim i,v1,v2 as byte dim vstep as integer v1=10 'values for example v2=0 vstep= -1 for i=v1 to v2 step vstep 'code next i But STEP value seems to be necessarily a constant . Is it right ? It is not written in help but compilation say this : Syn...

LCD_OUT command seems not to be concern because I noticed this problem before use of this command (I add this command to look at this problem). To summarize this problem: - 1 - acces to LIST[2] (with a litteral index) is ok acces to LIST (with a variable index) is right or wrong (zero values instead...

I made a test with software debugger and a code wich display two times the LIST const array : first time, display is ok, and second time, display is all zero instead of good values. I add breakpoints at LCD_OUT commands and I display variables (variable character and variable i), on both parts of th...