The HP IPAQ 6515 uses the boot loader2 password to unlock the full help menu in the serial console interface. It does not allow access to more commands than before and simply shows help for more commands.
If you are interested in viewing the commands there are a couple of passwords that would unlock it depending on your exact 6515 model.
Personally, both BOOTLOADER and 0000000000000000 worked fine for me on a HP IPAQ 6515e and you can enter level 1 directly with 0000000000000000
USB>password BOOTLOADER
HTCSPass.<Y-HTCEUSB>password 0000000000000000
HTCSPass1.CM^EHTCEUSB>
If you typed the wrong password, you will get
USB>password 0000000000000000
HTCSInvalid password
This is a long terminal log of me exploring the IPAQ 6515e’s bootloader firmware
USB>? full
Available monitor commands are:
? [command] [full]
h [command] [full]
r [[register] [[=] [hex_value]]]
eb Addr
eh Addr
ew Addr
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
string [Type [String]]
info [Type [Value]]
password [string]
l [path_name [startAddr offset ["cp"]]]
lnb nb-file [StartAddr [Length [SkipOffset ["cp"]]]]
ppdl [startAddr offset["cp"]]
s StartAddr Count Pattern...
map
cp reg# OPC_2 CRm [value]
stress [Type [Count(Hex)]]
d2s [StartAddr [Len [Type [Append[SkipStartAddr SkipLen]]]]]
s2d
set [Type [Value]]
task [Type [Value [Value1]]]
shmsg [Row [Col ["String"]]]
rbmc [FileName [StartAddr [Len]]]
erase [StartAddr [Len]]
wdata [StartAddr [Len]]
checksum [StartAddr [Len]]
prouter [PortID1[Baud1[PortID2[Baud2]]]]
lw [path_name [startAddr offset ["cp"]]]
rtask [Type [Value]]
rroute [UART Path1[Baud Rate1[UART Path2[Baud Rate2]]]]
HP released this IPAQ as 6510a,b and 6515a, b, c, d e, apparently they are all the same hardware except the 6515s have an additional camera.
UPDATE: Possible cause of these mentioned here
Alot of people including myself have lost the GSM Radio stack from a failed firmware update even though we were all using original firmware updates released by HP.
So far there has been NO FIX for this problem which seems to be caused by HP. Fortunately for me, my IPAQ was still under warranty and I managed to get it fixed by HP and they replaced my main board with no additional cost. Others have not been so lucky and many simply threw their IPAQ away.
So I thought I’d share my research in this matter which was carried out with the help of dim92 and simtech from mobilitytoday’s IPAQ forum. Hopefully this will help someone find a fix, and if you do please update me on that.