REST API Access

Good evening,

I upgraded the OS of an Arduino Yun Board with the most recent image available, dated July 12th 2014 (openwrt-ar71xx-generic-linino-yun-16M-250k-squashfs-sysupgrade.bin found at http://linino.org/doku.php?id=wiki:upgradeimage). After successfully doing this, the stability of the USB host port was fixed, while being used for a serial communication with another device which sends data dumps every second (114 bytes, at 57600 8N1). This means, the TTYUSB0 port doesnt get blocked after a while, and it can consistently receive data from a device plugged via a USB-Serial converter cable (which uses prolific driver PL2303) attached to it. This is awesome! This has been tested for 24 hrs continuously, so it's robust now, thank God.

The problem here, after this update, was that the REST API calls are now totally ignored. These ones, conform a software architecture that exposes various parts of the Arduino hardware through URLs. They used to work perfectly in the previous built-in image (openwrt-ar71xx-generic-linino-16M-squashfs-sysupgrade.bin). The digital pins of the board are used to turn on leds at this moment. Even using the default Bridge code example from arduino page, wont work anymore.

The code is effectively uploaded to the ATMEGA, because of LED 13 used as hint. No code, no LED 13 on at all. So, it's not a problem with an absence of code. It's the bridge itself, or so it seems. I guees it's related to the REST API access, which seems to be password protected. And even though I changed the setting at the Luci page to OPEN, it still wont work. So I'm venturing myslef to ask the community if there's a way to manually confirm this setting inside Linino, some sort of specific path as in /etc/config/luci to look for a file to verify the changes.

I'm only trying to see if this can be fixed, otherwise I will have to downgrade to the previous image and go back to suffer with USB host port.

Regards,

PS. The recent stated changes of the newest binary file point to a modification of the behavior of the Bridge , adding a parameter "-u", which makes me wonder about this subject even more.