After reboot OpenIPC no WLAN Connection no IP Adress about lightcamera-openipc

[dirandad]

May be you have a file on the SD Card that have replace your wlan configuration ?
Check that script autoconfig.sh is fired, for example by writing a test file on the SD Card.

I recently experiment that in some case, the image generated by ./make_images.sh give a different partitioning so that the following line in autoconfig.sh have to be adapted :
fw_setenv bootargs mem=\${osmem} panic=20 rootfstype=squashfs root=/dev/mtdblock3 init=/init mtdparts=hi_sfc:256k\(boot\),64k\(env\),3072k\(kernel\),10240k\(rootfs\),-\(rootfs_data\) mmz_allocator=hisi.

so steps can be:

• check if autoconfig.sh can fired : this will confirm that openipc can start
• If yes : you have to play and replace the wlan config in /autoconfig/etc/network/interfaces
  /interfaces
• if no : bad new, no other solution than opening the camera and write to the flash using an eeprom writer (CH341a)

[Goo15]

Unfortunately, the autoconfig file is no longer executed. This is very annoying, since openipc was already working. Only when I pressed the restart button did the camera no longer register in the WLAN. Is there perhaps the possibility of reloading the original firmware?

[Goo15]

I have now dismantled the lamp. Do I have to unsolder the EEprom or does flashing work with a clip? Can I possibly also address the camera via UART? I ordered the EEProm writer CH341a and will try my luck with it

[dirandad]

No need to usolder the eeprom, I was able to flash using a clip. You will need to remove the lens to get place to install the clip. Don't forget to verify the writing as some time there is some writing error.
Camera should be power off during flashing. The eeprom itself is powered by CH341a.
Yes, you can address the camera via UART. If indeed your issue sur because of formatting is different from the script provided in autoconfig.sh, the difference should be in kernel of data partition, so that uboot is not affected. In this case uboot should be accessible using UART. You should find all needed information to connect on UART on this github.

[Goo15]

I tried to write the image to the EEProm. However, I keep getting an error when comparing. Do you have any other ideas?

C::\Users\thgoe\Downloads\SNANDer-v.1.7.7\SNANDer-v.1.7.7\Windows> SNANDer -d -v -w openipc-hi3518ev300-ultimate-16mb.bin

SNANDer - Serial Nor/nAND/Eeprom programmeR v.1.7.7 by McMCC [email protected]

Found programmer device: WinChipHead (WCH) - CH341A
Device revision is 3.0.4
spi_nand_probe: mfr_id = 0x40, dev_id = 0x18, dev_id_2 = 0x18
SPI NAND Flash Not Detected!
spi device id: ef 40 18 0 0 (40180000)
Detected SPI NOR Flash: W25Q128BV, Flash Size: 16 MB
WRITE:
Write addr = 0x0000000000000000, len = 0x0000000001000000
Written 100% [16777216] of [16777216] bytes
Elapsed time: 253 seconds
Status: OK
VERIFY:
Read addr = 0x0000000000000000, len = 0x0000000001000000
Read 100% [16777216] of [16777216] bytes
Elapsed time: 125 seconds
Status: BAD

[Goo15]

After several attempts I was able to flash the EEProm without errors. But I still have no access to the SD card. I wanted to assign a WLAN connection via the SD card according to your instructions. Unfortunately that doesn't work. An empty SD card is not formatted with ext2 by the camera. Test writing to a file with autoconfig.sh also does not work. What else can I do?

[Goo15]

Got it running now. But when I load the lightcam application into the camera via the SD card, the kernel no longer starts. We noticed that the memory is very full. can it be because of that? Here the log from Putty.
System startup

Uncompress Ok!

U-Boot 2016.11-g6d2ed0c-dirty (Mar 20 2023 - 13:54:51 +0300)hi3518ev300

Relocation Offset is: 0374a000
Relocating to 43f4a000, new gd at 43b39ef0, sp at 43b39ed0
SPI Nor: hifmc_ip_ver_check(44): Check Flash Memory Controller v100 ...hifmc_ip_ver_check(50): Found
hifmc_spi_nor_probe(1802): SPI Nor ID Table Version 1.0
hifmc_spi_nor_probe(1827): SPI Nor(cs 0) ID: 0xef 0x40 0x18
spi_w25q256fv_qe_enable(193): Error: Disable Quad failed! reg:0x2
hifmc_spi_nor_probe(1892): Block:64KB hifmc_spi_nor_probe(1893): Chip:16MB hifmc_spi_nor_probe(1894): Name:"W25Q128(B/F)V"
hifmc100_spi_nor_probe(147): SPI Nor total size: 16MB
NAND: 0 MiB
MMC: Card did not respond to voltage select!
No SD device found !
hisi-sdhci: 0
In: serial
Out: serial
Err: serial
RAM size: 64MB
Net: eth0
Warning: eth0 (eth0) using random MAC address - 8e:e3:1c:40:e9:81

Press Ctrl-c to stop autoboot... 1
device 0 offset 0x50000, size 0x300000

SF: 3145728 bytes @ 0x50000 Read: OK

Booting kernel from Legacy Image at 42000000 ...

Image Name: Linux-4.9.37-hi3518ev300
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1929024 Bytes = 1.8 MiB
Load Address: 40008000
Entry Point: 40008000
Loading Kernel Image ... OK

Starting kernel ...

[Goo15]

I managed to get ipc open to run stably on the camera. The problem was that the camera didn't start because it was connected to the ch341 programmer in UART mode. If the serial connection is terminated, the camera starts without any problems.

[dirandad]

Hello,
Well done.
Do you have also the image from the sensor ?
Adrien

[Goo15]

Hello Adrien
What do you mean with the image of the sensor?
I still have problems with the lightcam application and unfortunately I don't know what to do anymore. I didn't recompile the lightcam binary file, I took it from your script. Which IP address must be entered in the lightcam.yamel on the MQTT server. I entered the IP of my camera. I hope this is right. When starting with /usr/sbin/lightcam /etc/lightcam.yml from the OpenIPC web console, there is always the error message as described in the "Lightcam application does not work" issue. Stopping lightcam with /etc/init.d/S50lightcam stop also leads to a fail. Is this even a malfunction of the lightcam application? What else could I do? I would be very grateful for any help, I'm running out of ideas. If you need more information I will be happy to provide it to you.
Greetings Thomas.

[dirandad]

I mean, do you see the image of the camera in the openipc web interface. To be sure you have the good sensors driver, and all is working well from this side.
Concerning mqtt configuration, I will answer on the other issues (#8)