I struggle to get any life to ADAS1000 chip. When writing command to it, the DReady pin goes high during writing cycle, should i stop the writing and wait the unit come ready?
Kind regards engineer student with headache
Thanks for the message.
Can you describe in a bit more detail what you are trying to do - in terms of writes - what have you already written, what are you trying to write? whereabouts do you see DRDYb go high and stay high? Have you initiated conversions?
What hardware are you using? What is your controller?
Let me know what you have tried and we can work to figure it out.
What code are you using?
Have you looked at some of the examples code on our WIKI page?
DRDY description from the datasheet:
Data Ready (DRDY)
The DRDY pin is used to indicate that a frame composed of decimated data at the selected data rate is available to read. It is high when busy and low when ready. Send commands only when the status of DRDY is low or ready. During power-on, the status of DRDY is high (busy) while the device initializes itself. When initialization is complete, DRDY goes low and the user can start configuring the device for operation. When the device is config-ured and enabled for conversions by writing to the conversion bit (CNVEN) in the ECGCTL register, the ADCs start to convert and the digital interface starts to make data available, loading them into the buffer when ready. If conversions are enabled and the buffer is empty, the device is not ready and DRDY goes high. Once the buffer is full, DRDY goes low to indicate that data is ready to be read out of the device. If the device is not enabled for conversions, the DRDY ignores the state of the buffer full status.
Currently i'm just trying to test the oscillator starting according
ADAS1000 Crystal Oscillator Startup -guide. So i'm just writing 0xF804BE to the ECGCTL register.In the image in my first post there is just happened power up the circuit, after 100ms i'm writing 0x81F804BE. And measuring the clock/IO pin with scope - no oscillation.
here is the link for EAGLE schematic for same picture https://drive.google.com/open?id=14h-dG-EYzr5trbF9XfdSV1hlMFWR9dTr
here is the same image as png https://drive.google.com/open?id=1WaEdTerZuaVd5sKBWbwL2ik5QSkEGjaJ
Controller is mbed.
Here is the code:
And are you checking to see if the oscillator is starting?
I see from your schematic that you are using 15pF caps at the crystal, depending on the parameters of the crystal and the layout parasitics on your board, you may need to review if this value is ok or if you need to lower the value.
The activity on DRDY is strange...are you sure your probes are properly grounded and that you are seeing proper activity on that line? Or is it possible you are picking up some noise? I wouldn't expect DRDY to change mid-write or even the later behavior doesnt' make sense.
Can you repeat the logic analyser capture from a power cycle situation - so power down the board, then apply power, then read and capture.
Apart from that schematic looks ok. Code looks benign. Nothing jumping out to me just yet...so you will need to start stripping things back to debug. If you can check the CLK is active, that would be a good first step.
woops, just found out that on pcb there wasn't any trace between pins 31 -> gnd and 40 -> gnd, both DGND, after adding jumpwires it seems to work.
I wonder who make this kind rookie mistakes? ( It seems that i have to look on a mirror and give little feedback our pcb designer )Thanks for your help.
Thanks for update Karri, I'm glad to hear you have identified the issue, these things happen, lesson learned, what's important is you are running now, I hope all goes well with your evaluations! :-)
Retrieving data ...