I am having an issue using NXP LPC18xx Serial Port on the latest pack. We just started a new project and I decided to update the packs just as a "get the latest" thing and it has some TLS stuff that may come in handy. We were using Device support 2.5.0 and middleware 7.0.0 without issue for years (and earlier versions). I installed Device support 2.10.0 and Middleware 7.8.0 and now the serial port does not work. Let me explain, I do the USARTdrv->Send, I get the call back and move past the wait (so it looks like it worked) but nothing physically goes out the port. Please note, I have gone back and forth a few times between the old and new versions and the old works every time. I have version of code that only does the serial bits and that has the same issue. Any Ideas?
Tool Version Numbers:Toolchain: MDK-ARM Professional Version: 5.15.0Toolchain Path: C:\Keil_v5\ARM\ARMCC\BinC Compiler: Armcc.exe V5.05 update 2 (build 169)Assembler: Armasm.exe V5.05 update 2 (build 169)Linker/Locator: ArmLink.exe V5.05 update 2 (build 169)Library Manager: ArmAr.exe V5.05 update 2 (build 169)Hex Converter: FromElf.exe V5.05 update 2 (build 169)CPU DLL: SARMCM3.DLL V5.15.0Dialog DLL: DCM.DLL V184.108.40.206Target DLL: ULP2CM3.DLL V220.127.116.11Dialog DLL: TCM.DLL V18.104.22.168
I just made a test on a MCB1800 board (LPC1857 based) using the latest DFP 2.10.0 pack, middleware v7.8.0 within MDK v5.28a using the latest armcc v5.06u6 compiler. The "USB Device Virtual COM" example from Pack Installer works fine, which exchanges data between the UART0 and the USB0 ports. This can prove that the CMSIS UART driver in the latest DFP pack works fine
Thank you for the information, taking the time to respond and you are correct it does work but here is my issue. The VirtualCOMM example uses RTOS2 - Keil RTX5 with cmsis_os2.h and this original project I am building on is RTX using cmsis_os.h and it is a huge project. I think that might be an issue. Do you think you using MDK v5.28a using the latest armcc v5.06u6 compiler is the difference? Is there a step by step conversion to the new os or...?
RTOS version shouldn't have any impact on the CMSIS UART driver included in the DFP pack. A quick test with the examples in Pack Installer is just to verify if there is a general issue with CMSIS UART driver for this device. If upgrading a DFP pack, your original example doesn't work properly, you should further debug it to find the real root cause.
On the other hand this doc helps you to migrate your RTOS from v1 to v2
Chen, Thank you again for your support!! I agree the CMSIS UART driver included in the DFP pack is not the issue. The pack changes a whole host of other bits and pieces that may be an issue. Just to make sure I set my system again back to Device support 2.5.0 and middleware 7.0.0 and everything worked. So there is an issue with the upgrade but trying to find it is like looking for a needle in a haystack.
I started the Level 1 Migration - Upgrade to RTX5 on API v1 as you suggested yesterday but it may take a day or two since the settings are not the same and quite complicated.
View all questions in Keil forum