I have been reading MDK5 documentation and testing different projects for several days. I got an impression that better stay with MDK4 if you have ongoing projects developed under MDK4, which is my case. Otherwise it will be a nightmare.
Did you install the "Legacy Support". When using that, MDK v5 behaves like MDK v4.
Thanks for your replay
Yes, I did. It will make most of the UV4 projects going. But for maintaining the existing projects in production, I just don't have the confidence that it won't cause me any issues down the road. I am using RTOS and RL-TCPnet in most of my product.
I didn't have too much of concern in those UV4 MDK version upgrades.
I think I am not the only one having this impression about MDK5 after playing with MDK5 on a separate computer for almost a week now, or am I? LoL
Thanks
Paul
Dear Mr. Keil
I didn't realize it was you replying. I like those presentations you made. :-)
MDK5 is on the right direction for sure. And it is very encouraging for the embedded software developer like myself. I am doing cell phone app developing too. I can see where Keil is going. I was very very anxieties to anxious to test MDK5 on my existing projects using RTX and RL-TCPnet. One of the difficulties I have right now is the ENC28J60 driver I had working on MDK4. But couldn't find any document for writing the driver for MDK5. I read thought the CMSIS driver manual, but with my limit knowledge about the CMSIS driver and Ethernet, I still couldn't figure out a clear to get my hand wet start trying things. I also browsed the sample driver .C files comes with MDK5. I got some clues for what needs to be implemented. But again, some basic guidance would help me a lot.
In MDK4, you just need to implement a few functions like, init_ethernet(), send_frame(), etc.
I also analysed MDK4 TCP_CM1.lib and the counterpart for CM0 in MDK5. I didn't see send_frame() in MDK5. Pretty sure that architecture is gone. I was a little hopeful :-D
My email is bonmotwang@hotmail.com Looking forward to get help from you.