Missing "run" command on hisilicon U-Boot 2010.6

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,779
Location
Scotland
Question: does this eprom only contain the boot loader or the whole firmware?
It's likely to be the whole firmware - all partitions, such as u-boot, kernel, rootfs, app, config, maybe even system logs.
got another working IPCAM with HI3516 and U-Boot running fine - flash programmer should able to read from that chip to copy over to bad eprom, isnt it?
I thought the problem cameras were 3518-based? You can't mix and match different camera boards.
But in principle - you could read one and write to another identical one, then deal with the problems of duplicate MAC address, serial number unique ID etc.
 

Paul Kuhn

n3wb
Joined
Apr 26, 2018
Messages
18
Reaction score
0
It's likely to be the whole firmware - all partitions, such as u-boot, kernel, rootfs, app, config, maybe even system logs.

I thought the problem cameras were 3518-based? You can't mix and match different camera boards.
But in principle - you could read one and write to another identical one, then deal with the problems of duplicate MAC address, serial number unique ID etc.
yes and no: I've got a 3518 and an additional 3516 based one; both from ieGeek... and ready to go now: CH341A with inplace SOP8 testclip arrived a few days ago but I did not get a full bin-file to flash the 25Q128 spi chip yet... ideas?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,779
Location
Scotland
but I did not get a full bin-file to flash the 25Q128 spi chip yet... ideas?
Neither did I - I went on the ieGeek downloads section for this : B18EV200HX_V11.1.23.5.3-20180413(1080P.38.b041.newp2p.AF.VBR).rar
There is no uImage, no bootloader, it's just app-related content in the firmware.
The 10. version would not download.

Did you say that you have a working camera of the exact same model?
If so, do you have telnet access to it?
 

Paul Kuhn

n3wb
Joined
Apr 26, 2018
Messages
18
Reaction score
0
405 Not Allowed
thats weired: got two of those yesterday evening - today its blocked!

anyway - they look like this:

General_HZXM_IPC_HI3516C_53H20L_S38_V4.02.R11.Nat.OnvifS.20160511_ALL.bin
General_HZXM__IPC_HI3516C_50H20L_RT3070_V4.02.R11.Nat.OnvifS.20160615_ALL.bin

and content is:

custom-x.cramfs.img 21kb
romfs-x.cramfs.img 3.2MB
u-boot.bin.img 61kb
u-boot.env.img 66kb
user-x.cramfs.img 2.4MB
web-x.cramfs.img 1.2MB

...no BIN so far... whats your guess, please?
 

Paul Kuhn

n3wb
Joined
Apr 26, 2018
Messages
18
Reaction score
0
ah missed two little file called "Install" and "InsatllDesc" with content:

// ±æ…˝º∂∞¸ ∫œµƒ”≤º˛¡–±Ì£¨“‘º∞…˝º∂√¸¡Ó–Ú¡–°£

// …˝º∂∞¸µƒø…–≈»Œ–‘”¶∏√µ√µΩ±£÷§£¨∑ґڅ˱∏”–±ªhackµƒø…ƒ‹°£

// …˝º∂∞¸µƒø…–≈»Œ–‘”¶∏√µ√µΩ±£÷§£¨∑ґڅ˱∏”–±ªhackµƒø…ƒ‹°£

{// …˝º∂√¸¡Ó–Ú¡–£¨±ÿ–Î∞¥À≥–Ú÷¥––°£…˝º∂√¸¡Ó∞¸∫¨±Í◊ºµƒshell√¸¡Ó∫ÕÃÿ ‚µƒ”√”⁄…’–¥

// flash∑÷«¯µƒburn√¸¡Ó°£

"Commands" : [
"burn u-boot-all.bin.img boot",
"burn custom-x.cramfs.img custom",
"burn romfs-x.cramfs.img romfs",
"burn user-x.cramfs.img user",
"burn web-x.cramfs.img web"
], // …˱∏¡–±Ì≥…‘±µƒ∏Ò ΩŒ™[…˱∏¿‡–Õ£¨”≤º˛∞ʱæ]
"Devices" : [
[ "53H20L_S39", "1.00" ]
]
}

-------------

{
"UpgradeCommand": [
{
"Command": "Burn",
"FileName": "u-boot.bin.img"
},
{
"Command": "Burn",
"FileName": "u-boot.env.img"
},
{
"Command": "Burn",
"FileName": "custom-x.cramfs.img"
},
{
"Command": "Burn",
"FileName": "romfs-x.cramfs.img"
},
{
"Command": "Burn",
"FileName": "user-x.cramfs.img"
},
{
"Command": "Burn",
"FileName": "web-x.cramfs.img"
}
],
"Hardware": "53H20L_S39",
"DevID": "000025321001000000000000",
"CompatibleVersion": 2,
"Vendor": "General",
"CRC": "1ce6242100007636"
}
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,779
Location
Scotland
and content is:

custom-x.cramfs.img 21kb
romfs-x.cramfs.img 3.2MB
u-boot.bin.img 61kb
u-boot.env.img 66kb
user-x.cramfs.img 2.4MB
web-x.cramfs.img 1.2MB
Maybe, just maybe -

If you know the partition sizes and therefore start locations, and create an empty file the same size as the flash chip, and write the above files in the correct order (some uncertainty there unless you have a partition list, but maybe the 'upgrade order' is correct) then you should have a .bin file to flash with the programmer. And that's assuming romfs-x.img holds uImage amongst other things. You can verify that with binwalk

*edit* Writing the files at the correct start points in the file.
 
Top