Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    maxdd
    @maxdd
    it seems an overflow to me
    if you see 32000 is the sum of the actual read second column till the error
    the working example reaches
    [httpc] Using actual read: 83 83
    27760 28499
    which is the size of the hello_world.bin file, mine since it is 356kb delivers an error
    Why a 27kb file is working while a 350 isn't
    or rather a "space" problem, since the same file is downloaded and flashed when using http
    Ed Johnson
    @edwin-n-johnson
    Hello. I'm trying to upgrade our devices over the air. We have about 40 devices in the field and 2 of them are not upgrading properly. Since they are in the field, I don't know much except that rfget_client_mode_update() returns -65537 (WM_E_HTTPC_TCP_CONNECT_FAIL). The call flow is rfget_client_mode_update() -> httpc_get() -> http_open_session() -> tcp_connect() -> connect() which returns some kind of error. Since majority of devices are working properly for many upgrades, I have confidence that URLs are being served properly. In addition, these 2 failing devices have worked previously as well. Can anyone help me understand or debug the problem? Does it have anything to do with wifi network, firewall, etc.?? Just not sure where to look...
    Ed Johnson
    @edwin-n-johnson
    @josecarballoGL @avsheth @anujdeshpande would any of you have any idea about my issue above?
    Jose Pablo Carballo
    @josecarballoGL
    @edwin-n-johnson This may sound too basic, but the way you are giving the device the upgrade URL, is it a too long URL? I remember some devices having trouble reading long url's because http_read_content() where I got the info from had to be called several times until everything was read. Just thinking out loud.. I don't know what your upgrade strategy is
    Ed Johnson
    @edwin-n-johnson
    @josecarballoGL thank you for the reply. I really appreciate it. No, I don't believe URL length is the issue for 2 reasons. 1) 38 devices work just fine with identical URL and identical initial firmware and 2) for the 2 failing devices, when a different wifi access point is used (i.e. the customer ships the device back to me and I put it on my network), then the same URL works just fine. So it really feels like something is wrong with the access point. But I can't understand why and since I don't have a failing network myself, this is very hard to debug. Does anyone know if there are any good wifi api's in the sdk to get more diagnostic information about the network? Like signal strength, etc.? As always, thanks in advance and after...
    maxdd
    @maxdd

    Question about I2C, using the default settings the clock speed appears to be 125khz (shouldn't it be 100Khz?)

    https://imgur.com/a/8G8UR

    Could it be the reason why my slave device on the other side is know ACKing the ACK bits?
    SCL probe had issue so signal quality is better from what you see here

    maxdd
    @maxdd
    is not* acking the write operation
    @edwin-n-johnson do other devices (smartphone/pc) download the firmware correctly when connected to that AP?
    Srisuryaprakash
    @Srisuryaprakash
    can anyone share any function to reboot or reset the application?
    Shellpry
    @Shellpry
    Anyone know how to query the WLAN firmware version from run time and send it out to a debug port?
    Jose Pablo Carballo
    @josecarballoGL
    /* Get the wifi firmware version extension string.
    • \note This API does not allocate memory for pointer,
    • It just returns pointer of WLCMGR internal static
    • buffer, So no need to free the pointer by caller.
      *
    • \return wifi firmware version extension string pointer stored in
    • WLCMGR
      /
      char
      wlan_get_firmware_version_ext();
    From wlan.h
    Shellpry
    @Shellpry
    Thanks!
    Jose Pablo Carballo
    @josecarballoGL
    You're welcome @Shellpry
    FirmwareEngineer
    @FirmwareEngineer
    @Prashant-Kmr , I'm facing same issue which you solved by yourself 2 times.
    Please share me how you can solve the issue.
    Actually I have followed the git guide only, there is no additional functions such as sensor,,,
    Using OpenOCD interface file ftdi.cfg
    Open On-Chip Debugger 0.9.0 (2015-05-19-12:06)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    adapter speed: 3000 kHz
    adapter_nsrst_delay: 100
    Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
    jtag_ntrst_delay: 100
    cortex_m reset_config sysresetreq
    sh_load
    Info : clock speed 3000 kHz
    Error: JTAG scan chain interrogation failed: all ones
    Error: Check JTAG interface, timings, target power, etc.
    Error: Trying to use configured scan chain anyway...
    Error: wmcore.cpu: IR capture error; saw 0x0f not 0x01
    Warn : Bypassing JTAG setup events due to errors
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Error: JTAG scan chain interrogation failed: all ones
    Error: Check JTAG interface, timings, target power, etc.
    Error: Trying to use configured scan chain anyway...
    Error: wmcore.cpu: IR capture error; saw 0x0f not 0x01
    Warn : Bypassing JTAG setup events due to errors
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Warn : Invalid ACK 0x7 in JTAG-DP transaction
    Error: Target not examined yet
    in procedure 'chip_id'
    in procedure 'reset' called at file "openocd.cfg", line 7
    in procedure 'ocd_bouncer'
    Volodymyr Shymanskyy
    @vshymanskyy
    Could anyone help me with the issue? marvell-iot/ez-connect-lite#9
    Looks pretty basic
    Volodymyr Shymanskyy
    @vshymanskyy
    OK, figured this out ;)
    Now the next challenge - can't build even simplest c++ file :(
    Volodymyr Shymanskyy
    @vshymanskyy
    OK
    I figured how to build C++ as well
    But it would be cool to have a default example
    Volodymyr Shymanskyy
    @vshymanskyy
    Just published results of my work: https://github.com/vshymanskyy/blynk-library-ez-connect
    This is an example of Blynk IoT App builder integration with EZ-Connect Lite SDK.
    Now we can use Blynk to create cool Apps for iOS, Android and Web
    This is still in early development, so reviews/contributions are welcome. Thanks! ; )
    Volodymyr Shymanskyy
    @vshymanskyy
    @anujdeshpande @josecarballoGL you might be interested!
    vienkmt
    @vienkmt
    I want use MQTT with this KIT
    have any body can help me?
    I can pay money for this solution
    if can, pls contact to me with email vienkmt@hotmail.com
    Volodymyr Shymanskyy
    @vshymanskyy
    @vienkmt Blynk is very similar to MQTT, but supports Apps out of the box. Maybe consider using the example I just posted...
    96konoha
    @96konoha
    Hello is anyone still here in development?
    I tried many times but I got a problem : aws shadow connect failed : -13
    I am trying out the aws_starter_demo, and the output is like this:

    Build Time: Jul 11 2018 11:25:01

    Board Name = mw302_rd

    AWS STARTER DEMO

    sensor_drv_init done
    [init] Initialized wireless stack
    [af] app_ctrl: prev_fw_version=0
    [net] Initialized TCP/IP networking stack
    [af] app_ctrl [sta]: State Change: INIT_SYSTEM => CONFIGURED
    [af] app_ctrl [sta]: State Change: CONFIGURED => NORMAL_INIT
    [af] app_ctrl [sta]: State Change: NORMAL_INIT => NORMAL_CONNECTING
    [af] network_mgr: network loaded successfully
    [af] app_ctrl [sta]: State Change: NORMAL_CONNECTING => NORMAL_CONNECTED
    Connected successfully to the configured network
    aws shadow connect failed : -13

    vienkmt
    @vienkmt
    @96konoha please config your router, use google DNS. It ok for me
    96konoha
    @96konoha
    no still not working
    is anyone still working with this board? please contact me
    let's discuss
    Jose Pablo Carballo
    @josecarballoGL
    Hi @96konoha, we still work for this board... if you are interested in professional engineering services msg us at jose.carballo@gorillalogic.com
    Patrick Kelly
    @paddyspatter_twitter
    anyone still working on this board?
    akashhajari
    @akashhajari
    Hello
    I am using VADACTRO’s IoT Evaluation Kit.
    I am able to compile prog with below command & provided toolchain.
    make APP=sample_apps/hello_world BOARD_FILE=sdk/src/boards/vd_iot_evalkit-v1p.c
    but I am not able to flash it using
    python sdk/tools/OpenOCD/flashprog.py --mcufw bin/vd_iot_evalkit-v1p/hello_world.bin
    it shows error as
    Using OpenOCD interface file ftdi.cfg
    ~/Vadactro/ez-connect-lite-master/sdk/tools/OpenOCD/Linux/openocd64: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
    OpenOCD failed! Aborting...
    Can someone help?
    Ghost
    @ghost~5cb2ffcdd73408ce4fbdaadd
    Hi,
    I am working on aws-iot project using mongoose os and esp32.
    Is there any way,so that i can change device desired state in shadow by using web or android app.
    Ghost
    @ghost~5cb2ffcdd73408ce4fbdaadd
    How can I change desired value is aws-iot shadow of multiple things together.
    _