<ayaka>
There is an (ARM) platform that have the password protection for the jtag. I could only first enable the first Access port in the DAP
<ayaka>
then write the password to that mem-ap. So I want to separate the configuration file into three ones
<ayaka>
but when I try to use the dap or tap defined in the first file, it seems that it can't find that define
<ayaka>
or it ask me to do it in the proc board_init
slobodan has joined #openocd
<zapb__>
ayaka, do you have a link to this ARM spec?
<zapb__>
or the MCU spec
<PaulFertser>
Protecting JTAG access with a password sounds like something either wrong or evil though? Why would one do that?
<braunr>
preventing product reverse engineering by competitors ?
<braunr>
o/
<PaulFertser>
That sounds anti-user.
<PaulFertser>
As an owner of hardware I think I have a right to know how it works and modify as needed.
<Haohmaru>
you optimist ;P~
<PaulFertser>
Before trying to help someone I'd like to be sure it's not used against me and my friends.
key2 has joined #openocd
<braunr>
well sure
<braunr>
i was just stating one reason why some people would do that
<Haohmaru>
the password is "curseyouifyoustealmycodez"
<braunr>
weak password :P
<Haohmaru>
it has a strong supernatural effect
<ayaka>
PaulFertser, because of the arm trustzone
<ayaka>
zapb__, even I work for the chip vendor, I don't have that. I just figure out how to enable the password from the old script
Haohmaru has quit [Quit: saionara]
<PaulFertser>
ayaka: you can't enable trustzone without setting a password?
<ayaka>
PaulFertser, no, you can't access to the CPU which would run the trustzone without the password
<ayaka>
the trustzone is for arm video trust path, which would have things like keys for digital right content
<ayaka>
I think I found the answer from 6.3.6 The init_targets procedure. I need to add a proc after all the configuration files are parsed
<ayaka>
but there is another problem, it is only meaningful to add mem-ap for cpus after I enabled the password
<ayaka>
is it proper that declare target in init_targets() which is the running stage?
<PaulFertser>
ayaka: by "digital right content" you mean digital restrictions management? Nobody should be implementing that I think.
MGF_Fabio has quit [Ping timeout: 246 seconds]
nerozero has quit [Ping timeout: 260 seconds]
<borneoa___>
PaulFertser: there is a new feature from arm named debug authentication. The chip exposes on DAP only one AP, where the debugger can: read the chip id, read the debug level (bit mask of what the debugger can access), and access some register for handshake for the authentication. Then the authentication allows changing debug level and even opening all the debug resources.
<borneoa___>
PaulFertser: there are already chips in the market with DA, and also ST will follow the "fashion"
<PaulFertser>
borneoa___: this doesn't sound like something I would desire in a hardware I can own... :(
<borneoa___>
PaulFertser: yep! If you buy the naked chip it will not be protected, but once added in a product the manufacturer will lock it and keep one certificate or password to reopen it to debug the returned items.
<karlp>
and the world rejoiced....
<karlp>
ewaste the only winner here.
crabbedhaloablut has quit []
lh has quit [Read error: Connection reset by peer]
lh has joined #openocd
lh has quit [Read error: Connection reset by peer]
bryanb has quit [Remote host closed the connection]
bryanb has joined #openocd
lh has joined #openocd
sugarbeet has quit [Ping timeout: 252 seconds]
sugarbeet has joined #openocd
MGF_Fabio has joined #openocd
MGF_Fabio has quit [Quit: Konversation terminated!]