No no nooooooo If you use more than one character as delimiter then how to you send the OFF command? Can you send M1_ON$ from the pc and get your firmware to send back the received string to the PC with only having $ as delimiter character? If yes then we can move on with trying to compare strings. ...

Short answer is no. For uart_read_text to work you need these things 1: a string variable to store received data into 2: the message you want to receive MUST have a delimiter. That is a character or characters that will tell the function that the end of message has arrived. In the below example i us...

LCD_OUT(1,1,"Hello"); //This is displayed correctly indicating the LCD connections are OK. LCD_OUT(2,2,Result); //This is simply ignored without any error or warning, I Don't know why? The reason you think it is a compiler problem is because you did a mistake. Result from strcmp is a numerical valu...

Hi, I think you have several problems with your code. 1: char uart_rd; This is a byte variable and can not be used to store an entire string consisting of several characters. 2: if (UART1_Data_Ready()) { uart_rd = UART1_Read(); // read the received data, UART1_Write(uart_rd); // and send data via UA...

Hi, One 16 bit integer value consist of a HIGHBYTE and a LOWBYTE. so one way is to use a 8 Bit variable and store each part of the 16 bit integer at 2 different addresses in the EEPROM for example.. unsigned int REGISTER = 0xABCD; unsigned char DUMMY=0; DUMMY=REGISTER; (this will actually put 0xCD i...

and have you tried to add a null character 0x00 in the end of your firmware string to make sure it is zero terminated?

and be aware that strncpy does NOT add a zero termination to the destination string so if you use that in your code.

Hi, if you first erase the entire pic, then use a programmer to load the bootloader and make sure the configuration bits are not set for code protection. then read back the entire FLASH and view the hex data and see what is stored at 0x0580. now let the bootloader load the firmware and now read the ...

Filip, is there any plans to release an upgrade for the mikroprog suit and programmer so we finally get support for all pics that the compilers support with full debugging features or is mikroprog a dead horse and we should all stop beating it to get it to move?

Hi,

Yes with my bigger project entering debugging takes several minutes. If you think it is useful I can email you the zip of the project and you maybe can try? If you think it is useful please give me your email address.

by the way the PIC is running on internal 8 Mhz with x4 PLL =32 MHz and that FQ is also set in the project settings.

and flashing a LED shows that the board is running at the expected FQ

Hi, I.am.using a mikroprog together with mikroc pro for pic and 16f1824 and when i started my project the hardware debug sessions would start up fast. but now when the project is just slightly bigger it takes several minutes to enter the debug session and during that time the mikroprog leds flashes ...

Hi, Is the hexfile stored internally in the CODEGRIP or is it received via WIFI each time it should program a PIC? How secure is the transfer protocol for the WIFI connection, is the hexfile sent in plain text or is there any secure protocol that ensures that the hexfile can not be extracted from th...

thank you janni for giving this clear answer.

Now I understand!

my code would still not run and I still can not debug using mikroProg but it would have failed in a more modern and colourful IDE.

Merry christmas!

Yes, you can do that also if you want @Filip So you mean that the pic57k42 have full support of all built in libraries in PIC AI and mikroProg can debug this pic if I move to NECTO? TFT, FLASH, HW I2C, HW SPI so any code i can run on a PIC18F46K20 will run on the 57K42 with no or minor changes? NEC...

I am still waiting for PIC18F57K42 to be supported with all libraries and MikroProg debugging in mikroC PRO for PIC but seems it might not be happening. This PIC a quantum leap in RAM memory compared to what was available before in 8-bit MCU. This device was released a long time ago and is supported...