how to make LS2088 boot from NOR flash?

[wenceslas_godar]

I try to boot the LSDK1909, on the LS2088ARDB.

I read it can only be made through parallel (or QSPI NOR) flash.

so i try to copy the image on it.

I tried:

# flashcp firmware_ls2088ardb_uboot_norboot.img /dev/mtd0

but I got follwowing  error:

   "nand_do_write_ops: attempt to write non page aligned data"

1/ is this the right way or shall I run another command to prepare the boot ?

2/ if right, what is the way to solve my issue ? (and opt. what will be the next step...?)

 thanks

[ufedor]

Is the RDB board directly connected to the Linux host?

Please consider that DPMAC5 is connected to the ETH0 front panel and it has to be PRIME.

[wenceslas_godar]

Hello, Aa the log-on service is unavailble on NXP,

I answer by email to follow up the thread.

Thanks because the card is now back to OK.

But still we are not able to boot the firwware nor boot image.

- We have tftp’ed it to a0000000 -> OK

- We “protect … “ the alternate bank -> ?

- We “xqisis_reset altbank”

è We get “bad FIT kernel Image Format” error

Question(s):

For the protect command with replace $sizefile by the size in HEX of the firware_xxx.img file is it ok or shall it be the size as return by “ls –al” in decimal ?

Is this the right way to do?

or shall we power on / off manually ?

or use a booti/boot/bootm command ?

Thanks

De : ufedor

Envoyé : lundi 18 novembre 2019 14:13

À : GODARD, Wenceslas <wenceslas.godard@airbus.com>

Objet : Re: - Re: how to make LS2088 boot from NOR flash?

NXP Community <https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: how to make LS2088 boot from NOR flash?

reply from ufedor<https://community.nxp.com/people/ufedor?et=watches.email.thread> in QorIQ Processing Platforms - View the full discussion<https://community.nxp.com/message/1233846?commentID=1233846&et=watches.email.thread#comment-1233846>

[ufedor]

> But still we are not able to boot the firwware nor boot image.

Please provide the firmware programming log and U-Boot booting log after that.

[wenceslas_godar]

It worked !

I tried again and it worked:

1/ "tftp  a0000000...."

2/ "protect... && ... &&... " on the current bank

3/ reset

I guess the error was coming from a wrong  "$filesize" in the protect command  (at first)

Thanks a lot for all the help  !

[wenceslas_godar]

thanks for the help.

The "tftp a0000000 firmware_ls2088ardb_uboot_norboot.img"  command was successfull

HOWEVER, after verifying the Switches and jumper are set up  for a BANK 0 boot, and booting:

when type "cat /etc/issue",  we  still NOT get the excepted "NXP LSDK 19.09"

    (instead we still get "QorIQ SDK (FSL Reference Distro) 2.0 \n \l" )

So as user guide mention we tried

=> protect off 580000000 +$filesize && erase 580000000 +$filesize && cp.b a0000000 580000000 $filesize

 with $filsize the hex size of our image....

We then have resetted the board  ("boot" failed and asked for it...)

And then Nothing, the PWR board is orange, there has been a 3 green LED chaser for a while (not too far from the switch but nothing else) of course putty is no longer displaying anything :smileysad:

We are sacred we lost the board... 

[ufedor]

Try to boot after setting SW9[3]=ON

[wenceslas_godar]

I tried, PWR button is now green (instead of amber)

However,  "putty" console shows Nothing at all

[ufedor]

Please refer to the following Community thread:

https://community.nxp.com/message/1079924 

[ufedor]

Please refer to the Layerscape Software Development Kit User Guide, Rev. 19.09, 4.1.2 Download and deploy LSDK images with flex-installer:

On LS2088ARDB:
=> load mmc 0:2 a0000000 firmware_ls2088ardb_uboot_norboot.img
or tftp a0000000 firmware_ls2088ardb_uboot_norboot.img
To program alternate bank:
=> protect off 584000000 +$filesize && erase 584000000 +$filesize && cp.b a0000000 584000000 $filesize
To program current bank:
=> protect off 580000000 +$filesize && erase 580000000 +$filesize && cp.b a0000000 580000000 $filesize

