Is it necessary to update the ATWINC1500 firmware to use the AT commands?

Go To Last Post
9 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi.
 
I am using the ATWINC1500 via RS232 and sent the start command:
 
A5 01 F2 00 00 0C 00 0C 00 61 2F 52 EF

And I get the following response:

(0)NO CORTUS app
(0)(M2M)DriverInfo: None. Assuming 19.3.0
(0)Chip ID = 1524b0
(0)Flash ID = b512302c, Size = 4 MBit
(10)EFUSE:MAC
(10)MAC_ADDR = 8F:F4:35:AB:8C:13
(10)Shared buff static: 0, 5, 5, 22, 9, 10
(20)NMI M2M SW VERSION 19.5.2 SVNREV 14274
(30)NMI MIN DRV VERSION 19.3.0
(30)Firmware SVN URL branches/WIFIIOT-1660_19_5_2_RC7
(30)Built at Jan 26 2017 22:13:34
(40)ROM LIB VER_2
(40)__AES_HW_ENGINE__
(40)(M2M)LOAD SEC
(50)(TLS)TLS Session Size= 1884
(70)PSM_OFF
 
But according to the document AT commands should get a response something similar to the following:

Response +OK+AT=AT:,FW:,ChipID:,RFRev

After the above, I send the "Check the AT Command Firmware" as follows:
 

 case CHECK_AT_COMMAND_FIRMW:{
            app_uart1.transmissionBuffer[0x00] = 'A';
            app_uart1.transmissionBuffer[0x01] = 'T';
                        
            app_uart1.transmissionBuffer[0x02] = 0x0D;
            app_uart1.transmissionBuffer[0x03] = 0x0A;
            
            app_uart1.sizeToTransmit = 0x04;
            break;
        }

But there is no response from the module.

In advance any comments or suggestions are welcome.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The support of MCHP indicates that there will be no support or updates for the AT commands via RS232, They have provided the old files to work:

"The AT Command application is no more supported officially, however if you want to work with the v19.4.4 version of WINC1500 + AT Command and limited support please use the the attached files for the configuration. You can find all the files and example applications mentioned in the AT Command document in the attachment"
 
 
My options now are the following:
 
1. Work with the old firmware of the module only for now.
 
2. Wait for the update that someday, they will do it in the not too distant future in which you can send AT commands via SPI.
 
3. Modify the MLA libraries with PIC18F or PIC24F to adapt them to the PIC32.
 
4. Fight with the exessive code of the examples with Harmony.
 
I'm going to analyze option 3 until I get a USB to RS232 converter of quality, since the one that has its TX terminal from the PC generates a lot of noise.
 
Fabián

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Why not just use the SPI interface as-is? Unless, of course, you run out of available IO lines. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

acpie360 wrote:

Why not just use the SPI interface as-is? Unless, of course, you run out of available IO lines. 

 

I want to use the AT mode since I only want to send some short-length frames via Telnet, with time I could implement higher utilities.
The examples in Harmony are so complex and I must dig in the code to remove what is not useful and also the PIC32 I use does not have enough data memory for the Harmony example.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There is no need to use Harmony at all. The standalone WINC1500 library can be found here: https://github.com/adafruit/Adaf... and yes, you do need to port it to PIC32. This means you need to provide PIC32 version of SPI read/write function, interrupt handler for the WINC's IRQ line and some other simple functions like the reset control, delay loop, etc.. That's pretty much all the driver code you need. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

acpie360 wrote:

There is no need to use Harmony at all. The standalone WINC1500 library can be found here: https://github.com/adafruit/Adaf... and yes, you do need to port it to PIC32. This means you need to provide PIC32 version of SPI read/write function, interrupt handler for the WINC's IRQ line and some other simple functions like the reset control, delay loop, etc.. That's pretty much all the driver code you need. 

Thank you very much for the suggestion, I wanted to avoid the work of migrating all the code, analyze what serves me and what is not useful and watching the model with AT commands I thought I could do something faster for something as simple as I want to do. Then, in the future, I thought about analyzing the model with the SPI libraries with greater emphasis.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

DominusDRR wrote:

The support of MCHP indicates that there will be no support or updates for the AT commands via RS232, They have provided the old files to work:

"The AT Command application is no more supported officially, however if you want to work with the v19.4.4 version of WINC1500 + AT Command and limited support please use the the attached files for the configuration. You can find all the files and example applications mentioned in the AT Command document in the attachment"
 
 
My options now are the following:
 
1. Work with the old firmware of the module only for now.
 
2. Wait for the update that someday, they will do it in the not too distant future in which you can send AT commands via SPI.
 
3. Modify the MLA libraries with PIC18F or PIC24F to adapt them to the PIC32.
 
4. Fight with the exessive code of the examples with Harmony.
 
I'm going to analyze option 3 until I get a USB to RS232 converter of quality, since the one that has its TX terminal from the PC generates a lot of noise.
 
Fabián

Hi! May you please send the firmware files that you received? 

 

Best regards!

Luís Henrique

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Note that  DominusDRR  hasn't been active here since 2018 - you may be better requesting the files direct from Microchip Support:

 

https://microchipsupport.force.com/s/

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi. Yes, I will do that. Thank you!

Luís Henrique