{"action":"created","issue":{"url":"https://api.github.com/repos/OP-TEE/optee_os/issues/2239","repository_url":"https://api.github.com/repos/OP-TEE/optee_os","labels_url":"https://api.github.com/repos/OP-TEE/optee_os/issues/2239/labels{/name}","comments_url":"https://api.github.com/repos/OP-TEE/optee_os/issues/2239/comments","events_url":"https://api.github.com/repos/OP-TEE/optee_os/issues/2239/events","html_url":"https://github.com/OP-TEE/optee_os/issues/2239","id":312308914,"number":2239,"title":"About TRUSTED_BOARD_BOOT and CryptoCell on Hikey","user":{"login":"spiderkiss","id":16435062,"avatar_url":"https://avatars2.githubusercontent.com/u/16435062?v=4","gravatar_id":"","url":"https://api.github.com/users/spiderkiss","html_url":"https://github.com/spiderkiss","followers_url":"https://api.github.com/users/spiderkiss/followers","following_url":"https://api.github.com/users/spiderkiss/following{/other_user}","gists_url":"https://api.github.com/users/spiderkiss/gists{/gist_id}","starred_url":"https://api.github.com/users/spiderkiss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spiderkiss/subscriptions","organizations_url":"https://api.github.com/users/spiderkiss/orgs","repos_url":"https://api.github.com/users/spiderkiss/repos","events_url":"https://api.github.com/users/spiderkiss/events{/privacy}","received_events_url":"https://api.github.com/users/spiderkiss/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-04-08T14:10:40Z","updated_at":"2018-05-15T21:07:15Z","closed_at":null,"author_association":"NONE","body":"Hi:\r\n\r\nI am a researcher in computer security, so I quite concern about the security part of OP-TEE. \r\n\r\nI am reading the codes of ARM_TRUSTED_FIRMWARE and try to open the flag of \"TRUSTED_BOARD_BOOT\"  to enable the verification during the ARM trusted boot process on Hikey620 with (a little) obsolete codes. \r\n\r\nHowever, after adding configurations in ARM-TF as follow:\r\n\r\n GENERATE_COT  := 1\r\n CREATE_KEYS  := 1\r\n TRUSTED_BOARD_BOOT := 1\r\n AUTH_MOD  := polarssl\r\n POLARSSL_DIR  := /home/user/Downloads/polarssl-1.3.9\r\n\r\n I didn't modify other parts of OP-TEE. And I successfully \"make\" the whole OP-TEE project with no errors. However, when I try to make flash the whole OP-TEE into Hikey, I get the following information:\r\n   \r\nroot@ubuntu:/media/user/apps/devel/hikey_optee# make flash\r\n   LLOADER\r\n +----------------------+\r\n  Serial:  /dev/serial/by-id/usb-???_?????-if00-port0\r\n  Image1:  l-loader/l-loader.bin\r\n  Image2: \r\n +----------------------+\r\n\r\nSending l-loader/l-loader.bin ...\r\n Done\r\n\r\n  FLASH   ptable\r\n < waiting for device >\r\n target reported max download size of 268435456 bytes\r\n sending 'ptable' (17 KB)...\r\n OKAY [  0.007s]\r\n writing 'ptable'...\r\n OKAY [  0.004s]\r\n finished. total time: 0.011s\r\n   FLASH   fastboot\r\n target reported max download size of 268435456 bytes\r\n sending 'fastboot' (1397 KB)...\r\n ...\r\n\r\nIt's jammed when 'fastboot' is being sent to Hikey. Although I tried many times, I got the same output every time. Maybe the latest codes won't have this problem, I guess.\r\n\r\nP.S. Since CryptoCell can offer hardware security guarantee for ARM development, my question is that d\r\ndoes Hikey (620 & 960) support CryptoCell? If supports, does OP-TEE on Hikey support CryptoCell.\r\n\r\nThanks in advance\r\n\r\nShiwei\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/OP-TEE/optee_os/issues/comments/389313655","html_url":"https://github.com/OP-TEE/optee_os/issues/2239#issuecomment-389313655","issue_url":"https://api.github.com/repos/OP-TEE/optee_os/issues/2239","id":389313655,"user":{"login":"gitfineon","id":11716650,"avatar_url":"https://avatars3.githubusercontent.com/u/11716650?v=4","gravatar_id":"","url":"https://api.github.com/users/gitfineon","html_url":"https://github.com/gitfineon","followers_url":"https://api.github.com/users/gitfineon/followers","following_url":"https://api.github.com/users/gitfineon/following{/other_user}","gists_url":"https://api.github.com/users/gitfineon/gists{/gist_id}","starred_url":"https://api.github.com/users/gitfineon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gitfineon/subscriptions","organizations_url":"https://api.github.com/users/gitfineon/orgs","repos_url":"https://api.github.com/users/gitfineon/repos","events_url":"https://api.github.com/users/gitfineon/events{/privacy}","received_events_url":"https://api.github.com/users/gitfineon/received_events","type":"User","site_admin":false},"created_at":"2018-05-15T21:07:15Z","updated_at":"2018-05-15T21:07:15Z","author_association":"CONTRIBUTOR","body":"Read this: https://github.com/ARM-software/arm-trusted-firmware/pull/1166#issuecomment-350764849\r\n\r\nI used this workaround from @raw-bin to manually add padding.\r\nhttps://github.com/ARM-software/tf-issues/issues/528\r\n\r\nTell me if that solves your problem."}}
{"actor":{"display_login":"gitfineon"}}