OMAP5432 at home !


How are defined the default parameters (well the card boots) if no bootfile is present ?

In the .dtb ?
 
BTW I bought a micro USB 3 to female adapter, pluging devices inside does nothing :/.

http://www.conecticplus.com/adaptateur-usb3-0-a-femelle-vers-micro-usb3-0.html


root@slackware:~# lsusb
Bus 001 Device 003: ID 0424:3503 Standard Microsystems Corp.
Bus 001 Device 004: ID 0424:7500 Standard Microsystems Corp. LAN7500 Ethernet 10/100/1000 Adapter
Bus 001 Device 002: ID 0424:3503 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@slackware:~# lsmod
Module                  Size  Used by
arc4                    1707  2
wl12xx                 49591  0
wlcore                163168  1 wl12xx
mac80211              444917  2 wl12xx,wlcore
xhci_hcd               81631  0
cfg80211              421151  2 mac80211,wlcore
snd_soc_spdif_tx        1424  0
dwc3                   35256  0
snd_soc_omap_abe_twl6040    13359  0
snd_soc_twl6040        21425  1 snd_soc_omap_abe_twl6040
omap_usb3               4028  1
wlcore_sdio             3932  0
palmas_usb              4096  0
dwc3_omap               4020  2 dwc3,palmas_usb
at24                    5174  0
tmp102                  3305  0
snd_soc_omap_mcpdm      5010  0
omap_usb2               3526  2 palmas_usb
snd_soc_omap_abe       32086  2 snd_soc_omap_abe_twl6040,snd_soc_omap_mcpdm
snd_soc_omap_mcbsp     18471  1 snd_soc_omap_abe_twl6040
snd_soc_abe_hal        41237  2 snd_soc_omap_abe,snd_soc_omap_mcpdm
snd_soc_omap_dmic       5528  0
snd_soc_omap_mcasp      5090  0
Your kernel boots fine aTc, thanks !
 
default parameters are compiled into u-boot itself.

usb 3.0 otg not working is normal, TI don't really seem to support it, or have bothered to implement it properly.

http://e2e.ti.com/support/omap/f/885/t/275115 and http://e2e.ti.com/support/omap/f/885/t/277258

http://processors.wiki.ti.com/index.php/Linux_Core_DWC3_User%27s_Guide#Features_NOT_supported

I don't expect the situation to be any better with the igep board, since their stuff is heavily based on TI's.

Support from igep isn't that great either, they won't update the .dts for the board to support more recent kernels. So you're pretty much stuck with their "ancient" 3.8 kernel.

hns did try a few things with his kernel version, but that didn't work in usb 3.0 mode either
 
Last edited by a moderator:
That's sad.

Trying your rootfs, things went strange, I have tons of :

Code:
[     *] A start job is running for Pyra First Run Wizard (7min 14s / no limit)
 
Last edited by a moderator:
weird, does the first run wizard show up on the hdmi output ?

And did you make sure to copy all the kernel modules and firmware to /lib ?
 
I'll connect hdmi.

I copied only the base modules directory, not the wifi addons.

---EDIT: ah, maybe I missed firmware :) .
 
Last edited by a moderator:
Same problem.

I don't use wifi.

Code:
[  OK  ] Started Network Manager.
Manager.
[   15.932586] wlcore: ERROR could not get firmware ti-connectivity/wl127x-fw-5-sr.bin: -2
[  OK  ] Started LSB: exim Mail Transport Agent.
[   16.357208] wlcore: ERROR couity/wl127x-fw-5-sr.bin: -2
ld not get firmware ti-connectivity/wl127x-fw-5-sr.bin: -2
[   16.769897] wlcore: ERROR firmware boot failed despite 3 retries
[   18.600738] smsc75xx 1-2.3:1.duplex, lpa 0xCDE1
         Starting Network Manage[  OK  ] Started Network Manager Script Dispatcher Service.
[  *** ] (1 of 2) A start job is running for dev-ttyO2.device
 
Last edited by a moderator:
I took /lib/firmware/ti-connectivity/* from Slack, and it finished booting.

What are login/password ?
 
Last edited by a moderator:
I have tons of wlcore crashes.

Systemd hadn't finished booting in fact...
 
login/password is root/root

The normal users are set up in the first-run-wizard

I don't remember wally having these issues with his board.

The most weirdness he had was caused by him not extracting the rootfs to the sd card as root.

Are you sure you're using, and booting, the right kernel and modules ?

you could retry reinstalling the complete rootfs, with all the modules and firmware, maybe something went wrong during the setup stage on the very first boot.
 
^ Jessie has password auth for root disabled in sshd by default, this was not the default in Wheezy
 
Last edited by a moderator:
I don't get how I mount the NAND :


$ ls /dev/mmcblk1
mmcblk1       mmcblk1boot0  mmcblk1boot1
---EDIT :

Some fdisk output :

Code:
root@darkstar:~# fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@darkstar:~# fdisk -l /dev/mmcblk1boot0
Disk /dev/mmcblk1boot0: 2 MiB, 2097152 bytes, 4096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@darkstar:~# fdisk -l /dev/mmcblk1boot1
Disk /dev/mmcblk1boot1: 2 MiB, 2097152 bytes, 4096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Last edited by a moderator:
the lite version has no NAND which I can tell you have due to the 1GB of RAM.

If you did infact order the 4GB model. Good luck getting iGEP to fix the issue.
 
ignore the boot0 and boot1 partitions, the rest just behaves like a normal sd card, just one you can't remove.
 
According to you (Wally), Kernel 4.0 needs a DTS file and iGEP don't have that file and can't be bothered making one.

But isn't a DTS a text file with parameters that is compiled along with the kernel ?
 
Last edited by a moderator:
ignore the boot0 and boot1 partitions, the rest just behaves like a normal sd card, just one you can't remove.
Great !

I suppose i can do the fat + ext4 partition writing MLO and u-boot.bin in fat first ?

---EDIT : didn't work :/
 
Last edited by a moderator:
it should work, but just like booting from a normal sd card, the partitioning and formatting and copying of files has to be EXACTLY right, or it won't do anything.

You might have to change the switches on the board to make it boot from emmc though. igep should have some docs on them somewhere.
 
Back
Top