hiroshi

The latest beta kernel and device tree blobs as of today still have this problem. Ideas anyone? root@orangepizero:/usr/local/bin# dpkg -l | grep -i "linux-image-dev-sun8i\|linux-dtb-dev-sun8i" ii linux-dtb-dev-sun8i 5.24.170121 armhf Linux DTB, version 4.9.4-sun8i ii linux-image-dev-sun8i 5.24.170121 armhf Linux kernel, version 4.9.4-sun8i root@orangepizero:/usr/local/bin# uname -a Linux orangepizero 4.9.4-sun8i #2 SMP Fri Jan 20 10:22:01 CET 2017 armv7l armv7l armv7l GNU/Linux root@orangepizero:/usr/local/bin# cat /proc/device-tree/model; echo Xunlong Orange Pi Zero root@orangepizero:/usr/local/bin# bash -x hid_testing.sh + cd /sys/kernel/config/usb_gadget + mkdir g1 + cd g1 + echo 0x1d6b + echo 0x0104 + mkdir strings/0x409 + echo 1234567890 + echo 0x1d6b + echo 0x0104 + mkdir functions/hid.usb0 + echo 1 + echo 1 + echo 8 + /bin/echo -ne '\x05\x01\x09\x06\xa1\x01\x05\x07\x19\xe0\x29\xe7\x15\x00\x25\x01\x75\x01\x95\x08\x81\x02\x95\x01\x75\x08\x81\x03\x95\x05\x75\x01\x05\x08\x19\x01\x29\x05\x91\x02\x95\x01\x75\x03\x91\x03\x95\x06\x75\x08\x15\x00\x25\x65\x05\x07\x19\x00\x29\x65\x81\x00\xc0' + mkdir configs/c.1 + mkdir configs/c.1/strings/0x409 + echo Conf 1 + echo 120 + ln -s functions/hid.usb0 configs/c.1 + echo musb-hdrc.1.auto Segmentation fault root@orangepizero:/usr/local/bin# dmesg [SNIP] [ 58.756380] Unable to handle kernel NULL pointer dereference at virtual address 00000002 [ 58.765376] pgd = cdb44000 [ 58.768237] [00000002] *pgd=4d891835, *pte=00000000, *ppte=00000000 [ 58.775106] Internal error: Oops: 17 [#1] SMP THUMB2 [ 58.780210] Modules linked in: usb_f_hid evdev xradio_wlan mac80211 cfg80211 rfkill sun8i_ths gpio_keys uio_pdrv_genirq cpufreq_dt uio thermal_sys libcomposite [ 58.795335] CPU: 0 PID: 1000 Comm: bash Not tainted 4.9.4-sun8i #2 [ 58.801660] Hardware name: Allwinner sun8i Family [ 58.806508] task: ce142ac0 task.stack: cd9ee000 [ 58.811426] PC is at alloc_ep_req+0x15/0x50 [libcomposite] [ 58.817101] LR is at kmem_cache_alloc+0xe5/0xec [ 58.821792] pc : [<bf803e06>] lr : [<c01c2aad>] psr: 200e0033 sp : cd9efdf0 ip : 00000000 fp : cda86298 [ 58.833519] r10: c9c734c4 r9 : ceb77cec r8 : 00000100 [ 58.838890] r7 : c9c734a8 r6 : cd244418 r5 : cda3e900 r4 : 00000008 [ 58.845568] r3 : 00000000 r2 : ffffffff r1 : 00000000 r0 : cda3e900 [ 58.852254] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment none [ 58.859784] Control: 50c5387d Table: 4db4406a DAC: 00000051 [ 58.865679] Process bash (pid: 1000, stack limit = 0xcd9ee210) [ 58.871661] Stack: (0xcd9efdf0 to 0xcd9f0000) [ 58.876179] fde0: bf9200c0 ceb77c94 00000000 bf91f47d [ 58.884617] fe00: c9c73524 cdbbf840 cda861ec bf80090f ceb77c94 c9c734a8 00000200 00000000 [ 58.893055] fe20: 00000100 bf800773 c9c7351c ceb77c94 c9c734a8 00000200 c9c7351c bf803541 [ 58.901491] fe40: cda86000 cda86260 00000000 cd245148 bf805180 cda861ec d0e30270 cd23ac00 [ 58.909926] fe60: c0b48f60 cda861ec cda861ec c0b48f48 cdbbf840 cda26000 00000051 c054e6e3 [ 58.918362] fe80: cd23ac00 c0b48f60 cd41d940 c054e9bb cd41d940 cda86000 cda86190 fffffff0 [ 58.926796] fea0: 00000011 bf803c3b 000cd408 00000000 00000011 cd41d040 000cd408 cd41d058 [ 58.935233] fec0: cd9eff80 c021e91d cd9eff80 cdbbf840 c021e88d c07121f8 cd9eff80 00000000 [ 58.943667] fee0: 00000011 00000000 000c475c c01d032f cc28b700 00000301 00000000 0000034e [ 58.952099] ff00: 00000000 00000000 00000000 cd9eff10 cd9efefc 00000001 cd20f300 00000000 [ 58.960532] ff20: 0000000a 00000100 cdaddf00 cdad0bc0 0000000a c01e5a11 cdbbf840 00000011 [ 58.968966] ff40: 000cd408 cd9eff80 00000000 00000000 000c475c c01d0d95 cd9b0a80 00000000 [ 58.977400] ff60: 00000002 cdbbf840 cdbbf840 00000000 00000000 000cd408 00000011 c01d1937 [ 58.985834] ff80: 00000000 00000000 ce142ac0 00000011 000cd408 b6f70d58 00000004 c0106024 [ 58.994268] ffa0: cd9ee000 c0105e61 00000011 000cd408 00000001 000cd408 00000011 00000000 [ 59.002702] ffc0: 00000011 000cd408 b6f70d58 00000004 00000000 000aa538 000c715c 000c475c [ 59.011135] ffe0: 00000000 bee220ec b6ed479b b6f0ff96 000e0030 00000001 00000000 00000000 [ 59.019800] [<bf803e06>] (alloc_ep_req [libcomposite]) from [<bf91f47d>] (hidg_bind+0x68/0x1c8 [usb_f_hid]) [ 59.030017] [<bf91f47d>] (hidg_bind [usb_f_hid]) from [<bf800773>] (usb_add_function+0x3a/0xcc [libcomposite]) [ 59.040555] [<bf800773>] (usb_add_function [libcomposite]) from [<bf803541>] (configfs_composite_bind+0x1cc/0x2f0 [libcomposite]) [ 59.052638] [<bf803541>] (configfs_composite_bind [libcomposite]) from [<c054e6e3>] (udc_bind_to_driver+0x1b/0x74) [ 59.063279] [<c054e6e3>] (udc_bind_to_driver) from [<c054e9bb>] (usb_gadget_probe_driver+0x9f/0xd4) [ 59.072730] [<c054e9bb>] (usb_gadget_probe_driver) from [<bf803c3b>] (gadget_dev_desc_UDC_store+0x82/0x98 [libcomposite]) [ 59.084118] [<bf803c3b>] (gadget_dev_desc_UDC_store [libcomposite]) from [<c021e91d>] (configfs_write_file+0x91/0xf8) [ 59.095028] [<c021e91d>] (configfs_write_file) from [<c01d032f>] (__vfs_write+0xf/0xb4) [ 59.103302] [<c01d032f>] (__vfs_write) from [<c01d0d95>] (vfs_write+0x71/0x13c) [ 59.110875] [<c01d0d95>] (vfs_write) from [<c01d1937>] (SyS_write+0x2b/0x64) [ 59.118137] [<c01d1937>] (SyS_write) from [<c0105e61>] (ret_fast_syscall+0x1/0x4c) [ 59.125965] Code: d722 4605 b1a0 6a73 (f993) 2002 [ 59.131522] ---[ end trace 05e0855db8c4b557 ]---

