Just for anyone interested, I've been releasing experimental disk images
of CoreOS  for the HiKey ARM64 developer board. These images
currently have about 90% of the packages in the CoreOS developer build.
See the README at https://github.com/glevand/hikey-coreos.
[cc'ing dev list. This can be discussed in public]
On Wed, Sep 30, 2015 at 12:37 PM, Daniel Thompson
> Hi Grant
> On 28/09/15 15:57, Grant Likely wrote:
>> On Mon, Sep 28, 2015 at 3:47 PM, Grant Likely <grant.likely(a)linaro.org>
>>> Update on the Sensors board.
>>> Unfortunately, some of the boards got shipped out without the Arduino
>>> bootloader installed on the Atmel. Before you can use the procedure in
>>> the starter guide, you'll need to disconnect the Sensors board from
>>> your 96boards baseboard and flash the bootloader. Pretty much any
>>> flashing method will work, but the easiest is probably to use another
>>> Arduino as a programmer as documented here (unless you already have an
>>> AVR-ISP programmer, in which case use that):
>>> I've also updated the getting started guide.
>>> Sorry for the inconvenience. Let me know if you have any trouble
>>> flashing the bootloader.
>> Also, can you please let me know if your board was missing the
>> bootloader, and if you were able to get it reflashed?
> Not sure if you want private e-mail to report troubles with the AVR or if I
> should put it on dev@... For now I've just done a straight reply but I'm
> happy to widen things.
> Either but anyhow my sensors board really isn't doing what I would expect.
> I've run a quite a few different experiments after looking at the schematic
> to try and figure out what is going on. The (somewhat lengthy) results are
> as follows:
> 1. When power is applied to baseboard (Dragonboard 410c in my case) the
> PB5 LED (red) comes on briefly then goes out and it replaced by the
> reset LED (blue).
> 2. avrdude (run via make upload) fails with "avrdude: stk500_getsync()
> attempt 1 of 10: not in sync: resp=0x00" errors. When avrdude is run
> the blue LED goes out and PB5 starts to blink.
Sounds like the bootloader is indeed missing and the manufacturing
test sketch is still on the board. The test sketch blinks LEDs on all
> 3. Running avrdude again interrupts the timing of the blink sequence
> It looks like avrdude can place the AVR into reset.reset.
Yes, that sounds right.
> 4. Shorting UART0 TX/RX on the LS connector (with the sensors board
> not fitted) results in character echo so we know the Dragonboard UART
> is able to send receive characters.
> 5. Shorting TX/RX after level shifting does *not* result in character
> echo. I tried on the arduino connector (P5) and directly on AVR pins
> 30 and 31.
This may not work as the AVR is also driving the UART RX signal. It
probably prevents the signal from going low enough to be detected.
> 6. I can light D7 using GPIO36 and the sysfs interface although the
> lamp strength is very weak.
I will check into that on my board.
> 7. Connecting a SW to P12 allows me to read the state of the switch.
> D7 also lights up and the lamp strength is much brighter. This is
> since in both cases
> 8. USBtinyISP cannot program the AVR using the ISP connector. I have
> checked the programmer with another ATMega328P based board and it is
> working OK.
I've not tried the ISP connector. It may be that we screwed it up
somehow. George, have you tried it? This was the very first batch of
boards, so there are things that I know are wrong and will be fixed
before going into production.
> avrdude: Using SCK period of 10 usec
> avrdude: initialization failed, rc=-1
> Double check connections and try again, or use -F to override
> this check.
> 9. (I suspect you have already discovered this but just in case...) the
> P2 (arduino 1x10) and P3 (ISP) are too close together to allow
> a normal IDC connector to be attached to P3. ;-)
For the next run I want to move the ISP connector down to the same
location it is on a real arduino. That will solve the connector
problem and also make it compatible with more shields.
> I'm pretty confused at this point, to the point of suspecting multiple
> faults. Next steps for me will be with a continuity tester...
Actually, most of this sounds to be symptoms of a missing bootloader.
Since you can't get USBtinyISP to program the board, do you have an
arduino board handy that you can run the ArduinoISP sketch on? I used
the following instructions for flashing the bootloader:
Feel free to make comments on the Getting Started guide as you find things.
I'm just trying to kick the tyres of my sensors board. I'm using a
dragonboard because that's the board I have "spare" to play with.
I've tried to play "dumb" and follow only documented instructions... as
a result I have a dragonboard flashed with the latest builds of the
boot-and-rootfs from the releases directory.
This build does not play nicely with the sensors board because
/dev/ttyMSM1 does not exist. As a result I cannot use the UART0 pins on
the LS connector to try and talk to the AVR (i.e. this is *not* the
known issue that the AVR may have no bootloader).
I haven't yet made much of a attempt to debug this (and won't until
tomorrow at best). However... has anyone already overcome this problem?
Does anyone have a canned command to deliberately corrupt the
boot-and-rootfs so I can get the board to jump into fastboot (so I can
try a snapshot) without having to take the sensors board of the top so I
can press Vol- ;-) ?
We would need to use UART2 in final stages of A-T-F. (UART0 and UART3 works fine)
We seem to be able to initialize and direct prints but nothing is transmitted at UART2 TX.
Have anybody successfully used UART2 for log prints ?
-CONSOLE_BASE := PL011_UART3_BASE
-CRASH_CONSOLE_BASE := PL011_UART3_BASE
+CONSOLE_BASE := PL011_UART2_BASE
+CRASH_CONSOLE_BASE := PL011_UART2_BASE
+#define PL011_UART2_BASE 0xF7112000
After roughly went through Hikey's schematics, found BUCK1_1V05 is to
power on ACPU's domain; so i'm trying to create hardware profiling
enviornment for CPU's power consumtion on Hikey. Here i need some
suggestions before can move forward:
- I searched schematics file, have not found there have on-board power
measurement chip; so if Hikey has such current/power measurement chip,
could you help point out? This will be much easier for us to do
profiling (similiar with TC2 boards).
- If we need use external power monitor / power meter to measure the
SoC's power, could you give some recommendation?  is a good one
power monitor which i used before, but it's expensive (> 700$), so
just want to check if have other better choices.
Thanks in advance,
I needed the kernel config changes below to cleanup most of
the 'missing' options found by the docker check-config script
when run on the Linaro 15.06 hikey kernel.
@@ -112,8 +112,9 @@
-# CONFIG_CGROUP_DEVICE is not set
-# CONFIG_CPUSETS is not set
@@ -121,12 +122,13 @@
-# CONFIG_CGROUP_PERF is not set
-# CONFIG_CFS_BANDWIDTH is not set
-# CONFIG_BLK_CGROUP is not set
+# CONFIG_DEBUG_BLK_CGROUP is not set
# CONFIG_CHECKPOINT_RESTORE is not set
@@ -239,6 +241,7 @@
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
+# CONFIG_BLK_DEV_THROTTLING is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
@@ -255,6 +258,7 @@
# CONFIG_IOSCHED_DEADLINE is not set
+# CONFIG_CFQ_GROUP_IOSCHED is not set
# CONFIG_DEFAULT_NOOP is not set
@@ -539,6 +543,7 @@
# CONFIG_NETFILTER_DEBUG is not set
# Core Netfilter Configuration
@@ -572,6 +577,16 @@
# CONFIG_NF_CT_NETLINK_TIMEOUT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE_CT is not set
+# CONFIG_NF_NAT_SIP is not set
# CONFIG_NF_TABLES is not set
@@ -597,10 +612,13 @@
# CONFIG_NETFILTER_XT_TARGET_LED is not set
# CONFIG_NETFILTER_XT_TARGET_LOG is not set
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
+# CONFIG_NETFILTER_XT_TARGET_REDIRECT is not set
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
@@ -611,7 +629,7 @@
# Xtables matches
-# CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_BPF is not set
# CONFIG_NETFILTER_XT_MATCH_CGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
@@ -642,6 +660,7 @@
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
+# CONFIG_NETFILTER_XT_MATCH_PHYSDEV is not set
@@ -669,7 +688,11 @@
# CONFIG_NF_LOG_ARP is not set
# CONFIG_NF_LOG_IPV4 is not set
-# CONFIG_NF_NAT_IPV4 is not set
@@ -678,7 +701,10 @@
# CONFIG_IP_NF_TARGET_SYNPROXY is not set
-# CONFIG_IP_NF_NAT is not set
+# CONFIG_IP_NF_TARGET_REDIRECT is not set
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_TARGET_ECN is not set
@@ -715,16 +741,20 @@
# CONFIG_IP6_NF_SECURITY is not set
# CONFIG_IP6_NF_NAT is not set
+# CONFIG_BRIDGE_NF_EBTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
-# CONFIG_BRIDGE is not set
+# CONFIG_BRIDGE_IGMP_SNOOPING is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
@@ -777,7 +807,7 @@
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
-# CONFIG_NET_CLS_CGROUP is not set
# CONFIG_NET_CLS_BPF is not set
@@ -810,8 +840,8 @@
-# CONFIG_CGROUP_NET_PRIO is not set
-# CONFIG_CGROUP_NET_CLASSID is not set
# CONFIG_BPF_JIT is not set
@@ -1172,9 +1202,12 @@
# CONFIG_DM_DEBUG is not set
+# CONFIG_DM_DEBUG_BLOCK_STACK_TRACING is not set
# CONFIG_DM_SNAPSHOT is not set
-# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_ERA is not set
# CONFIG_DM_MIRROR is not set
@@ -1204,13 +1237,14 @@
# CONFIG_NET_FC is not set
# CONFIG_IFB is not set
# CONFIG_NET_TEAM is not set
-# CONFIG_MACVLAN is not set
+# CONFIG_MACVTAP is not set
# CONFIG_VXLAN is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
-# CONFIG_VETH is not set
# CONFIG_NLMON is not set
# CONFIG_ARCNET is not set
@@ -1593,7 +1627,7 @@
-# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_SERIAL_NONSTANDARD is not set
@@ -3254,12 +3288,18 @@
# CONFIG_EXT2_FS is not set
-# CONFIG_EXT3_FS is not set
-# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_DEBUG is not set
+# CONFIG_JBD_DEBUG is not set
# CONFIG_JBD2_DEBUG is not set
@@ -3757,7 +3797,7 @@
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
-# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set