The video analytics market size is estimated to grow from USD 1.69 Billion in 2016 to USD 4.23 Billion by 2021, at an estimated CAGR of 20.2% from 2016 to 2021 (MarketsandMarkets 2016 report on global analytics market).
It looks like xdctools 3.25.06 is too old for the version of BIOS you are using. I got the same error when building with BIOS 4.42.03.35 and xdctools 3.25.06.96. I was able to build successfully with xdctools 3.32.01.22. You can find the xdctools downloads here:
I wasn't sure if you mean BIOS 4.42.03.35 or 6.42.03.35, but I tried using the XDCtools 3.32.01.22 with BIOS 6.42.03.35 and it gives different errors now. I also deleted the src and debug directories, did a clean project, and built the project again, same errors. Here they are below:
The TL-WR740N v4.23 works perfectly with the current unmodified Attitude Adjustment (12.09-beta) generic WR740N v4 and Attitude Adjustment (12.09 Final) generic WR740N v4 images. The best installation method is flashing it through the stock TP-Link web interface. So first download the openwrt-ar71xx-generic-tl-wr740n-v4-squashfs-factory.bin file from the above links (the 12.09 Final preferred). If there is a newer version of OpenWRT at the time you read this, you may use it, but be sure to download the file ending in: -tl-wr740n-v4-squashfs-factory.bin, or you may effectively brick your router.
So, after downloading the Image Builder, extracting it, enter the extraction folder and then continue issuing the respective command:
For Attitude Adjustment 12.09-beta ImageBuilder (r33312):
make image PROFILE=TLWR740 PACKAGES="base-files busybox dnsmasq dropbear firewall hotplug2 iptables iw jshn kernel kmod-ath kmod-ath9k kmod-ath9k-common kmod-cfg80211 kmod-crypto-aes kmod-crypto-arc4 kmod-crypto-core kmod-gpio-button-hotplug kmod-ipt-conntrack kmod-ipt-core kmod-ipt-nat kmod-ipt-nathelper kmod-leds-gpio kmod-ledtrig-default-on kmod-ledtrig-netdev kmod-ledtrig-timer -kmod-ledtrig-usbdev kmod-lib-crc-ccitt kmod-mac80211 kmod-nls-base kmod-ppp kmod-pppoe kmod-pppox -kmod-usb-core -kmod-usb-ohci -kmod-usb2 kmod-wdt-ath79 libblobmsg-json libc libgcc libip4tc libiwinfo libiwinfo-lua libjson liblua libnl-tiny libubox libubus libubus-lua libuci libuci-lua libxtables lua luci luci-app-firewall luci-i18n-english luci-lib-core luci-lib-ipkg luci-lib-lmo luci-lib-nixio luci-lib-sys luci-lib-web luci-mod-admin-core luci-mod-admin-full luci-proto-core luci-proto-ppp luci-sgi-cgi luci-theme-base luci-theme-openwrt mtd netifd opkg ppp ppp-mod-pppoe swconfig uboot-envtools ubus ubusd uci uhttpd wireless-tools wpad-mini luci-app-qos luci-app-openvpn luci-app-tinyproxy luci-app-upnp"
For Attitude Adjustment 12.09 Final ImageBuilder:
make image PROFILE=TLWR740 PACKAGES="base-files busybox dnsmasq dropbear firewall hotplug2 iptables iw jshn kernel kmod-ath kmod-ath9k kmod-ath9k-common kmod-cfg80211 kmod-crypto-aes kmod-crypto-arc4 kmod-crypto-core kmod-gpio-button-hotplug kmod-ipt-conntrack kmod-ipt-core kmod-ipt-nat kmod-ipt-nathelper kmod-leds-gpio kmod-ledtrig-default-on kmod-ledtrig-netdev kmod-ledtrig-timer -kmod-ledtrig-usbdev kmod-lib-crc-ccitt kmod-mac80211 kmod-nls-base kmod-ppp kmod-pppoe kmod-pppox -kmod-usb-core -kmod-usb-ohci -kmod-usb2 kmod-wdt-ath79 libblobmsg-json libc libgcc libip4tc libiwinfo libiwinfo-lua libjson liblua libnl-tiny libubox libubus libubus-lua libuci libuci-lua libxtables lua luci luci-app-firewall luci-i18n-english luci-lib-core luci-lib-ipkg luci-lib-nixio luci-lib-sys luci-lib-web luci-mod-admin-core luci-mod-admin-full luci-proto-core luci-proto-ppp luci-sgi-cgi luci-theme-base luci-theme-openwrt mtd netifd opkg ppp ppp-mod-pppoe swconfig uboot-envtools ubus ubusd uci uhttpd wpad-mini luci-app-qos luci-app-tinyproxy luci-app-upnp openvpn"
The v4.23 of the router uses the standard TP-Link pin-out, however the TX pin is not connected to the CPU. In order to make the TX line working, the two points on the bottom side of the PCB must be connected with a small wire. The pin at the SOC is labeled TP18, the one at the serial connector is labeled TP28. The RX line is 5V intolerant! So the connection needs a 3.3V RS232 level shifter. Pins on the connector of the board (look at the photos at the bottom of this post) are TX-RX-GND-3V3(VCC) (from left to right). After you solder all connections, you may use an USB to UART TTL convertor that you plug into your PC and use for example the cutecom application to connect to the /dev/ttyUSB0 device on your PC. Do not forget that you need to connect the TX pin of the convertor to the RX pin of the board and the RX pin of the convertor to the TX pin of the board. In case you use the USB to UART TTL convertor, you do not need to connect the VCC pin. Another important thing to do is to set the convertor to work with 3.3V if it can work both with 5V and 3.3V ! For more info look at the images at the bottom of this post.
I have tested the 12.09 Final (Attitude Adjustment 12.09 Final) and it upgrades and works just fine (incl. with keeping the old configuration files).
There are some bugs fixed and some tweaks for easier configuration done. The wireless-tools package is missing and the luci-app-openvpn is removed as broken (that is if you prepare your own customized image).
Configuring OpenWRT in Tp-TL WR740N V 5.0
Hi ..I find difficult in configuring openwrt in tp link wr740N wireless router version 5.0..In openwrt they have packages only upto version 4.23 for this router.Can anyone suggest solution ,,so that i configure openwrt in tp link 740n router version 5.0.
[Beta] Added support for LinkX module burning via MFT toolset. The new capability enables direct firmware burning from the internal flash storage to reduce the bandwidth and accelerate the burning process, including burning several modules at a time.
Target users: Developers of Flow Steering aware applications. This tool dumps the internal steering table which is used by the device to steer Ethernet packets and Multicast IB packets to the correct destination QPs.
STM32Cube software. A set of free-of-charge tools and embedded software bricks to enable fast and easy development on the STM32, including a Hardware Abstraction Layer, middleware and the STM32CubeMX PC-based configurator and code generator
altera-usb-blaster.cfg altera-usb-blaster2.cfg arm-jtag-ew.cfg at91rm9200.cfg buspirate.cfg calao-usb-a9260.cfg chameleon.cfg cmsis-dap.cfg dummy.cfg estick.cfg flashlink.cfg ftdi ftdi/100ask-openjtag.cfg ftdi/axm0432.cfg ftdi/calao-usb-a9260-c01.cfg ftdi/calao-usb-a9260-c02.cfg ftdi/cortino.cfg ftdi/digilent-hs1.cfg ftdi/digilent-hs2.cfg ftdi/digilent_jtag_hs3.cfg ftdi/digilent_jtag_smt2.cfg ftdi/dlp-usb1232h.cfg ftdi/dp_busblaster.cfg ftdi/dp_busblaster_kt-link.cfg ftdi/flossjtag-noeeprom.cfg ftdi/flossjtag.cfg ftdi/flyswatter.cfg ftdi/flyswatter2.cfg ftdi/gw16042.cfg ftdi/hilscher_nxhx10_etm.cfg ftdi/hilscher_nxhx500_etm.cfg ftdi/hilscher_nxhx500_re.cfg ftdi/hilscher_nxhx50_etm.cfg ftdi/hilscher_nxhx50_re.cfg ftdi/hitex_lpc1768stick.cfg ftdi/hitex_str9-comstick.cfg ftdi/icebear.cfg ftdi/iotlab-usb.cfg ftdi/jtag-lock-pick_tiny_2.cfg ftdi/jtagkey.cfg ftdi/jtagkey2.cfg ftdi/jtagkey2p.cfg ftdi/kt-link.cfg ftdi/lisa-l.cfg ftdi/luminary-icdi.cfg ftdi/luminary-lm3s811.cfg ftdi/luminary.cfg ftdi/m53evk.cfg ftdi/mbftdi.cfg ftdi/minimodule.cfg ftdi/minispartan6.cfg ftdi/neodb.cfg ftdi/ngxtech.cfg ftdi/olimex-arm-jtag-swd.cfg ftdi/olimex-arm-usb-ocd-h.cfg ftdi/olimex-arm-usb-ocd.cfg ftdi/olimex-arm-usb-tiny-h.cfg ftdi/olimex-jtag-tiny.cfg ftdi/oocdlink.cfg ftdi/opendous_ftdi.cfg ftdi/openocd-usb-hs.cfg ftdi/openocd-usb.cfg ftdi/openrd.cfg ftdi/pipistrello.cfg ftdi/redbee-econotag.cfg ftdi/redbee-usb.cfg ftdi/rowley-cc-arm-swd.cfg ftdi/sheevaplug.cfg ftdi/signalyzer-lite.cfg ftdi/signalyzer.cfg ftdi/stm32-stick.cfg ftdi/swd-resistor-hack.cfg ftdi/ti-icdi.cfg ftdi/tumpa-lite.cfg ftdi/tumpa.cfg ftdi/turtelizer2-revB.cfg ftdi/turtelizer2-revC.cfg ftdi/um232h.cfg ftdi/vpaclink.cfg ftdi/xds100v2.cfg ftdi/xds100v3.cfg jlink.cfg jtag_vpi.cfg nds32-aice.cfg opendous.cfg openjtag.cfg osbdm.cfg parport.cfg parport_dlc5.cfg raspberrypi-native.cfg raspberrypi2-native.cfg rlink.cfg stlink-v1.cfg stlink-v2-1.cfg stlink-v2.cfg sysfsgpio-raspberrypi.cfg ti-icdi.cfg ulink.cfg usb-jtag.cfg usbprog.cfg vsllink.cfg
The IndexError is because the tool expects a filename to flash on the argument list. Fortunately there are samples included, try this one: python flashSTM32.py stm32-firmwares/blink100k.bin. Gets further but again an empty read:
I know this sounds really dumb, but had the same thing happen to me. Come to find out I accidently sent the board to the wrong board on tool menu when trying to view the serial monitor quickly. When I set it back to the right board everything worked.
I had the same problem with the atmega1280, after a long time that I was fighting with the error I changed the board to atmega2560 and after two weeks (neither) the problem came.
Tonight I solved for atmega1280!
I was trying to burn the bootloader with jtagice mkii and I got this error:
We can create our project under the zephyr workspace directory, but then we will have trouble if we want to use git to manage our project since the zephyr workspace directory is already a git repository. So we will create our own directory outside of the zephyr workspace directory and work from there.
To do this we need to set the ZEPHYR_BASE environment variable to point to the zephyr workspace, otherwise the west tool that will compile and flash our project will fail. Since west is a python command and we are using virtual environments, as discussed on the previous post we need to first change to the virtual env that has west installed:
To be able to do this is necessary to have a ST-Link programmer and that it is properly connected to the STM32 blue pill board. Any issues here are probably not related with Zephyr or the west tool, since west only calls openocd to flash the board.
aa06259810