OK, so I've now ordered and received my Cubietruck. I decided to go with a 64GB Samsung EVO microSDXC card for storage (in addition to the 1TB hard drive), though I did consider getting a pair of USB sticks and setting them up in a BTRFS RAID 0 configuration. Two USB sticks should perform much better than the single microSDXC card because the USB ports on Cubietruck are independent. However, the improved performance would come at the cost of tying up the only (type-A) USB ports on the board. Also, I'm not sure that nand-sata-install would support such a setup? Anyway... I would like to hook up the Cubietruck serial console via a serial Bluetooth module (like this one), as described here for Cubieboard 1 and Cubieboard 2. Now, since Cubietruck rather inconveniently does not provide 3.3V through UART0, is there any reason not to simply grab GND and 3.3V from pins 1 and 2, respectively, of CN8? I already have 2.54mm to 2.0mm jumper wires (such as these) as well as "normal" 2.54mm to 2.54mm ones. Also, just to be absolutely sure, pins 1 and 2 of CN8 are the two CN8 pins closest to the SATA connector, as shown here, right? (That is, NOT the two CN8 pins closest to the Ethernet connector.) Yes, I'm a total n00b so bear with me.

8GB is enough for the OS, but not enough for my Usenet downloads, which require, in addition to the 1TB hard drive, a separate medium, around 128GB in size. Anyway, since USB sticks are cheaper than microSDXC cards, is there any reason to prefer a microSDXC card to a USB stick? The Cubietruck still seems to be the best fit for my application -- basically running a bunch of servers 24/7, including a particularly I/O intensive one.

Well, it was my impression (from this thread) that the Samsung EVOs were among the better (and more affordable) microSDXC cards for SBC purposes... and I need the SATA port for a 1TB (mechanical) hard drive that would otherwise sit here unused. As a consequence of using a hard drive, it is preferable to have separate media (one for reading and one for writing) when unpacking files, such as Usenet downloads, which will be one of the applications for my Cubietruck. The microSDXC card would be used for storing packed files before they're unpacked to the hard drive. Admittedly, a single 1TB SSD would do the job better than the microSDXC card + hard drive combination, but SSDs of that size are still too expensive, comparatively, and I have the hard drive already. Eventually, I want to run the OS from NAND but mainline support does not seem to be there quite yet. When mainline (and armbian!) NAND support improves sufficiently, then I'll move the OS to NAND and use the microSDXC card exclusively for downloads, as described. In this case the microSDXC card will be accessed mostly sequentially. I've also considered using a USB stick instead of the microSDXC card. Once I can run the OS from NAND, is there any reason to prefer a microSDXC card to a USB stick, at least for my described application?

I'm thinking of getting a 128GB microSDXC card (Samsung EVO) for my Cubietruck. Is this likely to work or is 64GB a hard limit? Of course, I intend to put a sane filesystem on it, like ext4.