[NXP Rapid IoT Review] W2 web development platform trial[Copy link]
During the first evaluation, web IDE ATMOSPHERE was mentioned twice, so the second evaluation will revolve around this guy. When applying, I also mentioned that I was very interested in this development environment. It is said that you don’t need to write code. Think about it. Kindergartens can develop the Internet of Things. What do you think? The URL of this web IDE is https://platform.atmosphereiot.com/
Of course, you have to register for the first login. Everyone must know the process. Fill in personal information, email verification, click the verification email link, and then you can log in. It may be a bit slow to enter for the first time because it needs to be initialized. The interface you see is relatively simple. As shown in the figure below, there are three tabs on the left, namely dashboard, device and project. When nothing is done, these places are empty, but there are links to tutorials. If you click the question mark, you will be directly navigated to the development center, which is a summary of all documents.
Let's take a look at what each part does, starting with the dashboard. From the introduction, it says, "The dashboard can display device data through various widgets. Widgets are visual components that can display input device data in various ways, such as through graphs, tables, and charts. Widgets also provide the ability to record, monitor, and analyze data, as well as the option to export data to spreadsheets and reports. In addition to the platform's dashboard page that allows data from any device under the account to be displayed, each registered device also has its own dedicated dashboard page, which can be accessed from the device page. " In other words, this is for cloud display. Then look at the device, which should be simpler. "The platform provides the ability to connect terminal devices. Any device with firmware installed can connect to this platform. Once connected, you can view and configure the terminal device, display and analyze its data, and so on. Supported hardware refers to any terminal device that is compatible with the platform. These devices also have corresponding project types. After creating a project and embedding firmware into the device, the device can be registered with the platform. " For details, please see https://developer.atmosphereiot.com/documents/connectingdevices/connectingtoatmosphere.html Of course, the platform currently supports very few devices, in addition to NXP Rapid IoT, ST SensorTile is also on the list, but ST doesn't seem to be that generous. After the last event, they took it back! ! Otherwise, we can try it together. Finally, let's take a look at the project page, which should be the main battlefield later. The interface is very simple, as shown in the figure below, mainly creating and importing.
Of course, there are many demos, a total of 24, NXP rapid IoT accounts for 18, which shows that NXP has put a lot of thought into it, while our ST SensorTile has only one, and the support is still not enough. Of course, we will first look at the embedded helloworld, blinkLED, click sample, and you can see the project, as shown below:
The middle figure is the code, and the right side is the basic elements that can be put on the figure. Now you can see BLE, gpio, adc, etc., which correspond to the various peripherals on the microcontroller. Through the connection and setting between these peripherals, the desired function is finally completed. When we click on any element on the programming diagram, the setting page for the element will be displayed on the right. For example, when we click on the gray interval, the right side will be like this. In fact, you can guess what each one is doing.
By checking the 4 elements on the page, we can basically know that this program is to toggle the state of the red LED every 1s, and display an icon of a light with a label on the display. Wow, code reading has never been so refreshing. If you want to try the actual running results of this program? Then see how to compile and download it. First click on https://developer.atmosphereiot.com/images/PlatformIcons/Compile.svg to compile, then click on https://developer.atmosphereiot.com/images/PlatformIcons/ProgramFirmware.svg[/img] You can download the firmware. Note that the other download arrow is for downloading code. According to the help center, some platforms can be burned directly, while NXP's is for downloading bin firmware directly. I waited for this for quite a long time and thought it was frozen.
Then press and hold the button in the upper left corner and press reset at the same time. When the USB flash drive appears after the reboot, drag the firmware into it and it's done. After the firmware is updated, it will automatically restart. Notice that even with such a simple firmware, there will be an "advertising" interface of NXP and ATMOSPHERE when it is started, and then the user interface. As expected, a light bulb appeared on the display, plus a line of words, "blinking a led", and the led in the upper left corner was a red light flashing.
Summary: 1. The design idea is very good, and programming seems to be very convenient and intuitive on the surface. Directly using the web means that you can use it as long as you have a modern browser, which is super cross-platform. Anyway, it is all about freedom. 2. The flexibility is reduced, the hardware platform that can be used is limited, and the efficiency of the firmware obtained by programming is definitely low. You can see it from the first two initialization screens. This is a bit like watching movies on Youku without membership. Some people say that you can download the code to the local machine and modify it. In theory, yes, but it always feels weird. After all, there are many GUI configuration programs from various manufacturers, so it is not worth it to toss this one. This review ends here, and I will try the sensor next time. This content was originally created by EEWORLD forum user johnrey. If you want to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source