- 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
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- 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
- S32Z/E
-
- 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
- Generative AI & LLMs
-
- 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
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
- Home
- :
- Product Forums
- :
- ColdFire/68K Microcontrollers and Processors
- :
- M52233DEMO UART problem
M52233DEMO UART problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
M52233DEMO UART problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having a problem with displaying a simple string "Hello World" to the terminal using the M52233DEMO board via serial. The output consists of some gibberish ASCII characters. I tried various baud rates and I'm confused as to why the string is not displayed properly. Any help would be greatly appreciated. Thank you :-)
Original Attachment has been moved to: StringTest.zip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm trying to create a project in CW 10.5 eclipse under windows 8 74bit.
I see from the screenshot attached that you use CW eclipse for this board...
Could you please post a basic project for the M52233DEMO board in CW 10.5 or a link where to download a basic sample for this board for CW eclipse?
I received the board only with samples in CW 7.2 which is not suitable for win 64bit.
thank you
Maurice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is most likely to be the baud rate that is wrong. The most likely cause of that is that the system clock isn't running at the rate you think it is, or you've missed a divider in the chain, or you've got an "off by one" bug where you program a register with "N" to get a division ration of "N+1" or "N-1" and you've missed that.
The standard why-would-you-do-anything-else way of fixing this is to use an oscilloscope on the pin and MEASURE what it is actually doing. That will tell you what factor you're out by, either *2 or /2, or 15/16 and that will lead you to the programming problem.
If you don't have one, then find a friend or school that has and go there.
If you still can't do that, write some code to program a timer to flash a LED at a rate you can count or measure on a stopwatch. That may show you the problem.
Before that you should read all the relevant sections of the CPU Reference Manual and cross-check with all the generated code and work out the timing chain yourself.
Tom
