• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 41 subscribers
  • Views 740 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.

RTOS/WL1835MODCOM8B: RTOS/WL1835MODCOM8B

vaishali sachdeva
Prodigy 190 points
Part Number: WL1835MODCOM8B
Other Parts Discussed in Thread: WL1835

Tool/software: TI-RTOS

Hello,

I am testing ack policy on wl1835 module connected to am335x eval board.

I was able to test 'Block Ack' ack policy by configuring wl1835 as AP and I observed 'block ack' packets on wireshark.

But, when I tried testing 'No Ack', the ack packets were observed on wireshark. I tried by configuring wl1835 as AP as well as station.

In both the cases, ack packets were observed on wireshark.

My question is :

1) Is this the expected behaviour? If yes, why ? If not, what should be done to test 'No ack' on wl1835 ?

--

Thanks.

  • 0
    TI__Mastermind 20285 points
    Hi,

    The ack packets are automatically generated by the firmware of wl18xx and not by the driver/os.
    Why would you want to disable them? This is not something you should do.

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Prodigy 190 points
    Hello Eyal,

    I am testing the ACK POLICY and as I can make out in the drivers (file: drivers/net/wireless/ti/wlcore/conf.h),
    there are three ack policies supported i.e LEGACY, BLOCK and NO ACK.
    I can see the behaviour of BLOCK ACK and wanted to test NO ACK policy.
    Is it TI firmware that is stopping me?

    As per your response, I should not try this testing. My query is Will that break/cause hamper to the board or what is
    the reason for stopping me from testing NO ACK? Standard IEEE802.11 mentions NO ACK as one of the policies.

    Thanks,
    Vaishali
  • 0 in reply to vaishali sachdeva
    TI__Prodigy 730 points

    Vaishali,

    On the RX side we surely support NO ACK policy as the standard defines. Meaning if we receive a frame with NO ACK policy we won't reply with an ACK.

    On the TX side we have an option to configure the policy per tid from the wlconf tool (see below).

    Meaning the frame we transmit will be generated with the configured ACK policy.

    core.tx.tid_conf0.ack_policy = 0x00
    core.tx.tid_conf1.ack_policy = 0x00
    core.tx.tid_conf2.ack_policy = 0x00
    core.tx.tid_conf3.ack_policy = 0x00
    core.tx.tid_conf4.ack_policy = 0x00
    core.tx.tid_conf5.ack_policy = 0x00
    core.tx.tid_conf6.ack_policy = 0x00
    core.tx.tid_conf7.ack_policy = 0x00

    Guy