Is it possible to update the jalapeno to the latest snapshot release of openwrt? It seems the snapshot includes compatability for the jalapeno. With the default lede image I'm unable to install a lot of software packages because the kernel version is incompatible according to opkg (stuff like openvpn, getdns).

Well, to answer myself. It's perfectly possible. I wasn't able to upgrade through Luci, but I reflashed the NAND from the serial console. The OpenWRT snapshot version runs fine on the jalapeno and all fancy stuff like wireguard and getdns also work.

I have a jalapeno devboard, I had to open the serial console, interrupt the uboot loader and I used tftpboot to load the openwrt-factory.ubi file and then the nand write command to write the image.

Hi,
I renamed the factory .ubi file (generated with openwrt build system) to fwupdate.bin and used the script "run do_recovery" to download the file from my tftp-server.
Obviously there is something wrong with the wifi driver:

[ 24.993286] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/pre-cal-ahb-a000000.wifi.bin failed with error -2
[ 24.993330] ath10k_ahb a000000.wifi: Falling back to user helper
[ 26.310120] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
[ 26.310174] ath10k_ahb a000000.wifi: Falling back to user helper
[ 26.367591] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 27.636891] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[ 27.636938] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 27.648485] ath10k_ahb a000000.wifi: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6c332c67
[ 27.718741] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:16 crc32 83549421
[ 29.066228] ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[ 29.082522] ath: EEPROM regdomain: 0x0
[ 29.082531] ath: EEPROM indicates default country code should be used
[ 29.082534] ath: doing EEPROM country->regdmn map search
[ 29.082542] ath: country maps to regdmn code: 0x3a
[ 29.082547] ath: Country alpha2 being used: US
[ 29.082550] ath: Regpair used: 0x3a
[ 29.283422] ath10k_ahb a800000.wifi: Direct firmware load for ath10k/pre-cal-ahb-a800000.wifi.bin failed with error -2
[ 29.283485] ath10k_ahb a800000.wifi: Falling back to user helper
[ 31.456012] ath10k_ahb a800000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
[ 31.456058] ath10k_ahb a800000.wifi: Falling back to user helper
[ 31.538152] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 31.538426] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[ 31.546077] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 31.559972] ath10k_ahb a800000.wifi: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6c332c67
[ 31.606545] ath10k_ahb a800000.wifi: board_file api 2 bmi_id 0:17 crc32 83549421
[ 32.955059] ath10k_ahb a800000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1

I remember getting that same error after flashing, but it went away after a few reboots and some fiddling. It might be that its a proprietary file that has to be downloaded, although that seems unlikely. If you are coming from the pre-flashed LEDE image, keep in mind that eth0/eth1 might have been switched. I had to use eth1 as WAN port and eth0 as local port. The TFTP procedure seems to work from both ports btw.

I didn't use the run do_recovery script but manually copied some of the steps from the rec1..rec4 variables found in printenv

Hi Sig,

My first try was also following this instructions with the result of a bootloop.
Using serial console and a TFTP server as written in my previous post worked for me...

Since my last visit at the 8devices website they added a howto page
http://www.8devices.com/wiki/jalapeno:gettingstarted

Thank you very much, the new howto was really helpful.
The jalapeno is now working again with the new openwrt 18.06.1 firmware.

Testing can go on now.

Regarding the dev board, I wish they would have added an extra micro USB port for power, had to buy a USB Hub with external power to use serial port.