Hi all, I am trying to implement a project using PIC32MZ2048EFH144 to display graphics and connect two of the MEB II boards over WINC1500. I am unable to get it up and running and it seems like a FreeRTOS issue. I am attaching my project with this post.

I am unable to get it up and running and it seems like a FreeRTOS issue

I’m afraid that this bit of information is not enough to find help on this forum. Go back to the basic: try a hello world program, see if it runs, does it get into main()? Try to communicate through the debug port, see if that works. Once you have logging, things are easier. Initialise the TCP/IP stack. Allow logging ( from FreeRTOS_printf() and FreeRTOS_debug_printf() ). See if the PHY Link Status becomes high. See if the device sends out ARP messages. Can you ping it? Step by step, and you will get there.

Hi Hein, This works perfectly fine before I add the graphics stack to it. I am able to connect to personal hotspot and send messages between Server-client. When I add Graphics or vice versa, it seems to be crashing. I tried to do a compare between code and the only changes between working and non working code is that I have added the WiFi driver to it.

Hi Hein, This works perfectly fine before I add the graphics stack to it. I am able to connect to personal hotspot and send messages between Server-client. When I add Graphics or vice versa, it seems to be crashing. I tried to do a compare between code and the only changes between working and non working code is that I have added the WiFi driver to it.

Sorry, I’m not following, you say it works fine until you add the graphics but the only difference between the working and non working code is you added a Wi-Fi driver (which is not related to graphics)? If the source of the issue is the graphics then I’m afraid we would need much more detailed information to be in a position to help. To start with you said you think the RTOS is the issue, so when adding the graphics stack which steps did you take to determine the RTOS was the issue? That information would help.

So here is the thing: I started my project by familiarizing with Graphics & Aria Library from Microchip. I was able to make the widgets work and it was working fine. I used the aria_quickstart demo for this and built my game on top of that. This had touch control as well. I was able to navigate through multiple screen by clicking on a button. Next I tried the TCP/IP demo from the following link: https://microchipdeveloper.com/wifi:wh The demo uses an explorer 16/32 board. I ported that to work with the MEB 2 board + EF starter kit + WINC1500 PICTail/ PICTail Plus Daughter board. First I was able to have one WINC + EF + MEB2 to run as server and a terminal would create a client and connect to the server and exchange messages. I was able to to run one WINC + EF + MEB2 as a server and have another WINC + EF + MEB2 run as client and they were able to communicate with each other. Each of these WINCs would be connected to my personal hotspot. It was working perfectly fine. Then I tried combining these projects by creating a new one having the same microchip harmony configurator. Initially I had a few build errors and that was related to manually adding some source files that were missing. Then when it compiled and ran, the screen would turn on and go blank after a second or so. This issue had been there for a very long time and I wasnt able to figure out why. Yesterday, I found out that the SYSCONSOLEPRINT was causing the problem of making the screen go blank. I removed the print statements and now I have the screen on but the touch doesnt work. The screen just stays on. The server seems to be connecting to my hotspot. But when I tried to create a new client connection on Tera Term, I am getting this error: [hifhandleisr]589 Fail to handle interrupt -12 try Again.. Wi-Fi driver ASSERTS: Failed to handle m2m events ../../../../framework/driver/wifi/winc1500/wirelessdriverextension/winc1500_task.c, line 388 I am just trying to find a solution to solving this. I reached out to the WiFi team in Microchip and they mentioned it could be FreeRTOS issue. The WiFi team mentioned that the above error might not be becuase of WiFi and it was caused somewhere in interrupts or FreeRTOS. Please advise and let me know if further information is required on this one. Regards, Anu

It sounds like you have two or more large-ish projects from third parties that we have never seen or used, combined them, and are running into integration issues. I’m sure you appreciate that FreeRTOS is just one small component of that, and that somebody else did the integration with FreeRTOS, so it is difficult for us to really start to make any suggestions beyond generic and standard suggestions such as looking through the ‘my application does not run, what could be wrong?” FAQ to check things like stack overflow, etc. In addition i recommend reading the documentation pages for our pre-configured PIC32 examples as they contain PIC32 specific information on how to use interrupt service routines when using FreeRTOS on those parts.

Thank you for your response. Can I get a link to the documentation you are mentioning?

Not at my computer now but go to FreeRTOS.org, click the quick start guide, and that will show you how to find it.