I don't see why that would be making a lot of change, but I implemented an additional FET which shorts VDD_FLASH to ground when reset is active. Gate is connected to the drain of Q2.
It's not a solution that makes me proud, but it works.
Erik
I don't see why that would be making a lot of change, but I implemented an additional FET which shorts VDD_FLASH to ground when reset is active. Gate is connected to the drain of Q2.
It's not a solution that makes me proud, but it works.
Erik
My company has developed a product around the 2S+ running a rather simple Node (8) application. However, the node_modules folder contains a lot of modules/submodules not being used by us and hence we need external flash to run the application right now.
Is there a way to scan the application and automatically remove any unused code from node_modules? We are using the Azure IoT device module which is big, and I removed some unused parts manually. But I'd rather have this process automated to save time and errors and to free up as much flash space as possible. It bothers me to install an eMMC chip just to hold unused code
Hi,
I am trying to use serialport in NodeJS 8 on the latest firmware on Omega2S+. I tried installing the module from https://github.com/sdesalas/node-serialport-omega2 but I get this error:
...
was compiled against a different Node.js version using
NODE_MODULE_VERSION 46. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module
I tried cross-compiling serialport but I end up getting another error when running a simple test:
Fatal error in ../deps/v8/src/api.cc, line 1244
Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
Not having much (read: any) experience building my own Node modules or cross-compiling at all, I have no clue how to solve this. Maybe going back to an earlier version of the firmware with NODE_MODULE_VERSION 46, but that does not seem like a good long-term solution.
Any help is greatly appreciated
I don't see why that would be making a lot of change, but I implemented an additional FET which shorts VDD_FLASH to ground when reset is active. Gate is connected to the drain of Q2.
It's not a solution that makes me proud, but it works.
Erik
Re: Omega2S Reset Pin C21 shutdown instead of reset
I have some issues with my Omega2S+ on a custom board. The CPU does not reboot after reset, and this HW reset circuit has been implemented.
I notice that even with Q2 (in the diagram of topic 2927) shut off (or even removed from the PCB) there is around 2V on the VDD_FLASH pin. I assume this is enough to keep the flash from resetting to 3 byte mode.
Does anyone know how to make sure the reset works?
Thanks,
Erik
Hi,
I have installed the Docker image for cross compiling and built the toolchain which took a few hours. Now I would like to save the container to avoid having to build it all over again.
What is the best approach to do that? I tried committing the container which took forever and then I got a "no space left" error. I am pretty sure this is not the appropriate way of doing it.
Any help is appreciated
Hi,
I have been using Python 2.7 and the SDK for Microsoft Azure IoT hub to build an application on a Pi, and I want to port it to an Omega2+ (with SD storage) for mass production.
It seems somewhat more complicated than getting started on the Pi.
Does anyone have a guide on how to install the IoT SDK for Python and its dependencies?
Thanks in advance,
Erik