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.

RTTT on WL1837

Other Parts Discussed in Thread: WL1837, WL1835MOD, WL18XXCOM82SDMMC

We are trying to set up a testing set on a WL1837 using RTTT. For some reason the UART communication fails with the following error message (which is the same if nothing is connected at all):

"Connection failed: Calling_ConnectTarget returned 4"

The setup is as following:

- Target is our own board with a Jorjin WL1837 module
- As described in WL183x manual, IRQ_WL is pulled-up with 10k to its own 1.8V supply to enable WL_RS232_TX/RX
- WL_RS232_TX/RX connected to PC via a FTDI TTL-232R-3V3 cable (modified for 1.8V). Nothing else on these lines.

We can confirm with a scope that the UART cable transmits 1.8V serial data when FTTT tries to connect. However the TX line from the chip is 0V. Also, IRQ_WL is at 0V despite the pull-up, but I assume it's pulled low by WL1837.

Have we forgotten something?
Any hints on how to debug this?

Best, Jon

  • Hi Jon,

    I will check with the RTTT experts and get back to you...

    Regards,
    Gigi Joseph.

  • Hi Jon,

    Please verify the below:

    (1) IRQ_WL = 1, UART_DBG_BT = 1, AUD_OUT_BT = 0
    (2) These lines should be stable at the respective voltage in order to enter debug mode.
    (3) The RX line is coming all the way up to the device.
    (4) Baud rate:115200 or 921600
    (5) Board type: HDK

    Regards,
    Gigi Joseph.

  • Gigli,

    1. IRQ_WL = 1 (I wrote earlier that it was 0, but it seems that the MCU took control over the WLAN module. Was under the impression that it would stay in "debug" mode as long as IRQ was pulled up but it seems not?)

    UART_DBG_BT = 1 (pin not connected to anything)

    AUD_OUT_BT = not connected, can't measure.

    2. But IRQ_WL is the only line we actually need to hold in this state, right? The other two are not connected.

    3. Can't confirm, but looks OK in the PCB layout anyway.

    4, 5: tried both combinations here, no luck.

    Best, Jon

  • In fact, WLAN TX seems to be floating/input, so we suspect the chip hasn't even entered debug mode. Also, if we let our application start, it will take over and the wifi will initialise. Isn't it supposed to stay in debug?

    /j

  • Hi Jon,

    Please let me know if it is still relevant.

    The debug mode means only IO’s that are pinmuxed to debug functionality like the RS232 and jtag so the wifi will initialize using SDIO if the processor will run.

    Regards,
    Gigi Joseph.

  • Hi Joseph,

    we are trying to get RTTT working with WL1835MOD + WL18xxCOM82SDMMC + onboard USB connection. It does not connect to the board (error 4) and firmware cannot be downloaded.

    While looking at the TP 3 and 4 WL RX/TX pins by oscilloscope, it seem that the baud rate stays at 115200 despite what you change in RTTT. It also echoes everything back (used also putty to check). WL_IRQ jumper is set, and BT works loud and clear with HCI Tester, and other jumpers are as they should be ( I guess). Physically board seem to be OK.

    Some questions:

    1. Do BT UART settings have anything to do with WLAN RS232? We tried to change the BT UART baud rate to 921600 and it did not make any effect for WLAN RS232.

    2. What else jumpers must be set other than for successfully operated BT? 3V3/1V8 jumpers are as for 3V3 from USB, also tried when connected to SDIO (if it needs some power other than USB)

    3. What should be board type in RTTT when using WL1835MOD + WL18xxCOM82SDMMC?

    4. In the manual it is said that "The default baud rate is 921600 but can be updated to 3M." How this can be done? RTTT version is 2.0.0.55, running on W7.

    - v
  • Any advice please on these RTTT settings? Tried also to re-install the software but it did not have any effect.

    Is there older versions of RTTT available if the serial speed problem has not been previously?

  • Hi Vincent,

    Only latest RTTT on TI.com supports 3M.
    For the debug mode you can refer to the SDMMC user guide.

    Regards,
    Gigi Joseph.
  • Hi Joseph,

    and thanks for your answer. Could you please look at my previous comment, too, regarding 115200 baud rate issue ?
    Still we cannot get the device working with latest RTTT.

    From where I can find the manual commands for WL_RS232 commands?

    -v
  • Hi Vincent,

    The baud rate in RTTT needs to be aligned with the default baud rate of the device - it doesn't program the device baud rate. Think of this window like any other serial terminal (i.e. PuTTy, HyperTerminal, etc.), where you are making sure the settings of the software + hardware match.

    In order to make your PC + SDMMC Adapter + COM8 board setup work, make sure to check your jumper configurations on the SDMMC Adapter Board as described here:

    And configure RTTT tool as Joseph described, keeping in mind that 4 serial ports should show up, in this order: BT Debug, BT Logger, WLAN Debug, WLAN logger:

    - Serial Port: [3rd COM port - check device manager]

    - Baud rate: 921600

    - Timeout: 1000 ms

    - Board: HDK

    Please let us know if this answered your question by clicking Verified Answer below.

    Best,

  • In addition:

    To change the baudrate, you can use HCITester.

    1. Configure HCITester as follows with View -> Options

    - [1st COM Port - check Device manager]

    - 115200

    - Hardware

    - HCILL

    2. Load the XML file in the command library found in the BT service pack.

    3. Load the INIT script found in the BT service pack.

    4. Use the following command: 

    
    
    Send_HCI_VS_Update_Uart_HCI_Baudrate 0xFF36, 3000000
    Wait_HCI_Command_Complete_VS_Update_Uart_HCI_Baudrate_Event 5000, any, HCI_VS_Update_Uart_HCI_Baudrate, 0x00

    NOTE: To continue using HCITester, you will have to go back into the View -> Options menu and change the baud rate to whatever you have updated it with, and click Apply.

    5. Now when you go back to RTTT, change the UART speed to 3 Mbps, and it will work. (I tested it)

    NOTE: Upon power cycle, the default UART baud rate will be restored.

    Best,

    Lina

  • Hi Lina, and thanks for your answer.

    Despite your instructions, RTTT is still not working with the board. All jumpers have been verified several times and must be then correct. BT is working fine.

    When attaching the jumper J4 on WL1835MOD board, the signal will not be pulled up, i.e. it stays at zero. This means that the device will not go to WLAN debug mode?

    Another strange thing is that when using Putty, WL_RS232 echoes everything back regardless of terminal speed. Using HCI tester to change the UART speed it makes no effect (I assume that the setting should be then common for both BT and WL UART?).

    Stuck at the moment, what could be wrong other than faulty board?

    -v

  • Hi Vincent,

    The WLAN_IRQ signal is required to be pulled up in order to put the device in debug mode. Once the device initializes, this pin is pulled low, which is why you see the zero. 

    What are the statuses of the LEDs on your SDMMC Adapter board? (i.e. WL_EN_LED, BT_EN_LED, VIO_LED and SYS_3V3)

    Also, it might speed up debug if you could send screenshots/pictures of your Device Manager window (when device is plugged in), RTTT tool configurations, and a picture of the top of the boards (plugged in).

    Best,

  • It was finally found the board to be somehow faulty. It works well with BT but not with WLAN debug mode. Got a new board for loan which works fine from first start.

    Jumper J4 on WL1835MOD board seem to be have no effect when connecting with RTTT, so it can be left out. RTTT starts first negotiating at 115200 baud and then raises the speed to 921600 as selected from the settings. Board type should be HDK with SD adapter board.

    One notice is that after loading the firmware, if you crash or shut down RTTT, it will not connect the board until powered down and up.

    Thanks for Lina supporting!

    -v

    Edit:

    "The jumper must be installed to put this device in debug mode. The reason that it works without the jumper installed, is because there is an internal pullup on the SDMMC board. However, there is also an internal pull-down in the wilink chip, so you are floating. Therefore, it will work sometimes and not work other times."

    This did not have any effect in my case but was confusing as the signal was low even pulled high with the jumper and still measured as 0V. So please put a jumper.