Zynq Petalinux 2014.4 device tree node for two SD card interfaces?

Question

I'm using a 3rd party zynq module (Trenz TE0720) for which they provide a .bsp file.  The resulting Petalinux build boots just fine out of the SD card.  But the module also has an on board eMMC memory that should look llike second SD card and it is connected to the zynq's second sdhci controller.  But Linux is unaware of its existence.
The likely cause is an omission from the device tree script and I would imagine it should be possible to add the missing device tree node.  However all of attempts thus far have failed.  The (very simple) device tree script looks like the below.
Can anyone point me to a correct SD card device tree node for a Petalinux 2014.4 device tree script?  Also the full present device tree script archive is attached.  Thanks!
/dts-v1/;
/include/ "system-conf.dtsi"
aliases {
mio = &gpio0;
/* TE0720-02 uses Spansion Flash */
&qspi {
flash0: flash@0 {
compatible = "spansion,s25fl256s1";
&usb0 {
dr_mode = "host";
&gem0 {
phy-handle = <&phy0>;
mdio {
#address-cells = <1>;
#size-cells = <0>;
phy0: phy@0 {
compatible = "marvell,88e1510";
device_type = "ethernet-phy";
reg = <0>;
/* restore LED settings */
marvell,reg-init = <0x3 0x10 0x0000 0x0501 0x3 0x11 0x0000 0x4415>;
&i2c1 {
/* Real Time Clock RAM is not supported, map as EEPROM */
eeprom@57 {
compatible = "at,24c01";
reg = <0x57>;
/* Real Time Clock, rtc0 name can used to set time at startup! */
rtc0: rtc@6F {
compatible = "isl12022";
reg = <0x6F>;
};

Answer 1

I figured out a solution by myself:
The Kernel image was not read from the correct position in the QSPI flash. In order to find out which is the correct address to read from, I modified the .bif-file (./build/bootgen.bif)  that was generated by petalinux-package:
the_ROM_image:
[bootloader] ./images/linux/zynq_fsbl.elf
./images/linux/u-boot.elf
./images/linux/image.ub
Then I executed:
bootgen -image newbif.bif -o test.bin -debug -w
The -debug is important here. This gave me:
*** After Link
-- Dump of Binary cache ----
00000000 Len: 000008a0 Res: 00000000 "BootHeader"
000008c0 Len: 00000014 Res: 00000000 "ImageHeaderTable"
00000900 Len: 00000024 Res: 00000000 "ImageHeader zynq_fsbl.elf"
00000940 Len: 00000020 Res: 00000000 "ImageHeader u-boot.elf"
00000980 Len: 00000020 Res: 00000300 "ImageHeader image.ub"
00000c80 Len: 00000040 Res: 00000000 "PartitionHeader zynq_fsbl.elf.0"
00000cc0 Len: 00000040 Res: 00000000 "PartitionHeader u-boot.elf.0"
00000d00 Len: 00000040 Res: 00000000 "PartitionHeader image.ub.0"
00000d40 Len: 00000040 Res: 000009c0 "PartitionHeader Null"
00001700 Len: 0001800c Res: 00000000 "zynq_fsbl.elf.0"
00019740 Len: 00043054 Res: 00000000 "u-boot.elf.0"
0005c7c0 Len: 00691ac0 Res: 00000000 "image.ub.0"
-- End of Dump
Here we see that the Kernel image is to be found at an offset of 0x0005c7c0 and has a length of 0x00691ac0.
The image can therefore be booted in u-boot by doing:
U-Boot-PetaLinux> sf read $netstart 0005c7c0 00691ac0
SF: 6888128 bytes @ 0x5c7c0 Read: OK
U-Boot-PetaLinux> bootm $netstart
This loads and successfully boots the kernel, finally presenting me a login prompt.
Hope this helps someone in the future.