Support for Hitachi SuperH4 VxWorks 5.5 platform
brainstorm opened this issue · comments
Hello PAGalaxyLab,
I've tried to run vxhunter against a VxWorks5.5 firmware that has Hitachi SuperH4 processor as underlying platform, but unfortunately it did not decode any functions during firmware_init.py
:
vxhunter_firmware_init.py> Running...
[INFO ][vxhunter_core.find_symbol_table] symbol table start offset: 0xafa680
[INFO ][vxhunter_core.find_symbol_table] symbol table end offset: 0xafa750
[INFO ][vxhunter_core._check_vxworks_endian] VxWorks endian: Little endian(2)
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x0
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x2000
[INFO ][vxhunter_core.quick_test] load address is not:0x80002000L
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x10000
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x1000
[INFO ][vxhunter_core.quick_test] load address is not:0xf2003fe4L
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x100000
[INFO ][vxhunter_core._check_load_address] strings at offset didn't match symbol table
[INFO ][vxhunter_core.quick_test] load address is not:0x107fe0
[INFO ][vxhunter_core.find_symbol_table] symbol table end offset: 0xafa750
[INFO ][vxhunter_core._check_vxworks_endian] VxWorks endian: Little endian(2)
substring not found
vxhunter_firmware_init.py> Finished!
I would be happy to share the firmware from my device with you, privately. Please shoot me an email over:
brainstorm at nopcode dot org
If you are interested in improving vxhunter for this platform ;)
Cheers!
@brainstorm I updated VxHunter codes for #2, it's should work for your firmware.
Works like a charm, thanks!