Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!ee.rochester.edu!moscom!adp From: adp@moscom.UUCP (Alan Percy) Newsgroups: comp.sys.m68k Subject: 68302 Development Message-ID: <2422@moscom.UUCP> Date: 17 Dec 90 20:00:54 GMT Organization: Moscom Corp., E. Rochester, NY Lines: 46 In article <4778@tellab5.tellabs.com> jab@tellabs.com (Jeff Brooks) writes: >Hello, > >Our group has begun a new realtime project which uses a realtime operating >system. We have just spent about $80K on new emulation equipment to debug >our code, but, we need some ideas on how to debug the code we write without >the realtime operating system getting in the way.... We started our 68302 development over a year ago and had a similar situation. What to do with out 68000 emulator (the 68302 pod was not available yet), how to debug the operating system, and then how to debug application tasks. In our environment we built our first hardware prototypes with a 68000 socket next to the 68302. We then used the emulator pod to get all the peripherals working until we got our first processors. BTW this proved to be very helpful, getting all the hardware working before debugging. Once we got the processors we used a logic analyser in the 68000 socket to get the operating system (OS9) bootstrap working. Now we used the "kernel debugger" and the logic analyser to get the drivers to work. In your situation, use the emulator instead. This debugger is very low level, ie: hitting a breakpoint stops the operating system. To this day we have left this debugger in the kernel bootstrap, but have to hold down some keys to initiate it. Once the kernel and drivers seemed to play together, we started using the task level debuggers for the application. This is similar to the debugger in MTOS. In a nutshell, we only needed the emulator or logic analyser for the first six months. But think about it, if we didn't have them how would we have gotten started?? The 68302 has some very capable and complex internal peripherals that now seem simple, but a year ago you would have heard another story. Good luck!! -- A nanosecond here, a nanosecond there, next thing you know you've got real time. Alan Percy..........................{rutgers,ames,cmcl2}!rochester!moscom!adp