-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to flash / interrupt Hi3518EV200 #1646
Comments
Curious enough; 'liteosconf' seems to be related to 'Huawei Lite OS' making me think again that HiSilicon is tightly coupled to Huawai? :) |
So after re-attaching the camera, things boot again! totally weird; AND i can access the U-Boot console via
Full log below
[/summary] I might try at some point to remove the camera again, and let it sit there for an hour to see if it continues to boot without a camera at all ... |
Sadly, I can't store the files on an SD card; all mmc writes (to different sizes of SD cards) fail with
Stupidly though, as mentioned above, things do get probed from U-Boot. Copying files from LiteOS to the card also works just fine. Any thoughts? Looks like, while some I thought I could ymodem files out; but that also doesn't work. Going to see what commands liteos has to dump something, otherwise, reading the serial flash externally might be the only way ... edit: So the U-Boot of 2010 requires the dev to be passed into 'write'. https://github.com/u-boot/u-boot/blob/v2010.06/common/cmd_mmc.c#L233 or rather, following https://openipc.org/cameras/vendors/hisilicon/socs/hi3518ev200 doesn't work because of the ancient u-boot, which ommits the dev argument. |
Hi all,
I have was donated a 'Hi Tone' doorbell featuring an HI3518EV200. I've taken it appart to just the bare PCB, but other then U-Boot logs, I'm not getting any boot information from the device any more.
Booting with the reset button pressed, I'm getting slightly more information, but still not enough to identify what to google for to interrupt the bootloader. Could be that it's completly locked, or that my TX line of the USB to UART adapter is not arriving properly at the RX of the board (the adapter itself works fine and was used more often, i can see letters echo'ed from the boot sequence, I think it's the BROM, though returning a different letter then what I pressed :/)
Here is the log when I keep the reset button pressed
While I'd be suprised if U-Boot had support for the camera module; I did remove all peripherials, e.g. buttons, speakers, camera etc.
Is this a known u-boot variant? Any clue's on what the interrupt sequence might be? Any tricks to trick u-boot into flashing something from the uSD/USB port? (I think the USB port is power only, as I do not see anything on
dmesg
on my host ...The text was updated successfully, but these errors were encountered: