@crispyoz the idea is to generate final binary that contains all partitions (uboot, factory, firmware...) in order to flash it to all my devices in the factory production phase.
there is unique params for each device that are stored in mtd2 partition(factory partition). these params are:
I want to change these params in my production process before flashing each device
uci-default will not help me in such process
@Lazar-Demin
I made a comparison between the mtd2 partitions of 2 boards. and here what I found:
the difference in the lines 0000000 and 0000020 and 0000030 are about the Mac addresses.
but the difference in line 0000050 is not clear for me. could be this related to the radio ?
@crispyoz as @Lazar-Demin said it's not about the uci config. it's a config that was put in the factory partition (mtd2) like the Mac address.
@Lazar-Demin Could you please let me know what could be the radio config that the factory partition hold? could you please provide example or link
thank you
thank you for your feedback
I checked the default radio configuration and it's the same for all device.
Do you mean the SSID name?
@Lazar-Demin
after flashing uboot and Openwrt to the SPI flash, then I can get the HEX file with the flash programmer.
Now I want to clone this file to other devices, but there is some parameters that are unique per each device like the MAC address that I have to change in the HEX file. Could you please let me know what other parameters that I need to change in the image file for each device?
thank you for your feedback
where I can find the programmer application ?
we have onion2 board
I can see that the board come with the uboot already installed.
1- First Question: what is the uboot used in the omega2 boards? I found 2 repositories of uboot in your Github:
https://github.com/OnionIoT/u-boot
or https://github.com/OnionIoT/omega2-bootloader ?
2- are there a ready binary of the boot loader that I can download and use in my board?
3- are there a way to combine the uboot binary and the omega2 openwrt binary in a single file and then flash it to the omega2 board? with this way I will flash only 1 file in the factory instead of 2 files
In our company, we are using Omega2 chipsets in our IOT bridge solution.
we were running OpenWRT18, and we are looking to bring up to openwrt 22.03.
I used the GitHub onion repo (https://github.com/OnionIoT/openwrt.git) to build openWRT 22.03.
I tried to change the Device Tree to fit our Board. so I used the following dts files:
OMEGA2.dts:
/dts-v1/;
#include "OMEGA2.dtsi"
/ {
compatible = "onion,omega2", "mediatek,mt7628an-soc";
model = "Onion Omega2";
memory@0 {
device_type = "memory";
reg = <0x0 0x4000000>;
};
gpio-leds {
compatible = "gpio-leds";
ethernet {
label = "ryse:blue:ethernet";
gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
};
internet {
label = "ryse:blue:internet";
gpios = <&gpio0 15 GPIO_ACTIVE_HIGH>;
};
};
};
&firmware {
reg = <0x50000 0xf30000>;
};
&flash {
user: partition@f80000 {
label = "user";
reg = <0xf80000 0x80000>;
};
};
&system_led {
label = "omega2:amber:system";
};
OMEGA2.dtsi:
#include "mt7628an.dtsi"
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/input/input.h>
/ {
compatible = "onion,omega2", "mediatek,mt7628an-soc";
chosen {
bootargs = "console=ttyS0,115200";
};
gpio-leds {
compatible = "gpio-leds";
system_led: system {
gpios = <&gpio1 12 GPIO_ACTIVE_LOW>;
};
};
gpio-keys-polled {
compatible = "gpio-keys-polled";
#address-cells = <1>;
#size-cells = <0>;
poll-interval = <20>;
reset {
label = "reset";
gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;
linux,code = <KEY_RESTART>;
};
};
};
&pinctrl {
state_default: pinctrl0 {
gpio {
ralink,group = "gpio";
ralink,function = "gpio";
};
perst {
ralink,group = "perst";
ralink,function = "gpio";
};
refclk {
ralink,group = "refclk";
ralink,function = "gpio";
};
i2s {
ralink,group = "i2s";
ralink,function = "gpio";
};
spis {
ralink,group = "spis";
ralink,function = "gpio";
};
wled_kn {
ralink,group = "wled_kn";
ralink,function = "gpio";
};
wled_an {
ralink,group = "wled_an";
ralink,function = "gpio";
};
wdt {
ralink,group = "wdt";
ralink,function = "gpio";
};
pwm0 {
ralink,group = "pwm0";
ralink,function = "gpio";
};
pwm1 {
ralink,group = "pwm1";
ralink,function = "gpio";
};
};
};
&gpio1 {
status = "okay";
};
&gpio2 {
status = "okay";
};
&spi0 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi_pins>, <&spi_cs1_pins>;
flash: m25p80@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <40000000>;
m25p,chunked-io = <31>;
partition@0 {
label = "u-boot";
reg = <0x0 0x30000>;
read-only;
};
partition@30000 {
label = "u-boot-env";
reg = <0x30000 0x10000>;
read-only;
};
factory: partition@40000 {
label = "factory";
reg = <0x40000 0x10000>;
};
firmware: partition@50000 {
label = "firmware";
};
};
spidev@1 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "rohm,dh2228fv";
reg = <1>;
spi-max-frequency = <40000000>;
};
};
&i2c {
status = "okay";
};
&uart1 {
status = "okay";
};
&uart2 {
status = "okay";
};
ðernet {
mtd-mac-address = <&factory 0x28>;
};
&sdhci {
status = "okay";
mediatek,cd-low;
};
&wmac {
status = "okay";
};
&pwm {
status = "okay";
};
I copied these 2 files from Openwrt SDK 18 from onion git repo (source): https://github.com/OnionIoT/source.git
I put these 2 files (OMEGA2.dst and OMEGA2.dtsi) under the directory "target/linux/ramips/dts/" in the new openwrt SDK 22.03 and then I build the openwrt and then upload the image to my board but the new Device Tree is not taken account.
What I am missing?