Skip to main content
tabekb
Associate III
June 6, 2017
Solved

SPWF04S File print issue

  • June 6, 2017
  • 2 replies
  • 933 views
Posted on June 06, 2017 at 09:51

Hi!

I am using the SPWF04S module configured in MiniAP mode. I've created a file in RAM memory using the AT+S.FSC command.

I am reading the file using the AT+S.FSP command. After about 450-500 successfully readings, the module responds with Low Memory and resets itself (watchdog) after 20 seconds. Sometimes the respond is 'WIND:8:Hard Fault:ConUart:0002b290:20030000:07fd5003:08023588:47938cc4:fb3f49b6:080bb3e0:21000000' instead of Low Memory.

The same happens if I am creating the file using POST messages to the module. In this case I have the following steps:

1. I send this from client PC: curl -i -X POST -H 'Content-type: multipart/form-data' -F 'data=@FileSetX' 172.10.20.1

2. I read the module using 'AT+S.FSP=FileSetX,,'. The content of the file are read correctly.

3. Repeat 1 and 2. After about 400-500 success, the module is blocked (Low Memory / Hard Fault or maybe something else...)

Thanks.

    This topic has been closed for replies.
    Best answer by Gerardo GALLUCCI
    Posted on June 08, 2017 at 14:55

    Thanks Tarek, bug solved!

    Fix will be part of FW1.1.0

    2 replies

    Gerardo GALLUCCI
    ST Employee
    June 6, 2017
    Posted on June 06, 2017 at 20:28

    Hi,

    please attach here content of AT+S.GCFG command. RAM disk is static, so, cannot use more than that amount of RAM...

    Thanks for 500 tests

    Ciao

    jerry

    tabekb
    tabekbAuthor
    Associate III
    June 7, 2017
    Posted on June 07, 2017 at 08:21

    Hi!

    Probably I was not clear enough. In the first case, I am sending AT+S.FSC command to create a file only ONCE. After that I am reading that file every second. After about 500 readings the issue appear. This should not be a RAM size problem, I am just reading a file containing 5 characters... This is a real situation, reading a file how many time you want should not be limited.

    My purpose with 500 tests was to test my application not the module, but I found this issue on the module.

    Here follows the AT+S.GCFG:

    AT-S.List

    AT-S.Var:nv_manuf=ST

    AT-S.Var:nv_model=SPWF04SA

    AT-S.Var:nv_serial=0317<06103

    AT-S.Var:nv_wifi_macaddr=00:80:E1:BD:D5:40

    AT-S.Var:standby_time=10

    AT-S.Var:standby_enabled=0

    AT-S.Var:sleep_enabled=0

    AT-S.Var:etf_mode=0

    AT-S.Var:blink_led=1

    AT-S.Var:ext_volume=3

    AT-S.Var:aes128_key=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:user_desc=xxx

    AT-S.Var:python_script=3:/uPython_test.py

    AT-S.Var:python_memsize=32

    AT-S.Var:console_enabled=1

    AT-S.Var:console_speed=115200

    AT-S.Var:console_hwfc=0

    AT-S.Var:console_echo=0

    AT-S.Var:console_errs=2

    AT-S.Var:console_winds=2

    AT-S.Var:console_verbose=1

    AT-S.Var:console_repeater=0x21

    AT-S.Var:console_delimiter=0x2C

    AT-S.Var:console_wind_off_low=0x00000000

    AT-S.Var:console_wind_off_medium=0x00000000

    AT-S.Var:console_wind_off_high=0x00000000

    AT-S.Var:wifi_tx_msdu_lifetime=0

    AT-S.Var:wifi_rx_msdu_lifetime=0

    AT-S.Var:wifi_operational_mode=0x00000011

    AT-S.Var:wifi_beacon_wakeup=1

    AT-S.Var:wifi_beacon_interval=100

    AT-S.Var:wifi_listen_interval=0

    AT-S.Var:wifi_rts_threshold=3000

    AT-S.Var:wifi_ssid=45:4C:45:4B:54:52:41:5F:44:45:46:41:55:4C:54:5F:41:50:5F:42:44:44:35:34:30:00:00:00:00:00:00:00

    AT-S.Var:wifi_ssid_len=25

    AT-S.Var:wifi_txfail_thresh=5

    AT-S.Var:wifi_dtim_period=1

    AT-S.Var:wifi_add_tim_ie=0

    AT-S.Var:wifi_region=1

    AT-S.Var:wifi_ht_mode=1

    AT-S.Var:wifi_channelnum=6

    AT-S.Var:wifi_opr_rate_mask=0x003FFFCF

    AT-S.Var:wifi_bas_rate_mask=0x0000000F

    AT-S.Var:wifi_mode=3

    AT-S.Var:wifi_auth_type=0

    AT-S.Var:wifi_atim_window=0

    AT-S.Var:wifi_powersave=0

    AT-S.Var:wifi_tx_power=18

    AT-S.Var:wifi_rssi_thresh=0

    AT-S.Var:wifi_rssi_hyst=0

    AT-S.Var:wifi_ap_idle_timeout=120

    AT-S.Var:wifi_beacon_loss_thresh=10

    AT-S.Var:wifi_priv_mode=0

    AT-S.Var:wifi_wep_keys[0]=31:32:33:34:35:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:wifi_wep_keys[1]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:wifi_wep_keys[2]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:wifi_wep_keys[3]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:wifi_wep_key_lens=05:00:00:00

    AT-S.Var:wifi_wep_default_key=0

    AT-S.Var:wifi_wpa_psk_raw=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

    AT-S.Var:wifi_wpa_psk_text=

    AT-S.Var:wifi_eap_identity=identity

    AT-S.Var:

    mailto:wifi_eap_anon_identity=anonymous@identity.org

    AT-S.Var:wifi_eap_passwd=password

    AT-S.Var:wifi_eap_type=0

    AT-S.Var:wifi_eap_skip_datechecks=0

    AT-S.Var:wifi_wps_walk_time=120

    AT-S.Var:wifi_wps_pin=1234567

    AT-S.Var:ip_sock_memsize=1

    AT-S.Var:ip_sock_threshold=0

    AT-S.Var:ip_dhcp_lease_time=120

    AT-S.Var:ip_macfilter=00:00:00:00:00:00

    AT-S.Var:ip_num_clients=5

    AT-S.Var:ip_allow_port_scans=1

    AT-S.Var:ip_use_v6=1

    AT-S.Var:ip_use_dhcpd=1

    AT-S.Var:ip_use_httpd=1

    AT-S.Var:ip_use_tftpd=1

    AT-S.Var:ip_use_dhcpc=2

    AT-S.Var:ip_hostname=DEFAULT_AP_BDD540

    AT-S.Var:ip_apdomainname=captiveportal.net

    AT-S.Var:ip_apredirect=index.html

    AT-S.Var:ip_ipaddr=172.10.20.1

    AT-S.Var:ip_netmask=255.255.255.0

    AT-S.Var:ip_gw=192.168.0.1

    AT-S.Var:ip_dns1=208.67.222.222

    AT-S.Var:ip_dns2=208.67.220.220

    AT-S.Var:ip_local=0:0:0:0:0:0:0:0

    AT-S.Var:ip_dns1v6=0:0:0:0:0:0:0:0

    AT-S.Var:ip_dns2v6=0:0:0:0:0:0:0:0

    AT-S.Var:ip_dhcp_timeout=20

    AT-S.Var:ip_ntp_server1=ptbtime1.ptb.de

    AT-S.Var:ip_ntp_server2=ntp0.ipv6.fau.de

    AT-S.Var:ip_ntp_refresh=3600

    AT-S.Var:ip_ntp_startup=1

    AT-S.Var:ip_mdns_domain_name=SPWF04S-Default

    AT-S.Var:ip_mdns_device_name_ttl=120

    AT-S.Var:ip_mdns_services_name=SPWF04S-WebSrv SPWF04S-TFTPSrv

    AT-S.Var:ip_mdns_services_prot=_http._tcp _tftp._udp

    AT-S.Var:ip_mdns_services_keys=dev1 dev2

    AT-S.Var:ip_mdns_services_vals=number1 number2

    AT-S.Var:ip_mdns_services_port=80 69

    AT-S.Var:ip_mdns_services_ttl=120 60

    AT-S.Var:ip_mdns_startup=01:01

    AT-S.OK

    Thanks

    Gerardo GALLUCCI
    ST Employee
    June 8, 2017
    Posted on June 08, 2017 at 14:55

    Thanks Tarek, bug solved!

    Fix will be part of FW1.1.0