• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 1903 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CE Certification Radiated RF Immunity Test Issue on 2.4GHz WiFi - Wilink8 WL1833 based module

M_E
Prodigy 130 points
Other Parts Discussed in Thread: WL1833, AM3352

We have a radiated RF immunity issue with the 2.4GHz WiFi interface on our device incorporating the Jorjin WG7833-B0, 2.4GHz/5GHz SISO WiFi and 2.4GHz Bluetooth module based on the TI WL1833. We are looking for guidance in debugging the issue, particularly in obtaining firmware/driver based debug information.

In performing radiated RF immunity testing as detailed in the ETSI standard EN 301 489-1 Clause 9.2 (Radio frequency electromagnetic field (80 MHz to 6 000 MHz)) we see a failure of the 2.4GHz WiFi link at specific frequencies which appear to be half harmonics of the 2.4GHz WiFi channel operating frequency being used.  Testing is required to be performed at 3V/m.

WiFi Channel      Operating Frequency      Failing RF Immunity Frequency Band       Failing Test Level

CH1                      2412MHz                            1195MHz + 1219MHz                                   2V/m

CH12                    2467MHz                            1228MHz + 1240MHz                                   2V/m

During the immunity test, we connected two devices both with WG7833-B0 parts with one set as an Access Point and the other in Station mode, we then used a ping between the two devices to verify the communications link was maintained during the test.  The unit under test is the access point and exposed to the RF field, the station mode device is positioned away from the RF field and when functioning without the RF field applied the link functions as expected, similarly, at other frequencies outside the affected bands the device operates as expected during the immunity condition.

Whilst we haven’t performed extensive testing we didn’t see an issue with the 5GHz WiFi or 2.4GHz Bluetooth links which were both active during the immunity test.

The Wilink8 firmware revisions we are using are:

WIFI_FWREV="8.9.0.0.78"

WIFI_PHY_FWREV="8.2.0.0.242";

Our device is based on the TI Sitara AM3352 1GHz processor and is running Yocto Linux 2.3.  

QUESTIONS:

1.) We are planning to perform additional testing to better understand the issue and would like to obtain detailed debug information from the device firmware/driver, would you please advise how this is best undertaken?  Ideally, this will be a software based solution rather than requiring hardware modifications.

2.) Do TI have any recommendations for debugging the issue?

3.) Have TI performed CE radiated RF immunity testing on WL18xxMOD devices with the latest TI firmware revision?  If so would you please provide the related test reports.

