- 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
- :
- CodeWarrior
- :
- Classic/Legacy CodeWarrior
- :
- Codewarrior 9.4 on Macintosh
Codewarrior 9.4 on Macintosh
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Codewarrior 9.4 on Macintosh
02-04-2008
11:29 PM
2,250 Views
larryb
Contributor I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have used Codewarrior for many years for a freeware application for the Macintosh. It is now time to convert to XCode. I am first converting the project to a MachO application. I am using CW9.4 and XCode 2.5. After creating a MachO target, I find that I cannot debug my original target (carbon) code. When I start the debug version, there is a long pause and the application starts up without the normal start screen at the beginning of the code. Codewarrior does not stop at any breakpoints. When I quit the application, there is a long pause. When I try to run the application again (in debug) mode, I get the message that "The process is already starting".
Does anyone know what is going on? I tried upgrading to Codewarrior 9.6. I downgraded to XCode 2.2. I removed Codewarrior and reinstalled. It seems like once I created a MachO target, some switch got changed which will not allow me to debug my non-MachO (carbon) target.
Thanks for any advice.
Does anyone know what is going on? I tried upgrading to Codewarrior 9.6. I downgraded to XCode 2.2. I removed Codewarrior and reinstalled. It seems like once I created a MachO target, some switch got changed which will not allow me to debug my non-MachO (carbon) target.
Thanks for any advice.
2 Replies
02-05-2008
05:02 PM
864 Views
J2MEJediMaster
Specialist I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Freescale no longer supports the Mac and Windows desktop version of CodeWarrior. However, I'll try a shot at an answer here.
The mach-o code uses a completely different calling and access conventions from Carbon, which uses code objects called code fragments. The two are incompatible, so that would explain why once you've set the build target up as mach-o, you can't go back to debug Carbon code. You probably need to set up two projects, one with a Carbon target and one with a mach-o target.
I don't know enough about the last Mac versions of CodeWarrior to explain the odd behavior. Sorry.
---Tom
The mach-o code uses a completely different calling and access conventions from Carbon, which uses code objects called code fragments. The two are incompatible, so that would explain why once you've set the build target up as mach-o, you can't go back to debug Carbon code. You probably need to set up two projects, one with a Carbon target and one with a mach-o target.
I don't know enough about the last Mac versions of CodeWarrior to explain the odd behavior. Sorry.
---Tom
02-05-2008
05:09 PM
864 Views
larryb
Contributor I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the advice. I did decide that I should probably use two different projects for this with one for mach-o and one for carbon. But I still have the same problem. It seems like a switch was change somewhere ... in a .plist file, etc that does not allow the normal debug with carbon to work. I did find one other question about this same problem yesterday on another web forum site dated about 18 months ago but there were no answers for it.
