• Posts

  • Joined

  • Last visited

Recent Profile Visitors

777 profile views

Ravikumar's Achievements

  1. Hi, I am working on H3 based Nano Pi Neo board. my task is to enable audio and kernel version is 4.4. I tested Armbian image, Audio is working fine(good) and capture working too. Enabled sun4i-codec.c (which has h3 support). I struck with major problem. I am unable to write AC registors(physical address: 1c22c00) but i can read them using readl. writel is not showing any effect on register. I enabled audio_pll, codec clock, bus codec gate registers and reset deasserted. I have cross-checked H3 datasheet for clock tree. Everything looks fine. why writel is not working?? any suggestion.?? help me. Thanks in advance.
  2. Hi, I am running openwrt on allwinner h3 boards with usb dongle. i found after some time, board is restarting. problem is out of memory because of skbuff_head_cache i can see in /proc/slabinfo.. skbuff_fclone_cache 0 0 448 18 2 : tunables 0 0 0 : slabdata 0 0 0 skbuff_head_cache 326740 326768 256 16 1 : tunables 0 0 0 : slabdata 20423 20423 0 Help me
  3. Press the [f] key and hit [enter] to enter failsafe mode Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level [ 1.784418] usb 2-1: New USB device found, idVendor=148f, idProduct=5370 [ 1.791161] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.798300] usb 2-1: Product: 802.11 n WLAN [ 1.802478] usb 2-1: Manufacturer: Ralink [ 1.806486] usb 2-1: SerialNumber: 1.0 [ 1.812060] random: procd urandom read with 27 bits of entropy available Segmentation fault [ 4.923551] procd: - early - [ 4.926494] procd: - watchdog - [ 5.629634] procd: - ubus - [ 5.685167] procd: - init - Please press Enter to activate this console. [ 5.994727] ip6_tables: © 2000-2006 Netfilter Core Team
  4. Please check the following code. https://github.com/BPI-SINOVOIP/BPI-M3-bsp there are some files in u-boot folder sunxi_efuse.c : efuse map and programing sequencing usb_burn.c : __sunxi_burn_key for burning efuse area do you know this code? He is burning e-fuse area via usb device. If you have any information this code. Please share with me.
  5. Thanks for reply, With present configuration, it just verifying checksum. But there are some unknow bits in efuse to enable security of the chip. Please check following code void sid_set_security_mode(void) { uint reg_val; reg_val = sid_read_key(EFUSE_LCJS); reg_val |= (0x01 << 11); //ʹÄÜsecurebit sid_program_key(EFUSE_LCJS, reg_val); reg_val = (sid_read_key(EFUSE_LCJS) >> 11) & 1; return; } I have written security (11-bit), now my board is not booting. I think BootROM trying to verify signature. One more thing, H3 is not a simple soc. it has ARM trust zone and it can run TEE(both linux & secure os at a time). BootROM security must for TEE.
  6. Hi, I bought nanopi_neo boards (for my hobby projects). I am learning about security. I am able to dump e-Fuse area at uboot stage. But i can't modify it (i want to write my own key). I don't have any memory map information of e-fuse. In present boards, bootROM is not verifying the uboot signature(RSA sign:-)). 1) How to enable signature verification in bootROM? 2) Is there any code or information regarding BootROM security and e-Fuse area mapping? 3) Is there any support of TEE (Trusted execution environment)?