Please let me know if you require further information to assist with this issue. 

  • 0
    TI__Mastermind 27080 points
    Our RF expert with review and get back.. You can take Wilink firmware logs as described below -

    www.ti.com/.../swru435a.pdf

    Thanks
  • 0 in reply to Hari Nagalla
    TI__Genius 12740 points

    Hi,

    Yes we have passed the EN301489-1 requirement on the wilink module. The report is attached here:

    EH741330_R01_EN301489_Texas_WL18MODGI_0725.pdf

    Since this is  a Jorjin module you need to check with Jorjin if they pass this test on their module. IF they did, then you will need to look closer at your design to see where the issue is. This is a hard one to debug and its not really related to RF performance. I would suggest that you see if you can work with your test house if they have any ideas on how to solve the issue. Perhaps at the product level there is some additional isolation that can be done to help with the issue.

    Thanks,

    Riz

  • 0 in reply to Rizwan Murji
    Prodigy 130 points

    Hi

    We have taken a firmware log from the device using the TI glogger tool during the immunity condition(1233MHz with the device set as an AP on WiFi Channel 12 2467MHz), we see repeated messages for:

    ApBeaconDtim_BeaconSent

    Tx Beacon: Beacon Expiry. Consecutive Beacon Miss: 129

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x03DEA009, Role : 0, is sending beacon on FLID 2, with msi=634

    We don’t see any driver debug output during the immunity condition and our ping between the AP and a connected device stops, the device is not subjected to the immunity.   After quote a few of the beacon miss messages we see:

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x040F1009, Role : 0, is sending beacon on FLID 2, with msi=665

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0410A009, Role : 0, is sending beacon on FLID 2, with msi=666

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04123009, Role : 0, is sending beacon on FLID 2, with msi=667

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0413C00B, Role : 0, is sending beacon on FLID 2, with msi=668

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04155009, Role : 0, is sending beacon on FLID 2, with msi=669

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0416E009, Role : 0, is sending beacon on FLID 2, with msi=670

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04187009, Role : 0, is sending beacon on FLID 2, with msi=671

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x041A000A, Role : 0, is sending beacon on FLID 2, with msi=672

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x041B9009, Role : 0, is sending beacon on FLID 2, with msi=673

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x041D2009, Role : 0, is sending beacon on FLID 2, with msi=674

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x041EB009, Role : 0, is sending beacon on FLID 2, with msi=675

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04204009, Role : 0, is sending beacon on FLID 2, with msi=676

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0421D009, Role : 0, is sending beacon on FLID 2, with msi=677

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0423600B, Role : 0, is sending beacon on FLID 2, with msi=678

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0424F009, Role : 0, is sending beacon on FLID 2, with msi=679

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0426800B, Role : 0, is sending beacon on FLID 2, with msi=680

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04281009, Role : 0, is sending beacon on FLID 2, with msi=681

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0429A009, Role : 0, is sending beacon on FLID 2, with msi=682

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x042B300A, Role : 0, is sending beacon on FLID 2, with msi=683

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x042CC009, Role : 0, is sending beacon on FLID 2, with msi=684

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x042E5009, Role : 0, is sending beacon on FLID 2, with msi=685

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x042FE009, Role : 0, is sending beacon on FLID 2, with msi=686

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04317009, Role : 0, is sending beacon on FLID 2, with msi=687

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04330009, Role : 0, is sending beacon on FLID 2, with msi=688

    Then

    Rx_handleRxCompleteFrame

    FRAME_TYPE RX: AUTHENTICATION

    CommandParser

    At TSF=0x043AE8AB, called Command CMD_ADD_PEER

    Roles_AddPeerToAp

    Command Roles_AddPeerToAp Received!!, roleID=0, HLID=3, BSSIndex=0

    Links_AddPeerToAP

    Mgmt_seq: Adding new station on FLID 3

    Links_AddLinkContext

    At TSF=0x043ae8c5, link Added, flid 3, frid 0, WMM mode 0

    FwQueues_GetInitNonQoSSeqNum

    AP: Assigning non-qos init seq num 0x003c for flid 3 and global flid 1

    Aging_NotifyStationAdded

    flid = 3

    AP_Sleep_StationAddedNotify

    APSL-CD [0x043AE91E] RoleType=2

    CommandParser

    At TSF=0x043AEB83, called Command CMD_REMAIN_ON_CHANNEL

    Links_ROCProcedure

    mgmt_seq: ROC Command role id 0

    Roles_StartMgmtSeq

    start mgmt seq: roleId = 0, mgmtType=MGMT_SEQ_TYPE_ROC, mgmtId=0x400000, mgmtOngoing=0x400000

    Link_AddMgmtSequence

    Mgmt_seq: add request RoleIndex is 0 IsRocCommandExisted is 4194304

    Roles_AddRxProtectionRequest

    Add RX Protection Req: roleId = 0, requestType=MGMT_SEQ_TYPE_ROC, requestType=0x400000, mgmtOngoing=0x400000

    Links_ROCProcedure

    return immediate ROC - role is resumed

    Service_SetEventMbox

    At Tsf=0x043AEBCA, set Event REMAIN_ON_CHANNEL_COMPLETE_EVENT_ID, EventData (Byte1)= 0

    __SWI_Entry_EventMBox

    Event Vector=0x40000 (buffer=0)

    WriteInfoEle

    At TSF=0x043AF1DB, COMMANDS_WRITE_INFOELE_ENUM - ACX_UPDATE_INCONNECTION_STA_LIST

    AddInConnectionSTA

    Adding STA to In Connection STA List, MAC[3]=d8, MAC[4]=4a, MAC[5]=7c

    EvaluateTxExchStatus

    FRAME_TYPE TX: AUTHENTICATION

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04349009, Role : 0, is sending beacon on FLID 2, with msi=689

    Rx_handleRxCompleteFrame

    FRAME_TYPE RX: ASSOCIATION_REQUEST

    EvaluateTxExchStatus

    FRAME_TYPE TX: ASSOCIATION_RESPONSE

    CommandParser

    At TSF=0x043B9B67, called Command CMD_SET_PEER_STATE

    CommandParser

    At TSF=0x043BB010, called Command CMD_ADD_PEER

    Roles_AddPeerToAp

    Command Roles_AddPeerToAp Received!!, roleID=0, HLID=3, BSSIndex=0

    Links_AddPeerToAP

    Mgmt_seq: Adding new station on FLID 3

    RemoveInConnectionSTA

    In Remove STA from InConnection list - MAC[3]=d8, MAC[4]=4a, MAC[5]=7c

    WriteInfoEle

    At TSF=0x043BB298, COMMANDS_WRITE_INFOELE_ENUM - ACX_PEER_HT_CAP

    Links_WriteHtPeerCap

    Links_WriteHtPeerCap - flid 3 HT_CAP_SUPP_CHANNEL_WIDTH_SET 0

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0436200A, Role : 0, is sending beacon on FLID 2, with msi=690

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0437B009, Role : 0, is sending beacon on FLID 2, with msi=691

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04394009, Role : 0, is sending beacon on FLID 2, with msi=692

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x043AD00B, Role : 0, is sending beacon on FLID 2, with msi=693

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x043C600B, Role : 0, is sending beacon on FLID 2, with msi=694

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x043DF009, Role : 0, is sending beacon on FLID 2, with msi=695

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x043F8009, Role : 0, is sending beacon on FLID 2, with msi=696

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04411009, Role : 0, is sending beacon on FLID 2, with msi=697

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0442A009, Role : 0, is sending beacon on FLID 2, with msi=698

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x04443009, Role : 0, is sending beacon on FLID 2, with msi=699

    CommandParser

    At TSF=0x044B2FA6, called Command CMD_CANCEL_REMAIN_ON_CHANNEL

    Links_CROCProcedure

    mgmt_seq: CROC Command role id 0

    Link_RemoveMgmtSeq

    Mgmt_seq: Remove request Role 0 counter 0

    Roles_StoptMgmtSeq

    stop mgmt seq: roleId = 0, mgmtType=MGMT_SEQ_TYPE_ROC, mgmtId=0x400000, mgmtOngoing=0x0

    Link_RemoveMgmtSeq

    Mgmt_seq: remove sched request

    Roles_RemoveRxProtectionRequest

    Remove RX Protection Req: roleId = 0, requestType=MGMT_SEQ_TYPE_ROC, requestType=0x400000, mgmtOngoing=0x0

    Links_RocRequestCB

    Mgmt_seq: CB request ,request CB handle 33524 ,request handle 0 , MgmtSeqCnt 0 , CB reason is SCHED_REQ_CALLBACK_REASON_REMOVE_COMPLETE)

    Links_RocRequestCB

    Roc req remove succsefully !!!

    ApBeaconDtim_SendApBeaconDtim

    at TSF 0x0445C009, Role : 0, is sending beacon on FLID 2, with msi=700


    We want to eliminate firmware as a potential issue in this, as we find it unusual that an immunity applied at a half harmonic of the WiFi channel frequency is resulting in a degradation of receiver performance, we would expect the receiver to reject this signal.

    Thanks

    Malcolm

    Full glogger output attached.

    WG7833-B0 glogger Output.zip

  • 0 in reply to M_E
    TI__Genius 12740 points
    Hi Malcolm,

    IF you are passing the normal regulatory requirements as well as normal operation tests such as thruput, there should be no issue with the FW. Again, since this is a Jorjin module, you need to ensure you are using the FW as recommended by them as well as the correct .INI file.

    As far as the imunity test failure, we have passed this on the TI module. This may be something at the system level that you need to look into for passing the test. There is nothing in FW that can be done for such an issue as a system level solution would need to be investigated.

    Thanks,
    Riz