From mboxrd@z Thu Jan 1 00:00:00 1970 From: pg-itk@t-online.de (Peter Graf) To: ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] Hitachi SH7709A problems Date: Mon, 20 Nov 2000 07:20:00 -0000 Message-id: <3.0.5.32.20001120161846.008fed80@pop.btx.dtag.de> References: <"Mon,> <20> <2000> <14:36:31> <+0100> <"Fri,> <17> <2000> <11:11:19> <+0100> <14869.1095.188352.237035@thinktwice.zoftcorp.dk> <3.0.5.32.20001120143631.008fc8b0@pop.btx.dtag.de> X-SW-Source: 2000-11/msg00247.html At 15:58 20.11.00 +0100, Jesper Skov wrote: >Peter> 1. When I use the GDB stub compiled from the latest CVS >Peter> sources, I can only set one breakpoint. If I remove it and set >Peter> the next and so on, everything works fine. If I don't remove >Peter> all old breakpoints before continuing, the target keeps on >Peter> running and ignores further breakpoint(s). An older stub, >Peter> compiled from sources probably around August, works fine. Could >Peter> be related to the use of the UBC, but I haven't been able to >Peter> figure out. > >Hm, no clue. Maybe because you use a new(er) version of GDB which uses >stub breakpoints, which I believe were added to the stub recently by >Drew. Only, I don't think they should affect the HALs unless they >claim to support it somehow. I haven't looked at it. > >In mod_7709a.h you can comment out the UBC definition, and the stub >will fall back to the old way of single-stepping. But that should be >the only effect. I can't think of any reason breakpoints should be >involved. Since single-stepping also doesn't seem work anymore, I will try removing the UBC definition, thanks for the hint. >Your target is indeed a 7709A, right? Exactly. >Peter> 2. ROMs compiled in ROMRAM startup mode don't work anymore, >Peter> although the pure ROM versions work. The ROMRAM feature has >Peter> also worked fine using earlier sources. > >I may have broken something when the code was split into variant >HALs. I probably won't have time to look at it until next year though >- so if it's something you need working ASAP, you are probably best of >(a) figuring out why it fails on your own, or (b) revert to the older >codebase. Sorry. I've already started (a), but debugging by burning Flashroms is quite tough. I'll let you know if I find something. Thanks Peter