S32K14x Eval board with NHD 7 inch Display module (FTD812) Sample Code

[suryazoox]

Hello @RudolphRiedel,
Thank you for helping me in advance.

I am trying to use NHD 7 inch display module ( with FTDI 812) and S32K144 eval board to bring up the display module and to play around with it. do you have any sample code or projects that I could try using s32 Design studio to start playing around with it?
Also, I tried using the following
EVE_Test_S32K144.zip but I get the following errors:

I am currently using s32 design studio version 2.2.

It would be great if you could also post some picture about your set up as well.

Thank you very much in advance.

[RudolphRiedel]

Ugh, I was kind of hoping to be done with S32K. :-)
Well, for a couple of different reasons.

I still have the "S32 Design Studio for S32 Platform" installed and it says it is Version 3.4.
Well, it also tells me that there are updates available.
But the project that got opened automatically did still compile and the target is S32K144, I also still have the eval board here.

I really has been a while, I have not updated the library in the project to the current release so far.

[suryazoox]

Thanks for your response. But do not get done with S32K. I would really need your help with it.

Well, I created a new project and started to copy the following header and c files.

It reduced the number of errors but I am stuck with the following errors as shown below:

Any help on this, please?

Also, do we need to include the PD pin as well for the connection?

[RudolphRiedel]

I wrote that I was hoping to be done, not that I am done with S32K. :-)
Ok, I am updating my S32DS to 3.4.1 now and then I'll try to update the project to 5.0.6 of my library.

The issue with DL_CLEAR_RGB is that it was renamed to DL_CLEAR_COLOR_RGB in the more recent EVE.h.
g_pin_mux_InitConfigArr0 is declared in pin_mux.c from NXP.
NUM_OF_CONFIGURED_PINS0 is defined in pin_mux.h from NXP, somehow your version is missing "0" at the end?
I removed the function macro RESTORE_CONTEXT and added the define DL_RESTORE_CONTEXT instead.
EVE_cmd_dl_burst(RESTORE_CONTEXT()); -> EVE_cmd_dl_burst(DL_RESTORE_CONTEXT);

And yes, I highly recommend using PD to the connections in order to get a proper reset cycle for init.
If PD is not used a EVE_cmdWrite(EVE_RST_PULSE,0U) is necessary for a start without power cycle, this line is in EVE_init() but commented out.

[suryazoox]

Hi Rudolph,
were you able to view the trace files?

[RudolphRiedel]

Nope, the folder is access restricted.

[suryazoox]

now you should have acess to the link.

[RudolphRiedel]

Nope, still the same, I can only ask for permission to access but I already did that.
Why not paste just the .sal file packed in a .zip here?

[RudolphRiedel]

Here is another one to take a peek:
RP2040_EVE3-50G.zip

Btw., the .sal files are actually renamed .zip files so renaming these to attach them would work as well.