RADE Error (Code 1) on KW47B42Z83AFTB — digital_key_car_anchor_cs_freertos

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

RADE Error (Code 1) on KW47B42Z83AFTB — digital_key_car_anchor_cs_freertos

403 Views
chris123951
Contributor III

 Hi NXP Support Team,

We are using the KW47B42Z83AFTB on a custom PCB for both ECU (anchor/car side) and Transponder (device side) roles.

Setup:
- SDK: SDK_25_12_00_KW47B42Z83xxxA
- ECU (Initiator / Car Anchor): flashed with digital_key_car_anchor_cs_freertos
- Transponder (Reflector / Device): flashed with digital_key_device_cs_freertos
- Both devices are on the custom PCB design

Issue:
On the initiator side (ECU / car anchor), we consistently receive RADE error code 1 during Channel Sounding procedures. RTT distance measurement runs correctly on both sides, but the RADE-based distance calculation fails at the initiator.

Questions:
1. Is RADE distance calculation supported on KW47B42Z83AFTB (no LCE) with the current SDK?
2. Does error code 1 indicate that LCE hardware is required but absent, or is there a software fallback available?
3. Are there any known configuration flags in app_preinclude.h or the CS profile layer that need to be set for RADE on a non-LCE variant?

Please let us know if additional logs or configuration files would be helpful.

Best regards
Christian

BLE-NFC  BLUETOOTH-BEACON 

0 Kudos
Reply
1 Reply

379 Views
Ricardo_Zamora
NXP TechSupport
NXP TechSupport

Hello,

 

Hope you are doing well. Is there any particular reason to use an IC version without LCE.

Anyways, I would recommend you checking this section from the SDK documentation: Enabling RADE v1 Usage (non-LCE) — MCUXpresso SDK Documentation

 

Best Regards,

Ricardo

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2362466%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERADE%20Error%20(Code%201)%20on%20KW47B42Z83AFTB%20%E2%80%94%20digital_key_car_anchor_cs_freertos%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2362466%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%26nbsp%3BHi%20NXP%20Support%20Team%2C%3C%2FP%3E%3CP%3EWe%20are%20using%20the%20%3CSTRONG%3EKW47B42Z83AFTB%3C%2FSTRONG%3E%20on%20a%20custom%20PCB%20for%20both%20ECU%20(anchor%2Fcar%20side)%20and%20Transponder%20(device%20side)%20roles.%3C%2FP%3E%3CP%3ESetup%3A%3CBR%20%2F%3E-%20SDK%3A%20%3CSTRONG%3ESDK_25_12_00_KW47B42Z83xxxA%3C%2FSTRONG%3E%3CBR%20%2F%3E-%20ECU%20(Initiator%20%2F%20Car%20Anchor)%3A%20flashed%20with%20%3CSTRONG%3Edigital_key_car_anchor_cs_freertos%3C%2FSTRONG%3E%3CBR%20%2F%3E-%20Transponder%20(Reflector%20%2F%20Device)%3A%20flashed%20with%20%3CSTRONG%3Edigital_key_device_cs_freertos%3C%2FSTRONG%3E%3CBR%20%2F%3E-%20Both%20devices%20are%20on%20the%20custom%20PCB%20design%3C%2FP%3E%3CP%3EIssue%3A%3CBR%20%2F%3EOn%20the%20initiator%20side%20(ECU%20%2F%20car%20anchor)%2C%20we%20consistently%20receive%20%3CSTRONG%3E%3CEM%3ERADE%20error%20code%201%3C%2FEM%3E%3C%2FSTRONG%3E%20during%20Channel%20Sounding%20procedures.%20RTT%20distance%20measurement%20runs%20correctly%20on%20both%20sides%2C%20but%20the%20RADE-based%20distance%20calculation%20fails%20at%20the%20initiator.%3C%2FP%3E%3CP%3EQuestions%3A%3CBR%20%2F%3E1.%20Is%20RADE%20distance%20calculation%20supported%20on%20KW47B42Z83AFTB%20(%3CSTRONG%3Eno%20LCE%3C%2FSTRONG%3E)%20with%20the%20current%20SDK%3F%3CBR%20%2F%3E2.%20Does%20error%20code%201%20indicate%20that%20LCE%20hardware%20is%20required%20but%20absent%2C%20or%20is%20there%20a%20software%20fallback%20available%3F%3CBR%20%2F%3E3.%20Are%20there%20any%20known%20configuration%20flags%20in%20app_preinclude.h%20or%20the%20CS%20profile%20layer%20that%20need%20to%20be%20set%20for%20RADE%20on%20a%20non-LCE%20variant%3F%3C%2FP%3E%3CP%3EPlease%20let%20us%20know%20if%20additional%20logs%20or%20configuration%20files%20would%20be%20helpful.%3C%2FP%3E%3CP%3EBest%20regards%3CBR%20%2F%3EChristian%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fc-pwmxy87654%2FBLE-NFC%2Fpd-p%2FBLE-NFC%22%20class%3D%22lia-product-mention%22%20data-product%3D%222717-1%22%20target%3D%22_blank%22%3EBLE-NFC%3C%2FA%3E%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fc-pwmxy87654%2FBLUETOOTH-BEACON%2Fpd-p%2FBLUETOOTH-BEACON%22%20class%3D%22lia-product-mention%22%20data-product%3D%222575-1%22%20target%3D%22_blank%22%3EBLUETOOTH-BEACON%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2362577%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20RADE%20Error%20(Code%201)%20on%20KW47B42Z83AFTB%20%E2%80%94%20digital_key_car_anchor_cs_freertos%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2362577%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EHope%20you%20are%20doing%20well.%20Is%20there%20any%20particular%20reason%20to%20use%20an%20IC%20version%20without%20LCE.%3C%2FP%3E%0A%3CP%3EAnyways%2C%20I%20would%20recommend%20you%20checking%20this%20section%20from%20the%20SDK%20documentation%3A%20%3CA%20href%3D%22https%3A%2F%2Fmcuxpresso.nxp.com%2Fmcuxsdk%2Flatest%2Fhtml%2Fmiddleware%2Fwireless%2Fbluetooth%2Fdoc%2FBluetooth%2520Low%2520Energy%2520Localization%2520Application%2520Note%2Ftopics%2Fdisabling_lce.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EEnabling%20RADE%20v1%20Usage%20(non-LCE)%20%E2%80%94%20MCUXpresso%20SDK%20Documentation%3C%2FA%3E%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBest%20Regards%2C%3C%2FP%3E%0A%3CP%3ERicardo%3C%2FP%3E%3C%2FLINGO-BODY%3E