[wenceslas_godar]

thanks for the answer, BUT the "load" command does not exist on my LS2088 bootloader.

Is the right way to make it is by using "loadb" instead (or loadx, loady ...) ?

which command should I type?

reminder: my goal is to have the LSDK19.09 on a LS2088 

[ufedor]

Please refer to the Layerscape Software Development Kit User Guide, Rev. 19.09, 4.1.2 Download and deploy LSDK images with flex-installer:

tftp a0000000 firmware_ls2088ardb_uboot_norboot.img

[wenceslas_godar]

Sorry to reply agian but I tried also unsuccesfully

I run into "TFTP retry count exceeds" , when I set the serverip to 192.168.10.1 for example Icannot even ping it (I got ARP tiemout)

from the uboot, i did  set serverip, ipaddr, I also set ethaddr and ethact

i tried to set staticIP Address for my EThernet interface, added corrsponding ARP resolution on the host, and launch some dnsmasq in order to get tftp server

By the way I also saved for ever and therfore erased the inital "ethaddr" value that was set and I am not sure how to get it back. Would that be an issue ?

( so I set it io the  ethaddr2 instead) 

[ufedor]

Please provide as textual attachment complete U-Boot log including "printenv" output.

[wenceslas_godar]

Thanks for the reply,

here is the output of printenv after my sauvenv command that may have lost for ever the original "ethaddr" .The bold are the other I try to change but as I cannot find no information on how to set them up and what to do on the host machine neither, I did try some magic :smileysad: 

=> printenv

baudrate=115200

bootargs=console=ttyS1,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0600 ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256

bootcmd=fsl_mc apply dpl 0x580700000 && cp.b $kernel_start $kernel_load $kernel_size && bootm $kernel_load

bootdelay=10

eth1addr=00:10:F3:81:93:37

eth2addr=00:10:F3:81:93:38

eth3addr=00:10:F3:81:93:39

eth4addr=00:10:F3:81:93:3A

eth5addr=00:10:F3:81:93:3B

eth6addr=00:10:F3:81:93:3C

eth7addr=00:10:F3:81:93:3D

eth8addr=68:05:ca:2b:9e:d3

ethact=DPMAC1@xgmii

ethaddr=00:10:F3:81:93:37

ethprime=DPMAC1@xgmii

fdt_high=0xa0000000

fdtcontroladdr=ffcf91b0

gatewayip=192.168.10.1

hwconfig=fsl_ddr:bank_intlv=auto

initrd_high=0xffffffffffffffff

ipaddr=192.168.10.1

kernel_addr=0x100000

kernel_load=0xa0000000

kernel_size=0x2f00000

kernel_start=0x581100000

loadaddr=0x80100000

mcinitcmd=vdd_override 1050 && fsl_mc start mc 0x580300000 0x580800000

mcmemsize=0x40000000

netmask=255.255.255.0

ramdisk_addr=0x800000

ramdisk_size=0x2000000

scsidevs=0

serverip=192.168.10.99

stderr=serial

stdin=serial

stdout=serial

　

Environment size: 1140/8188 bytes

[ufedor]

Please provide as textual attachment complete U-Boot log

[wenceslas_godar]

Hello,

I added the uboot log (plus “printenv” output) as requested.

I am still unable to configure uboot (and tftp server on the Ubuntu machine) to make the tftp work (“ping” the serverip does not work neither)

At the end, I see this warning message that I cannot explain to myself …

Warning: e1000#0 MAC addresses don't match:

Address in SROM is 68:05:ca:8d:2a:6e

Address in environment is 68:05:ca:2b:9e:d3

Best regards

De : ufedor

Envoyé : jeudi 14 novembre 2019 16:26

À : GODARD, Wenceslas <wenceslas.godard@airbus.com>

Objet : Re: - Re: how to make LS2088 boot from NOR flash?

NXP Community <https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: how to make LS2088 boot from NOR flash?

