开云体育

No distraction at all. It got me thinking about the activity of the firmware eeprom since it utilizes the extra addressing. It might help to paint a more complete picture.

That makes sense to me as well. [email protected]> wrote:

I dont believe there is any "mapping" like the Spectra and beyond use. The EEPROMs consume all the address lines except for a13 on a 2816 (JU15 is NC). The a14 and a15 are used to generate the CE for

Don't let me distract you from a focused project. De

I can add in the other address lines and read it. Will that help?

:) Here too, until it _poured_ 1.5" of rain in 45 minutes. Temp fell 10 degrees, dew point did not. I thought it might eventually be interesting to see other bus activity, especially i/o, but doing

Note to self: read the entire email, THEN reply. You already know that ... it's too hot here today, that's my excuse and I"m sticking to it! Skip <skip@...> wrote:

Yea, but we don't have all 16 address lines hooked up so you're only seeing the bottom 11 address lines so 0x108 is probably 0x8108 if we were watching all 16. 73's Skip WB6YMH

Did a read with the WG disabled. No obvious difference in the data visually which isn't unexpected.

There is a disable watchdog jumper. I wonder what if anything that would reveal. I will look.

I would expect the code plug to start at address 0x8000. I imagine you're not decoding the whole address space here, of course. The firmware seems to start at 0xC000. A code plug whose first

Fixed ... I've never really used drive, I was following your lead! 73's Skip WB6YMH

Your file was set to private. I have sent the request access request.

It triggers on any input data if all are left unselected. I guess I was hoping for some sort of way for it to read only when a certain condition is met instead of looking for a one shot trigger that

I added in the U501 firmware EPROM chip enable line under U502 EEPROM codeplug chip enable line. They are mirror opposites. That makes perfect sense and it now shows exactly where the uP is toggling

Trigger is just like on a scope, it starts recording, but it doesn't qualify what's stored in the trace buffer.? There are logic analyzers that allow such things, but I don't think this one does.?

This one looks good!? OE occurs where I would expect and the data is now consistent. The first few reads are: adr? data 0x108 0xe0 0x108 0xe0 0x108 0xe0 0x009 0x18 0x109 0x04 0x009 0x18 0x109

...... *the* CE line.....

Since you said using CE as a low trigger didnt work, I guess I should have asked what is the source for the simple trigger than is giving you results. I'm guessing you see those options when

LOW, HI, transition LOW, transition HI, transition either or none and it just acquires [email protected]> wrote: