This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hello.
If I proceed with the procedure below normally and read STATUS1,
SPI Watchdog warning appears.
How do I solve it?
Status0~2 read by SPI is C2 08 26 C3 00 20 C5 00 0B C6 04 90
8.2.4.5.2 Broadcast Deployment
1. Write CMD2 = 84h (No deployment delay) or 86h (with deployment delay) to trigger the deployment
(CLR_FAULT, LOCK_CONFIG also asserted), followed by CMD2 = 00h. Response will include previous
command content (command confirmation).
2. Wait ~1 msec or ~3 msec (depends on the DEPLOY_ISEL settings) for deployment to complete
3. Read STATUS0, STATUS2 , MEAS0 and MEAS1
4. A normal response should indicate
a. DEPLOY_SUM = 2h
b. DEPLOY_STAT = 0h
c. Deployment start time measurement - TSTART_MEAS
d. Deployment current duration measurement – TDEPLOY_MEAS
Thank you.
Hi Soonnam,
Thanks for the question
SPI watchdog error is coming since the SPI is inactive for the SPI_WD_SEL duration.
In case this needs to e avoided you can read STATUS0 continuously with in SPI_WD_SEL.
Thanks,
Ibinu
From STATUS0 read bac it looks like the DEPLOY_SUM = 0x2 which means that the deployment is successful.
Thanks,
Ibinu
Thank you for your reply.
I issued the Deployment command and succeeded.
Why do I get a warning when I read the STATUS0 register?
The reason for the warning is SPI_WD_W.
During the initialization process, the value of STATUS0 is 1E 02, which is normal.
Hi Soonnam,
The device has a integrated SPI watchdog monitor which is set by SPI_WD_SEL.
In case the device does not get an SPI command for the time set by SPI_WD_SEL then the device will issue a warning. This warning can be used to see if there a break in SPI communication between master and slave.
Thanks,
Ibinu