- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- Kwikstik UART
Kwikstik UART
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm just getting started with my K40 Kwikstik in CW10.1, and do not have a tower system. I've tried running several of the demos, and have been successful at building the MQX libraries to get the demos to debug and execute, however when I probe the UART5 TPs (which I believe are ttyf in software), I see no communication. I have also tried switching the BSP_DEFAULT_IO_CHANNEL to "ttye:", which should be UART4 (the CAN TPs on the Kwikstik), and have probed these with a scope as well with no success. What am I missing? The demo I'm currently trying is the "io_kwikstikk40x256", and it builds successfully after enabling ttya and ttyb.
I also debugged to see that Hardware flow control is not being used, however I also can't figure out where this is set in the software.
Any help would be appreciated!
Thanks,
Neil
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And the solution:
On the KwikStik-K40 V5 board, the silk screen labels for UART5 TX and RTS are REVERSED! As soon as I moved my probe over to the RTS pin, I saw the serial data screaming across as it should.
From continuity checking my KwikStik V5:
TP labeled as "RTS" is connected to pin A44 of the tower connector "PTE8/UART_TX".
TP labeled as "TX" is connected to pin B21 of the tower connector "PTE7/UART_RTS".
TP labeled as "RX" is correctly connected to pin A43 of the tower connector "PTE9/UART_RX".
TP labeled as "CTS" is correctly connected to pin A9 of the tower connector "PTE10/UART_CTS".
I assumed by V5 of a board, Freescale would have the basics checked out, and that a non-functioning port would be my own software mistake. I am still assuming this was my issue with UART4 as well... Maybe I'm wrong?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some more information:
I have verified that the output pins still work by using the LWGPIO, and simply toggling the bits.
Additionally, to eliminate flow control as an issue (since I'm not connected to a serial level shifter or other device), I set:
#define BSP_DEFAULT_IO_OPEN_MODE (pointer) (IO_SERIAL_RAW_IO)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And the solution:
On the KwikStik-K40 V5 board, the silk screen labels for UART5 TX and RTS are REVERSED! As soon as I moved my probe over to the RTS pin, I saw the serial data screaming across as it should.
From continuity checking my KwikStik V5:
TP labeled as "RTS" is connected to pin A44 of the tower connector "PTE8/UART_TX".
TP labeled as "TX" is connected to pin B21 of the tower connector "PTE7/UART_RTS".
TP labeled as "RX" is correctly connected to pin A43 of the tower connector "PTE9/UART_RX".
TP labeled as "CTS" is correctly connected to pin A9 of the tower connector "PTE10/UART_CTS".
I assumed by V5 of a board, Freescale would have the basics checked out, and that a non-functioning port would be my own software mistake. I am still assuming this was my issue with UART4 as well... Maybe I'm wrong?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Neil ,
So you were successful at everything?
I downloaded the demo code, MQX, added MQX patches, updated CW10.1, and build the code.....did everything per the demo lab document (0.4).
I got close but no cigar as they say.
Something appears not to be built right? Definitely, problems arise when I do the final "Run Debug Configurations",.... Did you do anything special? I'm building on WInXP.
Thanks for any info.
-Kevin 314-546-9624
