Sid Price

  • Content Count

  • Joined

  • Last visited

  1. @attilaI just hooked up my new PCB and tried this new decoder, so far it seems to work. I hope to do a little deeper decoding of some of the fields at some point, perhaps after the debugger update :) I am really looking forward to that. Again, I really appreciate your help with this, thank you.
  2. @attilaThank you so much, I should be able to test this in the next couple of days, I unfortunately had a hardware failure so I am waiting for a new evaluation board. Having the debugger use real data would be wonderful, thank you for passing that on.
  3. Hi @attila I had already tried that as a solution, the decode is still incorrect. Note the "DIR" bit is "1" but the decoder says "Device: 0".
  4. @attilaThe only change I have made is to the output function so I could check what the "DIR" bit value was: function Value2Text(flag, value){ switch(flag){ case 0: return "X" case 1: return "Start" case 2: return (value?"Host: ":"Device: ")+value.toString(2) case 3: return "CMD:"+value.toString(16) // hexadecimal representation case 4: return "Cont:"+value.toString(16) case 5: return "CRC:"+value.toString(16) case 6: return "End:"+value.toString(2) // binary representation default: return value.toString(16) } }
  5. @attila Sad to report that the decoder does not correctly decode the capture for me. The attached screen shot shows the decoder incorrectly shows "Device: 0" (I added the value after it) when the CMD input is "1". I have tried to use the script debugger to investigate but it appears the debugger only receives a very limited number of samples (100). How should one proceed to debug this? It is a great example and has helped me understand the way to write a decoder. Sid
  6. Hi @attila So sorry I missed this post, seems the forum either did not send a notification or it got lost in spam! After getting myself a little confused with the decoder I have it working, thank you so very much!
  7. @attila I am finally back to trying to get an eMMC decoder working and getting more confused, I hope I can get a nudge in the right direction. This is my attempt at a decoder, it does not produce a display at all: // rgData: input, raw digital data array // rgValue: output, decoded data array // rgFlag: output, decoded flag array samples = rgData.length synced = 0 bit = 47 clkState = 0 not_synced = 0 sync_bit = 1 tx_bit = 2 cmd_index = 3 content = 4 crc = 5 end = 6 temp = 1 for(var i = 0; i < samples; i++){ // // check if the clock input is low, if so we done for this loop //
  8. I am having trouble with my Digital Discovery. I am getting noise displayed on the digital inputs. For example, I have a 400KHz clock on DIN0 and the data is supposed to be on DIN1. I need to trigger on the DIN1 negative edge. What I see, while DIN1 is actually a constant "1" (verified with 'scope) is glitches on some falling edges of the clock (DIN0). If I ground DIN1 I still see glitches on that input. I have tried switching tot DIN3 for the data but still see the same pulses The attached screen capture shows DIN0 on CLK and DIN1 on the data input. As I said, my 'scope does not show the
  9. @attilaWhat would be an improvement is that when using "Screen" if one adjusted the time-base so the signal is displayed the instrument would stay on that time-base when the Screen display was next selected. This would at least make the instrument more reliable. It would be especially helpful if it did not adjust the time-base automatically at all, just stay on whatever the other modes are using. Chances are for a particular workspace all the modes are going to require being at similar time-bases.
  10. @attilaThanks for pointing that out ... why does the instrument do that? Seems a little user hostile to me. I have neve seen a 'scope to that and I have worked with them for many, many years.
  11. Hi @attila, I made a screen capture video of the issue. Thanks.
  12. OK, will do. Sorry I missed tour reply, I didn't get a notification from the forum. :( Hopefully I can post the screen shots later today. Thank you again.
  13. I have an issue with the scope of my AD2. I spent a long time trying to figure out why I was not seeing a 400KHz square wave on the output of my MCU. However, when I used the logic instrument it showed the signal. Eventually I switched to a different scope and the signal was indeed present and looking good. What I have found is that if the mode is set to "screen" I see a DC voltage of about half the supply rail, however, when I change to "Repeated" the signal appears once again. I also see some very strange captures when I record the signal, it should be continuous, the recording shows i
  14. Does anyone have a custom protocol file for decoding the eMMC command bus? Or, perhaps a simple decoder that would lead me in the right direction to write one. I have not written a custom decoder before and I am not sure wat the basic process is. Thanks.