

surfero75
-
Posts
13 -
Joined
-
Last visited
Reputation Activity
-
surfero75 got a reaction from guidol in Orange Pi i96
I
Sorry! you're right! the buildroot for opi 2G is that:
https://github.com/txurtxil/broot2g
I Leave the config-OpiIoT2G file preconfigured for our card, the procedure is this:
git clone https://github.com/txurtxil/broot2g
cd broot2g /
mv config-OpiIoT2G .config
make menuconfig -> if you want to see or modify buildroot parameters
make ---> to build buildroot
Note1: you can modify or view kernel parameters by running make linux-menuconfig
Note2: I use to develop and compile a cheap tv box (x96) with armbian, I am very comfortable and I do not use the PC, I access it by SSH, tmux, etc ...:
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Amlogic
-
surfero75 got a reaction from guidol in Orange Pi i96
In a Opi Iot 2G I have used 64gb usb flash disk mounted from a armbian that i installed at 512mb flash rom.
The kernel is 3.10.62, I have modified it so that it does not rotate the MAC, I do not see a larger version of the kernel necessary although it seems that it has been incorporated into version 5 in development:
https://github.com/torvalds/linux/tree/master/arch/arm/mach-rda
Actually I have created several images with buildroot, it is simple, I have shared the code ready to make the image in my github:
https://github.com/txurtxil/broot2g
The merit is from a 4pda user (Yoshee) has done an in-depth job to program tft screens from the kernel. I have never seen it work so well at the same time oled screen + sensor dht22 and switches and with the image that has left yoshee all the good and very fine, I leave it here (root / 1)
https://mega.nz/#!oB0mmSBD!XhslDKikwAyvt-6frhpsnX5Tj5SIrKKK7KrHqVE7hms
In /etc/iot.conf we can configure bot telegram, mqtt, etc ... it's a great job.
-
surfero75 got a reaction from TonyMac32 in Orange Pi i96
I have recovered my IoT-2G board because, basically I think it can be fun to program it, I also expect an i96, I love its small size (and its price to learn basic things about kernel programming). Armbian has discarded this board, but we have alternative: buildroot, which is great and can be installed in the 512mb flash memory.
You can do things as interesting as this: DHT22+Qt5+Old SD1301
-
surfero75 got a reaction from guidol in Orange Pi i96
I have recovered my IoT-2G board because, basically I think it can be fun to program it, I also expect an i96, I love its small size (and its price to learn basic things about kernel programming). Armbian has discarded this board, but we have alternative: buildroot, which is great and can be installed in the 512mb flash memory.
You can do things as interesting as this: DHT22+Qt5+Old SD1301
-
surfero75 got a reaction from Millhouse in Orange Pi 2G-IOT
Already it is possible to see and write in NAND memory from linux, I have left a small guide (in Spanish, use google translate) to be able to experiment with its use:
Http://surfero.blogspot.com.es/2017/08/orange-pi-iot-2g-trabajar-con-la.html
At the moment it has not been able to make linux boot from nand but mount it. Everything has been made possible thanks to the work of the gitub aib user (https://github.com/aib)
Dmesg:
[ 0.692321] NAND device: Manufacturer ID: 0x98, Chip ID: 0xac (Toshiba TC58NYG2S0H 4G 1.8V 8-bit), 512MiB, page size: 4096, OOB size: 256
fdisk -l:
Disk /dev/mtdblock1: 8 MiB, 8388608 bytes, 16384 sectors
.........
..........
Disk /dev/mtdblock4: 280 MiB, 293601280 bytes, 573440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
-
surfero75 got a reaction from guidol in Feedback (not requested) for WIP images for unsupported board (Orange Pi 2G-IOT)
We are already a few users of this board. We believe that it already has enough potential for support. I myself have managed to install armbian W.I.P, community on the 512mb of NAND of this card and works well.
Thanks
-
surfero75 got a reaction from guidol in Orange Pi 2G-IOT
Already it is possible to see and write in NAND memory from linux, I have left a small guide (in Spanish, use google translate) to be able to experiment with its use:
Http://surfero.blogspot.com.es/2017/08/orange-pi-iot-2g-trabajar-con-la.html
At the moment it has not been able to make linux boot from nand but mount it. Everything has been made possible thanks to the work of the gitub aib user (https://github.com/aib)
Dmesg:
[ 0.692321] NAND device: Manufacturer ID: 0x98, Chip ID: 0xac (Toshiba TC58NYG2S0H 4G 1.8V 8-bit), 512MiB, page size: 4096, OOB size: 256
fdisk -l:
Disk /dev/mtdblock1: 8 MiB, 8388608 bytes, 16384 sectors
.........
..........
Disk /dev/mtdblock4: 280 MiB, 293601280 bytes, 573440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
-
surfero75 got a reaction from Armen Hovhannisyan in Feedback (not requested) for WIP images for unsupported board (Orange Pi 2G-IOT)
We are already a few users of this board. We believe that it already has enough potential for support. I myself have managed to install armbian W.I.P, community on the 512mb of NAND of this card and works well.
Thanks
-
surfero75 got a reaction from Armen Hovhannisyan in Orange Pi 2G-IOT
Already it is possible to see and write in NAND memory from linux, I have left a small guide (in Spanish, use google translate) to be able to experiment with its use:
Http://surfero.blogspot.com.es/2017/08/orange-pi-iot-2g-trabajar-con-la.html
At the moment it has not been able to make linux boot from nand but mount it. Everything has been made possible thanks to the work of the gitub aib user (https://github.com/aib)
Dmesg:
[ 0.692321] NAND device: Manufacturer ID: 0x98, Chip ID: 0xac (Toshiba TC58NYG2S0H 4G 1.8V 8-bit), 512MiB, page size: 4096, OOB size: 256
fdisk -l:
Disk /dev/mtdblock1: 8 MiB, 8388608 bytes, 16384 sectors
.........
..........
Disk /dev/mtdblock4: 280 MiB, 293601280 bytes, 573440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000