[Elphel-support] Elphel 393 Question
Mohamed Morsy
mmorsy at redzone.com
Wed Feb 21 10:52:21 PST 2018
I have not used the mircro usb port. The default ip address has been
changed to 10.4.1.4.
-Mohamed
On Wed, Feb 21, 2018 at 1:34 PM, Oleg <support-list at support.elphel.com>
wrote:
> Hi Mohamed,
>
> 10.4.1.4 is that elphel's ip.
>> Do you know how to resolve this issue?
>
>
> The default IP is 192.168.0.9
> On the 10393 there's a micro USB port - this is serial console:
>
>> https://wiki.elphel.com/wiki/Tmp_manual > *serial console access*.
>
>
> Do you use it? See any bootlog when power on?
>
> Todd was changing the default IP addresses like this:
> https://wiki.elphel.com/wiki/Tmp_manual > *Change_default_ip_address*
>
> Regards,
> Oleg
>
> On Wed, Feb 21, 2018 at 11:18 AM, Mohamed Morsy <mmorsy at redzone.com>
> wrote:
>
>> Hello Oleg,
>>
>> I was having some difficulties with my linux computer so I hold off on
>> this. I followed your instructions and I increased the php upload limit and
>> I was able to upload rootfs. I'm still having some issues. Here's what I've
>> done:
>> 1. Put recovery card in elphel
>> 2. Went to http://camera-ip-address/update_software.html and flashed it
>> from NAND folder
>> 3. Powered off elphel.
>> 4. Removed card
>> 5. Powered on elphel
>>
>> Now the connection is not working. In my terminal I typed arp and i got
>> this result
>>
>> Address HWtype HWaddress
>> 10.4.1.4 (incomplete)
>>
>> 10.4.1.4 is that elphel's ip.
>>
>> Do you know how to resolve this issue?
>>
>> Thanks,
>>
>> Mohamed Morsy
>>
>> On Tue, Feb 20, 2018 at 12:49 PM, Oleg <support-list at support.elphel.com>
>> wrote:
>>
>>> Hi Mohamed,
>>>
>>>
>>>> However, I'm still having the same problem. On one of my elphels, when
>>>> I use the recovery card it works fine but when I remove the card the feed
>>>> is very laggy. Do you know what the issue is?
>>>
>>> It's hard to say without seeing the actual bootlog. If you boot from
>>> recovery card, uploaded and flashed *boot.bin*, *u-boot-dtb.img*,
>>> *devicetree.dtb* and *uImage*, but not rootfs.ubi - I would expect some
>>> kind of "kernel panic" on any of the boards.
>>>
>>>
>>>> Also, when I uploaded the files to ipaddress/update_software.html the
>>>> rootf file would not upload. I don't know if that is a problem.
>>>
>>> The Note in my previous letter addresses this problem - the upload limit
>>> in php on the recovery card. There are 3 options:
>>> 1. Copy rootfs.ubi manually
>>>
>>> - http://camera-ip/update_software.html
>>> - upload all files except rootfs.ubi
>>> - from PC terminal window:
>>>
>>> ...$ scp rootfs.ubi root at camera-ip:/var/volatile/html/update/
>>>
>>>
>>> - go back to http://camera-ip/update_software.html - hit 'verify'
>>> and you should see rootfs in the list
>>>
>>> 2. Increase php upload limit of the recovery image on the card
>>>
>>> 2a. when boot from the recovery card:
>>>
>>> - boot from the recovery card
>>> - In the browser: http://camera-ip/phpinfo.php - find:
>>> *post_max_size* and *upload_max_filesize *- they are 128M probably.
>>> - from PC terminal window:
>>>
>>> ...$ ssh root at camera-ip
>>>
>>>
>>> - Edit the /etc/php/php.ini - you will see that the limit is less
>>> than rootfs size - increase it so it will read:
>>>
>>> upload_max_filesize = 512M
>>>>
>>>>
>>>>
>>>> post_max_size = 512M
>>>
>>>
>>> - sync command just makes sure changes are stored on the card.
>>>
>>> root at elphel393:~# sync
>>>
>>>
>>> - restart web server (or reboot)
>>>
>>> root at elphel393:~# /etc/init.d/lighttpd restart
>>>
>>>
>>> - In the browser: http://camera-ip/phpinfo.php - check if those
>>> variables have changed to 512.
>>> - In the browser: http://camera-ip/update_software.html - upload
>>> rootfs, and other files as well
>>>
>>> 2b. If you have a linux os and a usb card reader - insert in PC, mount
>>> rootfs partition and edit /mountpoint/etc/php/php.ini as in 2a.
>>>
>>> 3. Update recovery card. This option requires linux os and a usb card
>>> reader... and a few programs installed: parted, kpartx
>>>
>>> - insert the card - check with dmesg the device name, you will see
>>> something like this:
>>>
>>> [83470.681265] sd 6:0:0:0: [sdb] 7806976 512-byte logical blocks: (4.00
>>>> GB/3.72 GiB)
>>>> [83470.686369] *sdb*: sdb1 sdb2
>>>
>>> If the card is discovered by PC as *mmcblk0* then the script will not
>>> work - as I didn't cover this case.
>>>
>>> - Open konsole, using 'cd' navigate to write_bootable_mmc.py in the
>>> unpacked firmware image (elphel393_20180130/mmc/)
>>> - ...$ sudo ./write_bootable_mmc.py */dev/sdb* (sdb as reported by
>>> dmesg - this is important)
>>> - After the script is done - boot this from this card.
>>>
>>> Best regards,
>>> Oleg Dzhimiev
>>> Electronics Engineer
>>> phone: +1 801 783 5555 x124 <(801)%20783-5555>
>>> Elphel, Inc.
>>>
>>> On Feb 20, 2018 8:20 AM, "Mohamed Morsy" <mmorsy at redzone.com> wrote:
>>>
>>> Hi Oleg,
>>>
>>> Thank you for your help. However, I'm still having the same problem. On
>>> one of my elphels, when I use the recovery card it works fine but when I
>>> remove the card the feed is very laggy. Do you know what the issue is?
>>> Also, when I uploaded the files to ipaddress/update_software.html the rootf
>>> file would not upload. I don't know if that is a problem.
>>>
>>> Thanks,
>>>
>>> Mohamed
>>>
>>> On Mon, Feb 19, 2018 at 6:27 PM, Oleg <support-list at support.elphel.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have 2 Elphel 393 boards and I believe both of their internal flash
>>>>> are corrupt or old. I am trying to update them. Do you have a link for the
>>>>> files or any instructions on how to do so?
>>>>>
>>>>
>>>> Before updating:
>>>> How are you trying to update them? What image do you use?
>>>>
>>>> Update instructions:
>>>> 1. The latest is 20180130 - download and unpack archive from here:
>>>> https://community.elphel.com/files/393/20180130/ (a list of firmware
>>>> images can be found here
>>>> <https://wiki.elphel.com/wiki/Tmp_manual#Firmware_images>)
>>>> 2. Inside there's readme.md with instructions and images for SD card
>>>> and the internal flash.
>>>>
>>>> Note: if you have an old recovery card you will probably need to create
>>>> a new one as rootfs grew a bit bigger than php's upload limit. There's a
>>>> script (*write_bootable_mmc.py*) that will partition the card - it's
>>>> linux only.
>>>> Alternatively you can increase the limit:
>>>>
>>>>
>>>> - boot from the recovery card (default ip address is 192.168.0.9 -
>>>> change with ifconfig if needed)
>>>> - ssh root at camera-ip-address
>>>> - (using nano or vi) edit /etc/php/php.ini:
>>>>
>>>> upload_max_filesize = 512M
>>>>> post_max_size = 512M
>>>>
>>>>
>>>> - save, restart lighttpd or reboot, then 3.
>>>>
>>>> 3. Once boot from a recovery card:
>>>>
>>>> - go to http://camera-ip-address/update_software.html
>>>> - upload all files from *nand/* folder
>>>> - hit flash, wait until done
>>>> - power off, remove card, power on
>>>>
>>>> Let me know if you have any further questions.
>>>>
>>>> Best regards,
>>>> Oleg Dzhimiev
>>>> Electronics Engineer
>>>> phone: +1 801 783 5555 x124 <(801)%20783-5555>
>>>> Elphel, Inc.
>>>>
>>>
>>>
>>> _______________________________________________
>>> Support-list mailing list
>>> Support-list at support.elphel.com
>>> http://support.elphel.com/mailman/listinfo/support-list_supp
>>> ort.elphel.com
>>>
>>>
>>>
>>
>> _______________________________________________
>> Support-list mailing list
>> Support-list at support.elphel.com
>> http://support.elphel.com/mailman/listinfo/support-list_supp
>> ort.elphel.com
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20180221/2ba9d531/attachment-0001.html>
More information about the Support-list
mailing list