kotc
-
Posts
15 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by kotc
-
-
umkay, uboot fixed, didnt even need to do uart rescue (as i was able to boot armbian kernel and write uboot from there to spi). for future reference changes to spi_flash_ids.c:
{"is25wp032", INFO(0x9d7016, 0x0, 64 * 1024, 64, SECT_4K) },
i also had to hack around uboot to enable issi flash. but now i have working uboot booting my armbian-ascii (devuan).
-
on amazon it stated 'v5', so i guess that's that. and confirming on the board is v5_0_1
-
-
so on 2018-11-20 i've ordered an espressobin and tried armbian. and i probably got bitten by "yet another spi chip".
using: U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian (Sep 05 2018 - 21:49:34 +0200)
i get: SF: unrecognized JEDEC id bytes: 9d, 70, 16. from the chip lookup (U10):
IS25WP032 - UNSUPPORTED by armbian as of 2018-11-29
so i will try to gather already seen spi chips and their status with corresponding armbian uboots/kernels. since i'm new in the espressobin land, i ask other owners to post their chips and status.
-
well, i've just found that adding iomem=relaxed makes things work for my case (own uboot with compat flag set when built), thanks jernej! now i need someone with full armbian install to check
-
@MX_Master: so, did you find what was off in armbian's uboot/kernel? because right now you are only sidestepping problem by loading via uboot
-
or not. if i understand schematics correctly, on opi0+2h3 both csi_en and csi_pwr_en are connected to pa08
-
now that i look at it, i enabled PG13 on opi0+2h3, which probably also supplied power and made camera powered. ho hum. funny those little boards, stealing power from any source they can ;). and yeah, i agree camera driver should handle all powering. not to mention it would be nice if it didnt segfault on rmmod
-
hi guys, it looks like mainline uboot doesnt set PG11 (CSI_EN) on opipc etc anymore. i was lucky to have it enabled on my opi0+2h3. so to make camera work on opipc/opipc+/opilite/opi1 you have to:
sunxi-pio -m "PG11<1><0><1><1>"
then load modules (or create uboot which enables it at boot time). and PA17 is CSI_PWR_EN which is already set correctly in fex as vip_dev0_power_en. (btw. on opi0+2 CSI_PWR_EN is PA08).
-
on my tests i got camera working with:
sunxi-pio -m "PG11<1><0><1><1>"before loading modules (opipc+)
-
-
opi0+2H3 8GB emmc:
random random kB reclen write rewrite read reread read write 102400 4 5350 5923 12191 12233 9453 5861 102400 16 17258 19735 28225 27445 24999 18945 102400 512 36332 34508 59980 60008 59936 33483 102400 1024 34079 35472 61459 61508 61546 33952 102400 16384 36899 36954 67638 67631 67605 36413 -
test setup: opi+2e, 3.4.113, ondemand governor, running from ramdisk. header:
SpoilerIozone: Performance Test of File I/O
Version $Revision: 3.429 $
Compiled for 32 bit mode.
Build: linuxContributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
Al Slater, Scott Rhine, Mike Wisner, Ken Goss
Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,
Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,
Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,
Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,
Vangel Bojaxhi, Ben England, Vikentsi Lapa.Run began: Wed Jun 7 10:34:26 2017
Include fsync in write timing
O_DIRECT feature enabled
Auto Mode
File size set to 102400 kB
Record Size 4 kB
Record Size 16 kB
Record Size 512 kB
Record Size 1024 kB
Record Size 16384 kB
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2
Output is in kBytes/sec
Time Resolution = 0.000001 seconds.
Processor cache size set to 1024 kBytes.
Processor cache line size set to 32 bytes.
File stride size set to 17 * record size.card info:
cid : 035344534c30384780d1f92540011269
csd : 400e00325b5900003b377f800a4040af
date : 02/2017
erase_size : 512
fwrev : 0x0
hwrev : 0x8
manfid : 0x000003
name : SL08G
oemid : 0x5344card was bought from xunlong's store. white, red logo, black text, 8GB U1 C10 HCI, "made in china"
sandisk-industrial-8gb-opip2e-internal: random random kB reclen write rewrite read reread read write 102400 4 1907 1998 6985 6813 6093 832 102400 16 6830 7020 13507 13420 13316 47 102400 512 9996 11927 20052 20040 20004 1549 102400 1024 10655 12051 20906 20930 20937 2958 102400 16384 11725 12421 22239 22235 22179 11776sandisk-industrial-8gb-opip2e-usbreader: random random kB reclen write rewrite read reread read write 102400 4 1995 2017 4495 4497 4462 863 102400 16 7085 7147 10656 10669 10284 47 102400 512 10271 10989 17790 17763 17745 1523 102400 1024 10724 11145 18054 18050 18007 2937 102400 16384 10873 11120 18679 18640 18671 9767 -
hello, here is an updated patch for 4.7.0-rc1: http://pastebin.com/raw/U0uWE0Yi
espressobin SPI woes. shall we make a list?
in Marvell mvebu
Posted
@mlevistm: uboot works even without boot env.
1/ stop autoboot by pressing any key early
2/ set bootargs variable with cmdline (assuming you want to boot to sdcard):
setenv bootargs "console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p1 rootwait"
3/ load kernel and dt (your paths might be different):
load mmc 0 0x7000000 boot/Image
load mmc 0 0x6000000 boot/armada-3720-espressobin.dtb
4/ if above went without errrors, boot:
booti 0x7000000 - 0x6000000
5/ once you are in linux, add missing spi flash description and recompile flashimage/uboot, then write it to spi using flash tools (in my case plain dd to mtdblock0 worked),or:
5b/ use the newest image from parallel thread.
6/ once it's written, you should continue with normal armbian first time setup as seen on downloads page (ie. clear env etc).
disclaimer: untested and might contain some typos