Mohamed,

It may be that the corner is not cut off enough (mechanical switch is still 
engaged) or the card does not have a resistor on D3. When selecting the card we 
X-rayed multiple brands - many cards have active components in that area and do 
not survive cutting the corner off. Does it still work when inserted into the 
normal adapter?

Andrey


 

---- On Mon, 26 Feb 2018 13:28:36 -0800 Mohamed Morsy<mmo...@redzone.com> 
wrote ---- 

Hi Oleg,

I'm experiencing another issue. I'm trying to create a bootable micro sd card. 
I was able to get it to work on one of my elphels (the older one that doesn't 
work without a card). However it's not working with the other 3 newer elphels. 
They just boot using NAND memory. I filed off the corner on the card I'm using 
so it's like the recovery card. Do you know what the issue might be?


Thanks,


Mohamed


On Thu, Feb 22, 2018 at 2:08 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
That worked. Thanks

On Thu, Feb 22, 2018 at 1:04 PM, Oleg <support-list@support.elphel.com> 
wrote:
You don't have to close minicom.


It works with the card, right? Then:

1. If the board is one of the first we sent you (what's the serial number?) 
then... later we had to make a minor fix. The problem was it wouldn't boot from 
flash without a card.


Try: if you have some other micro sd card at hand (w/o a cut corner) - insert 
it and see if it boots. If yes then you can send us the board and we will fix 
it.


2. Make sure you flashed boot.bin.


Oleg






On Thu, Feb 22, 2018 at 10:38 AM, Mohamed Morsy <mmo...@redzone.com> 
wrote:
The 2 leds (green and yellow) are on. I'm using power from a battery without 
the traco board. This is what I did with the 1st board. I also have the traco 
board if i need it which is 18-75V. I haven't changed anything in minicom. I 
just flashed with the recovery card in, removed it, and tried to connect with 
minicom but I can't type anything in.

On Thu, Feb 22, 2018 at 12:01 PM, Oleg <support-list@support.elphel.com> 
wrote:
No it doesn't print anything at all. I can't connect via ssh. Is it possible 
the baud rate isn't 115200?No. 
Any network leds blinking? Or at least light up temporarily?
Is the board getting warm?
Do you power with the power supply board (TRACO)? Is it the same you used for 
the 1st board? Is it "18-75V" or "9-36V" - can't remember if you have both 
types.
Did you guys manage to power 10393 with 3.3V directly (Todd asked about this 
recently)? In this case you can check the current.

On Thu, Feb 22, 2018 at 9:44 AM, Mohamed Morsy <mmo...@redzone.com> wrote:
No it doesn't print anything at all. I can't connect via ssh. Is it possible 
the baud rate isn't 115200?

On Thu, Feb 22, 2018 at 11:35 AM, Oleg <support-list@support.elphel.com> 
wrote:
Hi,

Is it printing anything when you power on?
Can you connect to the camera via ssh?


Oleg

On Thu, Feb 22, 2018 at 7:38 AM, Mohamed Morsy <mmo...@redzone.com> wrote:
Hello Oleg,

I was able to fix one of my elphels yesterday using the methods you suggested. 
Now I'm trying to do the same with my other one but when I open the minicom 
console I can't type anything. Do you have any idea how to fix this?


Thanks,


Mohamed


On Wed, Feb 21, 2018 at 4:06 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
Thank you very much

On Wed, Feb 21, 2018 at 3:53 PM, Oleg <support-list@support.elphel.com> 
wrote:
Alright. Since you're modifying files on flash rootfs, don't forget to 
run:root@elphel393:~# overlay_sync 1 
root@elphel393:~# shutdown -hP now




On Wed, Feb 21, 2018 at 1:50 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
actually i think i found my answer.

Thanks!


On Wed, Feb 21, 2018 at 3:44 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
ok so the ip was 192.168.0.9. I changed it and it works. But when i power it 
off and restart it, it goes back to 192.168.0.9. Do i have to save it somehow?

On Wed, Feb 21, 2018 at 3:35 PM, Oleg <support-list@support.elphel.com> 
wrote:
It's 'root'

On Wed, Feb 21, 2018 at 1:32 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
It's asking for a login and password. I know the password is pass but what is 
the login?

On Wed, Feb 21, 2018 at 3:12 PM, Oleg <support-list@support.elphel.com> 
wrote:
Get the serial console up and type:root@elphel393:~# ifconfig
On Wed, Feb 21, 2018 at 1:08 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
Is it possible the ip address of the elphel changed. If so, how do i find it?

-Mohamed


On Wed, Feb 21, 2018 at 1:52 PM, Mohamed Morsy <mmo...@redzone.com> wrote:
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@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 <mmo...@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@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@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@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 = 512Msync command just makes sure changes are stored on the card.
root@elphel393:~# syncrestart web server (or reboot)

root@elphel393:~# /etc/init.d/lighttpd restartIn 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 sdb2If 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
Elphel, Inc.



On Feb 20, 2018 8:20 AM, "Mohamed Morsy" <mmo...@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@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)
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@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
Elphel, Inc.
 

 


 



_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 




 

 


 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

 



 


 




 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 







-- 
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 5555 x124
Elphel, Inc.
 


 


 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 





-- 
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 5555 x124
Elphel, Inc.
 
 




 




 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 





-- 
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 5555 x124
Elphel, Inc.
 
 




 




 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

 




 


 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 





-- 
Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 5555 x124
Elphel, Inc.
 




 


 


_______________________________________________
 Support-list mailing list
 Support-list@support.elphel.com
 http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

 



 


 




 _______________________________________________ 
Support-list mailing list 
Support-list@support.elphel.com 
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com 





_______________________________________________
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

Reply via email to