ffmpeg -i input.mov \
-c:v libx264 -crf 23 -profile:v baseline -level 3.0 -pix_fmt yuv420p \
-c:a aac -ac 2 -b:a 128k \
-movflags faststart \
if [ -z “$DIRPATH” ]
mkdir -p processed
for i in $FILES
if [ -d “$FILES” ]
NEW_NAME=$(echo $i | sed ‘s/\.[^.]*$/.mov/’)
ffmpeg -i “$i” -vcodec dnxhd -profile:v dnxhr_hq -r 25 -pix_fmt yuv422p -s 3840×2160 -c:a pcm_s16le “processed/$NEW_NAME”
#ffmpeg -i “$i” -vcodec dnxhd -acodec pcm_s16le -s 1920×1080 -r 30000/1001 -b:v 36M -pix_fmt yuv422p -f mov “processed/$NEW_NAME”
Update, the course is completed and can be found on udemy, link is here: STM32 Beginner Course
I’ve seen some interest in my stm32 blinky example tutorial and want to give you guys more content in the fun embedded world, especially for the stm32 microcontroller. I’ve put up a table of contents down below, this is what the course will cover.
What radio would you like to see in this course? Please leave a comment down below or email me. I’m also thinking of creating a hardware starter kit with all the necessary components needed for the project.
Thanks for your time,
I’m currently doing a project with STM32 and radios. I want to have a server with all the stm32’s connected, with UART, USB and ST-Link v2. I’m using a laptop as my development computer and don’t want to plug the connections in and out all the time. Therefor I installed a Linux server which will host this for me.
Folder structure for mMesh:
- src/spi # Serial Peripheral Interface (SPI)
- src/test # GTest
- src/test/mesh # GTest
- src/syscalls # Wrapper for calls like sleep and timers, differs between different platforms.
- src/netAlgorithm # Implementation for network algorithms for choosing parent, neighbour and routing for packets.
- src/mesh # Mesh implementation
- src/network # Network adapter and network drivers
- src/network/RF24 # RF24 driver ported from https://github.com/nRF24/RF24
- src/node # Is used for testing, a node simulates a radio with network functionality
- src/GPIO # General Purpose Input Output (GPIO)
- src/islands # Is used for testing, simulates physical boundaries, if two nodes reside in one island they are able to speak with each other.
I have created a mesh network algorithm for embedded systems. This implementation is released be released under MIT License.
Me and a friend have started an Internet Of Things project and we wanted to have a radio module to our microcontroller for communication. The radio module we choose was the NRF24L01+.
One question might arise: Why not use the NRF24Mesh solution that’s already been developed? I’ve looked at the design and noticed that it could be improved which are mentioned in the features, and I also wanted to create it by myself, because I can 🙂
In this post I will discuss about the architectural design of the Mesh Network.
Features of this implementation:
Address range: ~2^18 addresses (262144).
Decentralized network topology: a master is needed, all grouping and addressing will be decentralized, which means that the closest “parent” is responsible to address it’s children’s.
Mesh with multiple routes: All the nodes in the network has always a “default” route to master. Nodes can also pair to other nodes in the network that is physically close. If node A and node B needs to communicate with each other they don’t need to send the packet via the master node, if there is an opportunity to send the packet to a physically near node, and the number of hops is less than via the master, the packet will be sent to that neighbour, which will route it onwards.
To update u-boot via tftp, install a tftp software and copy its binaries to the directory where tftp has its data. The text in bold is the text you type in. This is intended for armbian use. They require the latest u-boot version.
Espressobin is my new toy which eventually be my new bridge to the internet while it hosts my connected home. Eventually it will be hosting Home Assistant, OpenVPN and be the WLAN Access Point.
The Espressobin has all the “horse power” i need, it is equipped with 1 gigabyte of ram and a dual core ARM Cortex A53 processor with a clock speed up to 1.2GHz. Which will be plenty enough for my setup. Technical details about the Espressobin is available on their homepage: http://espressobin.net/tech-spec/
I am currently working with a project regarding my LED-lightening in the kitchen. The system will be based on a STM32-circuit and the communication device is a mrf24j40 which supports the 802.15.4 protocol.
This is my first encounter with the new microcontroller and programmer I ordered from aliexpress. The microcontroller is an STM32F103C8T6 and the programmer is a ST-Link v2 clone.