reply from ufedor<https://community.nxp.com/people/ufedor?et=watches.email.thread> in QorIQ Processing Platforms - View the full discussion<https://community.nxp.com/message/1232645?commentID=1232645&et=watches.email.thread#comment-1232645>

[wenceslas_godar]

U-Boot 2016.092.0+ga06b209 (Mar 30 2017 - 01:15:01 +0800)

SoC:  LS2088AE Rev1.1 (0x87090011)
Clock Configuration:
       CPU0(A72):1800 MHz  CPU1(A72):1800 MHz  CPU2(A72):1800 MHz
       CPU3(A72):1800 MHz  CPU4(A72):1800 MHz  CPU5(A72):1800 MHz
       CPU6(A72):1800 MHz  CPU7(A72):1800 MHz
       Bus:      700  MHz  DDR:      1866.667 MT/s     DP-DDR:   1600 MT/s
Reset Configuration Word (RCW):
       00000000: 483038b8 48480048 00000000 00000000
       00000010: 00000000 00000000 00a00000 00000000
       00000020: 01001180 00002581 00000000 00000000
       00000030: 00000c0b 00000000 00000000 00000000
       00000040: 00000000 00000000 00000000 00000000
       00000050: 00000000 00000000 00000000 00000000
       00000060: 00000000 00000000 00027000 00000000
       00000070: 412a0000 00000000
Model: Freescale Layerscape 2080a RDB Board
Board: LS2088AE Rev1.1-RDB, Board Arch: V1, Board version: F, boot from vBank: 0
FPGA: v1.22
SERDES1 Reference : Clock1 = 156.25MHz Clock2 = 156.25MHz
SERDES2 Reference : Clock1 = 100MHz Clock2 = 100MHz
I2C:   ready
DRAM:  Initializing DDR....using SPD
Detected UDIMM 18ASF1G72AZ-2G3B1
Detected UDIMM 18ASF1G72AZ-2G3B1
DP-DDR:  Detected UDIMM 18ASF1G72AZ-2G3B1
18.5 GiB
DDR    14.5 GiB (DDR4, 64-bit, CL=13, ECC on)
       DDR Controller Interleaving Mode: 256B
       DDR Chip-Select Interleaving Mode: CS0+CS1
DP-DDR 4 GiB (DDR4, 32-bit, CL=11, ECC on)
       DDR Chip-Select Interleaving Mode: CS0+CS1
SEC0: RNG instantiated
SEC Firmware: config@1: no such config
SEC Firmware: error (-2)
SEC Firmware: Failed to load image
PSCI: PSCI does not exist.
Waking secondary cores to start from ffeff000
All (8) cores are up.
Using SERDES1 Protocol: 42 (0x2a)
Using SERDES2 Protocol: 65 (0x41)
Flash: 128 MiB
NAND:  2048 MiB
MMC:   FSL_SDHC: 0
EEPROM: NXID v1
In:    serial
Out:   serial
Err:   serial
Debug Server FW: Bad FIT image format
VID: Core voltage after adjustment is at 1023 mV
SATA link 0 timeout.
AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst
Found 0 device(s).
SCSI:  Net:   VID: Core voltage after adjustment is at 1054 mV
crc32+
fsl-mc: Booting Management Complex ... SUCCESS
fsl-mc: Management Complex booted (version: 10.1.6, boot status: 0x1)
PCIe0: pcie@3400000 disabled
PCIe1: pcie@3500000 disabled
PCIe2: pcie@3600000 Root Complex: x1 gen1
PCIe3: pcie@3700000 Root Complex: no link
e1000: 68:05:ca:8d:2a:6e
       DPMAC1@xgmii [PRIME], DPMAC2@xgmii, DPMAC3@xgmii, DPMAC4@xgmii, DPMAC5@xgmii, DPMAC6@xgmii, DPMAC7@xgmii, DPMAC8@xgmii, e1000#0
Warning: e1000#0 MAC addresses don't match:
Address in SROM is         68:05:ca:8d:2a:6e
Address in environment is  68:05:ca:2b:9e:d3