UART as host interface for CLRC663

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

UART as host interface for CLRC663

543 Views
lokeshjassal2004
Contributor I
Hi NXP Community,
 
I am experiencing an issue where my CLRC663 plus is not responding over the UART interface, and I would appreciate any insights into what might be missing from my configuration.
 
Problem Description:
Despite sending valid frames to the RX pin, the CLRC663 TX pin (Pin 30) remains idle (no signal transition).
 
Current Setup & Troubleshooting Steps:
  1. Power & Clock: I have verified the device is not in Power Down (PDOWN) state. All power supplies are stable, and the oscillator is functioning correctly.
  2. Interface Selection: Pins IFSEL0 and IFSEL1 are both tied to VSS, which according to the datasheet, selects the UART interface.
  3. Physical Layer:
    • Pin 31 (IF3): Connected to PAD_VDD (3.3V) as required per the CLRC663 Datasheet.
    • Logic Levels: Verified 3.3V for High and 0V for Low on all digital lines.
  4. Signal Analysis: I have attached oscilloscope plots for Pin 28 (RX) and Pin 30 (TX).
    • The RX plot shows a valid command to read register 0x3D (PLL_Ctrl Register) at the baud rate of 115.34 kbps, which is close to default rate of 115.2kbps.
    • The TX plot shows no response from the CLRC663; the line remains consistently high.
lokeshjassal2004_0-1769357827764.png
 
Question:
Since the interface pins (IFSEL) and power levels are correctly configured for UART, is there a specific startup sequence or internal reset condition required before the CLRC663 begins monitoring the UART RX line?
Any help would be greatly appreciated.

 

Regards,
Lokesh Jassal

0 Kudos
Reply
1 Reply

406 Views
jimmychan
NXP TechSupport
NXP TechSupport

Please read the 8.4.3 RS232 interface in the datasheet.

 

FYI.

CLRC663 Programming Guide via UART - NXP Community

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2300042%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EUART%20as%20host%20interface%20for%20CLRC663%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300042%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3EHi%20NXP%20Community%2C%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3EI%20am%20experiencing%20an%20issue%20where%20my%20CLRC663%20plus%20is%20not%20responding%20over%20the%20UART%20interface%2C%20and%20I%20would%20appreciate%20any%20insights%20into%20what%20might%20be%20missing%20from%20my%20configuration.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CSTRONG%3EProblem%20Description%3A%3C%2FSTRONG%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3EDespite%20sending%20valid%20frames%20to%20the%20RX%20pin%2C%20the%20CLRC663%20TX%20pin%20(Pin%2030)%20remains%20idle%20(no%20signal%20transition).%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CSTRONG%3ECurrent%20Setup%20%26amp%3B%20Troubleshooting%20Steps%3A%3C%2FSTRONG%3E%3C%2FDIV%3E%3COL%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3EPower%20%26amp%3B%20Clock%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EI%20have%20verified%20the%20device%20is%20not%20in%20Power%20Down%20(PDOWN)%20state.%20All%20power%20supplies%20are%20stable%2C%20and%20the%20oscillator%20is%20functioning%20correctly.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3EInterface%20Selection%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EPins%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EIFSEL0%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EIFSEL1%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eare%20both%20tied%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EVSS%3C%2FSTRONG%3E%2C%20which%20according%20to%20the%20datasheet%2C%20selects%20the%20UART%20interface.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3EPhysical%20Layer%3A%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CUL%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3EPin%2031%20(IF3)%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EConnected%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EPAD_VDD%20(3.3V)%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eas%20required%20per%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3ECLRC663%20Datasheet.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3ELogic%20Levels%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EVerified%203.3V%20for%20High%20and%200V%20for%20Low%20on%20all%20digital%20lines.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3E%3CSTRONG%3ESignal%20Analysis%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EI%20have%20attached%20oscilloscope%20plots%20for%20Pin%2028%20(RX)%20and%20Pin%2030%20(TX).%3C%2FSPAN%3E%3CUL%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EThe%20RX%20plot%20shows%20a%20valid%20command%20to%20read%20register%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E0x3D%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E(PLL_Ctrl%20Register)%20at%20the%20baud%20rate%20of%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E115.34%20kbps%2C%26nbsp%3B%3C%2FSTRONG%3Ewhich%20is%20close%20to%20default%20rate%20of%20115.2kbps.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EThe%20TX%20plot%20shows%20no%20response%20from%20the%20CLRC663%3B%20the%20line%20remains%20consistently%20high.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FOL%3E%3CDIV%20class%3D%22%22%3E%3CSTRONG%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22lokeshjassal2004_0-1769357827764.png%22%20style%3D%22width%3A%20747px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22lokeshjassal2004_0-1769357827764.png%22%20style%3D%22width%3A%20747px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22lokeshjassal2004_0-1769357827764.png%22%20style%3D%22width%3A%20747px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F374159i8C9D5FD0142039B8%2Fimage-dimensions%2F747x224%3Fv%3Dv2%22%20width%3D%22747%22%20height%3D%22224%22%20role%3D%22button%22%20title%3D%22lokeshjassal2004_0-1769357827764.png%22%20alt%3D%22lokeshjassal2004_0-1769357827764.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CSTRONG%3EQuestion%3A%3C%2FSTRONG%3E%3CBR%20%2F%3ESince%20the%20interface%20pins%20(IFSEL)%20and%20power%20levels%20are%20correctly%20configured%20for%20UART%2C%20is%20there%20a%20specific%20startup%20sequence%20or%20internal%20reset%20condition%20required%20before%20the%20CLRC663%20begins%20monitoring%20the%20UART%20RX%20line%3F%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3EAny%20help%20would%20be%20greatly%20appreciated.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3CP%3ERegards%2C%3CBR%20%2F%3ELokesh%20Jassal%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2312508%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20UART%20as%20host%20interface%20for%20CLRC663%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2312508%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EPlease%20read%20the%26nbsp%3B8.4.3%20RS232%20interface%20in%20the%20datasheet.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EFYI.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FNFC%2FCLRC663-Programming-Guide-via-UART%2Fm-p%2F664722%22%20target%3D%22_blank%22%3ECLRC663%20Programming%20Guide%20via%20UART%20-%20NXP%20Community%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E