jab@tellabs.com (Jeff Brooks) (12/09/90)
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. Our setup: Target: Motorola 68302 (68000 with extra goodies on board). RTOS: MTOS-UX from Industrial Programming Inc. Emulator: HP9000/400 running HP-UX and a 64700 Series M68302 emulator. Compiler: Microtec 4.1 Language: C for everything except drivers. Up to now our group has been using assembly language and writting our own single threaded operating system. The concept of debugging code in an environment with a preemptive operating system has us thinking that all the money we spent on the fancy emulation system has been wasted. How do you step through code without the operating system getting screwed up? MTOS has a debugger task, but, its cumbersome to run in our target and doesn't let us take advantage of the M68302 specific features of the emulator. Any help you good people could provide would be deeply appriciated (mainly because I was responsible for spending the money on the new emulation system and if we can make use of it, the company may have no use for me either :-). Please email your methods for debugging code with a realtime OS even if its a different processor/OS combination. I'll summarize them and let you know how we decided to work it out (bet ya can't wait :-). Jeff Brooks Tellabs Inc. Lisle, IL jab@tellabs.com
paulc@hp-lsd.COS.HP.COM (Paul Carroll) (12/12/90)
/ hp-lsd:comp.realtime / jab@tellabs.com (Jeff Brooks) / 2:44 pm Dec 8, 1990 / 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. Our setup: Target: Motorola 68302 (68000 with extra goodies on board). RTOS: MTOS-UX from Industrial Programming Inc. Emulator: HP9000/400 running HP-UX and a 64700 Series M68302 emulator. Compiler: Microtec 4.1 Language: C for everything except drivers. Up to now our group has been using assembly language and writting our own single threaded operating system. The concept of debugging code in an environment with a preemptive operating system has us thinking that all the money we spent on the fancy emulation system has been wasted. How do you step through code without the operating system getting screwed up? MTOS has a debugger task, but, its cumbersome to run in our target and doesn't let us take advantage of the M68302 specific features of the emulator. Any help you good people could provide would be deeply appriciated (mainly because I was responsible for spending the money on the new emulation system and if we can make use of it, the company may have no use for me either :-). Please email your methods for debugging code with a realtime OS even if its a different processor/OS combination. I'll summarize them and let you know how we decided to work it out (bet ya can't wait :-). Jeff Brooks Tellabs Inc. Lisle, IL jab@tellabs.com ----------
paulc@hp-lsd.COS.HP.COM (Paul Carroll) (12/15/90)
Hum, it looks like my response to Jeff got hosed (luckily, I sent him email as well). Anyway, the gist of my response (which, WARNING, may be considered self-serving and commercial) was as follows: a) HP does have C language tools, debugger/simulators, and debugger/emulators for use with the HP64700 tools. b) Jeff might see if Microtec would consider porting Xray to the HP 400. Either suggestion might be considered commercial, since HP could see profits, so I hope this posting isn't out of line. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Paul Carroll "Math can be used for evil + + HP Logic Systems Division as well as for good" + + paulc%hp-lsd@hplabs.hp.com + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++