Shop OBEX P1 Docs P2 Docs Learn Events
Latest firmware for the 32420 Wi-Fi module — Parallax Forums

Latest firmware for the 32420 Wi-Fi module

JimFouch2JimFouch2 Posts: 26
in Propeller 2
After watching the Programming your P2 with the WI-Fi module zoom meeting on the 16th, I bought one. It came with firmware from 2016.

I've looked high and low and can not find any newer firmware on Parallax's site. Both the DIP and SIP modules' pages have the same one from 2016.

Does anyone know where I can find the latest?

Comments

  • VonSzarvasVonSzarvas Posts: 3,280
    Hi @JimFouch2

    The latest version is here at the moment: https://drive.google.com/drive/folders/11KquS93woptxTfJMx8J7WY4tSFkeH9Oq

    httpd_1218.ota

    Upload it using the firmware menu in the WiFi module web-gui.
  • dgatelydgately Posts: 1,621
    I've updated 3 of the Parallax WiFi modules with the latest firmware. One succeeds, while the other two have issues:

    Module #1. Updates firmware, without issue, shows the P2 Drag/Drop Loader option, and I can upload binaries. SUCCESS!

    Module #2. Updates firmware, displays "Version: v1.3 (2020-12-17 21:10:29 6-g6c70722)", but does not display the P2 Drag/Drop Loader option:
    Home.jpg
    No P2 Drag/Drop option:
    Settings.jpg
    Debug Log (note: 791728> URL = /wx/setting?name=cmd-p2-ddloader
    791728> GET args = name=cmd-p2-ddloader
    791728> GET 'cmd-p2-ddloader' --> '0'): 
    74:60652, using pool slot 0
353421> URL = /wx/setting?name=cmd-events
353421> GET args = name=cmd-events
353421> GET 'cmd-events' --> '0'
353427> Pool slot 0 is done. Closing.
353427> Pool slot 0: socket closed.
791688> Conn req from  10.0.0.74:60924, using pool slot 0
791690> URL = /wx/setting?name=module-name
791690> GET args = name=module-name
791691> GET 'module-name' --> 'gatorWX173'
791697> Pool slot 0 is done. Closing.
791698> Pool slot 0: socket closed.
791707> Conn req from  10.0.0.74:60925, using pool slot 0
791709> URL = /wx/setting?name=version
791709> GET args = name=version
791710> GET 'version' --> 'v1.3 (2020-12-17 21:10:29 6-g6c70722)'
791718> Pool slot 0 is done. Closing.
791718> Pool slot 0: socket closed.
791726> Conn req from  10.0.0.74:60926, using pool slot 0
791728> URL = /wx/setting?name=cmd-p2-ddloader
791728> GET args = name=cmd-p2-ddloader
791728> GET 'cmd-p2-ddloader' --> '0'
791735> Pool slot 0 is done. Closing.
791736> Pool slot 0: socket closed.
793228> Conn req from  10.0.0.74:60927, using pool slot 0
793229> URL = /wx/setting?name=cmd-p2-ddloader
793229> GET args = name=cmd-p2-ddloader
793230> GET 'cmd-p2-ddloader' --> '0'
793236> Pool slot 0 is done. Closing.
793237> Pool slot 0: socket closed.
793349> Conn req from  10.0.0.74:60928, using pool slot 0
793351> URL = /log/text?start=0
793351> GET args = start=0
    Can this module be reset & the firmware reapplied? How?

    Module #3. Updates firmware, displayed correct version, on restart now fails to show up as an AP or STA on my network. No amount of twiddling the AP connections resets to AP-only mode! I will connect to this one via USB dongle and see if it responds as a USB device.

    dgately
    Home.jpg
    759 x 383 - 68K
    Settings.jpg
    757 x 547 - 84K
  • avsa242avsa242 Posts: 432
    Hi Dennis,

    For module #3, when you say:
    Module #3. Updates firmware, displayed correct version, on restart now fails to show up as an AP or STA on my network. No amount of twiddling the AP connections resets to AP-only mode! I will connect to this one via USB dongle and see if it responds as a USB device.

    do you mean you've tried to reset the module by grounding the PGM pin 4 times (within 2sec, I think?)?
    You may also be able to attach a serial link to the DBG pin to see if there's any useful info logged there, if it's configured.

    Cheers,
    Jesse
  • dgatelydgately Posts: 1,621
    avsa242 wrote: »
    do you mean you've tried to reset the module by grounding the PGM pin 4 times (within 2sec, I think?)?
    You may also be able to attach a serial link to the DBG pin to see if there's any useful info logged there, if it's configured.
    Yes, tried PGM pin grounding (which has worked on past), to no avail.
    Attached a serial link to DBG and have touched RST to GND... It spits out garbage text (I have tried many normal BAUD rates as well as 2_000_000 & 3_000_000, in case I had set that initially) to the terminal.

  • dgatelydgately Posts: 1,621
    Module #2 seems to have re-awoken and is working... I moved it from P2ES to P2Edge, un-connected its propPlug, powered down and back up. Now it displays P2 Drag/Drop Loader and is able to upload binaries.

    2 out of 3 is good enough for now!
  • VonSzarvasVonSzarvas Posts: 3,280
    #2 seems like a case of the browser caching old web pages. Shift+F5 would resolve, or waiting a while.
  • dgatelydgately Posts: 1,621
    VonSzarvas wrote: »
    #2 seems like a case of the browser caching old web pages. Shift+F5 would resolve, or waiting a while.
    Yeah, quite possible!

  • JimFouch2JimFouch2 Posts: 26
    Anyone know if there is a virtual COM port software that will allow you to treat this like a normal COM port. As in, allows older software that only supports COM ports to see this as a normal com port but send receive characters to the Wi-Fi module.

    I've seen a few software options, but they are like $100-$900 depending on how many ports you open.
  • iseriesiseries Posts: 1,454
    @JimFouch2 ,

    Sure, you can use the Prop Plug and connect up the wires or use any TTL-232R-3v3 module to talk to the WiFi module.

    The unit must only supply 3.3v and that includes the pins. This is what I use to program the module. I have and LDO in-between that converts the 5 volts to 3.3.

    If you use the SIP version you can power it with 5 volts.

    Mike
Sign In or Register to comment.