![]() for now there's some focus on how to bypass the checksum which seems to have been explained a few times. i have not had time to purchase a rom emulator and if you followed the other thread on andy's forum we've pretty much reached the limits of emulation w/ the software without writing a dedicated input simulator. and Thouse ECU have socet ONLY for EPROM - 27c256(512)-413 There no any shadowing going on.ĪAAaaaaa. ![]() given that the 413 dme doesn't do rom shadowing, an ICE would probably be unnecessary because you can do all the address tracing you want from the rom emulator and that's good enough for what i want to use it for.Now I understand you. data access buffers, much like the rom emulator you were talking about, are pretty much the same things. branch trace buffers give you the ability to reconstruct the code path of the cpu and is typically non-intrusive, at least for ICE's. if you wanted to set a breakpoint on a data access to the address of the idle fuel map, the cpu would stop when it access this region of memory. the the ICE can give you the ability to stop the cpu given certain conditions, like address matching. i'm not sure if the 413 dme is socketable, but if it isn't, it quickly renders this idea pointless. given that the 413 dme doesn't do rom shadowing, an ICE would probably be unnecessary because you can do all the address tracing you want from the rom emulator and that's good enough for what i want to use it for.Īn in-circuit-emulator actually emulates the 80196 cpu and replaces it entirely in the socket. ![]() The ECU of 402 and 403 don't do shdowing of rom image.Ĭould you gave a bit more of info on that? espicialy on breakpoints and branch trace buffersĤ13 also don't do shadowingan in-circuit-emulator actually emulates the 80196 cpu and replaces it entirely in the socket. the far left 4 characters are the addresses, data in between that and the assembly mnemonics is the opcode in hex, and stuff that starts with an "L" to the left of the mnemonic means it's a label.Ģ086 A3 01 00 40 1C L2086 LD L001C,L4000 [ascii B1 1E 0A LDB TMR1LO,#001Eh. it just keeps repeating this over and over. at this point i'm not sure why it's doing this, probably not finding something it needs to so i'm single stepping this. So here is an instruction trace of the code loop the emulator is executing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |