BOOTME issue

May 24, 2016 at 2:38 PM
Hi David,

I have been working with your BSP for some weeks now and I am currently trying to integrate a driver for the FT5x06 touch.

Now that I have written the driver (according to Microsoft guidelines), I would like to debug it from Platform Builder.

After entering the bootloader menu, here is what I do:

[2] Select Boot Device --> [1] Internal EMAC --> [0] Exit and Continue

Here, I expect the bootloader to start sending BOOTME messages over the Ethernet link but nothing happens. Well, not extactly, here is the output:
INFO:g_bootSlot=1 - g_bootCfg.bootDevLoc.LogicalLoc = 0x4a100000
INFO:Boot device override
LCD 800x480
BOOTLOADER: FileIoInit() calling init.
BOOTLOADER: FileIoInit() calling init.
Init HW: controller RST 1
SDCARD:Reqested speed 1000000, actual speed 1000000
MMCIssueIdentify: SD HC card detected
SDCARD:Reqested speed 25000000, actual speed 24000000
BOOTLOADER: FileIoInit() calling read_sector to get partition table
BOOTLOADER: FileIoInit() calling read_sector to get partition table
0 33 c0 8e d0 bc 0 7c fb 50 7 50 1f fc be 1b 7c 3.....|.P.P....|
10 bf 1b 6 50 57 b9 e5 1 f3 a4 cb bd be 7 b1 4 ...PW...........
20 38 6e 0 7c 9 75 13 83 c5 10 e2 f4 cd 18 8b f5 8n.|.u..........
30 83 c6 10 49 74 19 38 2c 74 f6 a0 b5 7 b4 7 8b ...It.8,t.......
40 f0 ac 3c 0 74 fc bb 7 0 b4 e cd 10 eb f2 88 ..<.t...........
50 4e 10 e8 46 0 73 2a fe 46 10 80 7e 4 b 74 b N..F.s*.F..~..t.
60 80 7e 4 c 74 5 a0 b6 7 75 d2 80 46 2 6 83 .~..t....u..F...
70 46 8 6 83 56 a 0 e8 21 0 73 5 a0 b6 7 eb F...V...!.s.....
80 bc 81 3e fe 7d 55 aa 74 b 80 7e 10 0 74 c8 a0 ..>.}U.t..~..t..
90 b7 7 eb a9 8b fc 1e 57 8b f5 cb bf 5 0 8a 56 .......W.......V
a0 0 b4 8 cd 13 72 23 8a c1 24 3f 98 8a de 8a fc .....r#..$?.....
b0 43 f7 e3 8b d1 86 d6 b1 6 d2 ee 42 f7 e2 39 56 C..........B..9V
c0 a 77 23 72 5 39 46 8 73 1c eb 1a 90 bb 0 7c .w#r.9F.s......|
d0 8b 4e 2 8b 56 0 cd 13 73 51 4f 74 4e 32 e4 8a .N..V...sQOtN2..
e0 56 0 cd 13 eb e4 8a 56 0 60 bb aa 55 b4 41 cd V......V.`..U.A.
f0 13 72 36 81 fb 55 aa 75 30 f6 c1 1 74 2b 61 60 .r6..U.u0...t+a`
100 6a 0 6a 0 ff 76 a ff 76 8 6a 0 68 0 7c 6a j.j..v..v.j.h.|j
110 1 6a 10 b4 42 8b f4 cd 13 61 61 73 e 4f 74 b .j..B....aas.Ot.
120 32 e4 8a 56 0 cd 13 eb d6 61 f9 c3 49 6e 76 61 2..V.....a..Inva
130 6c 69 64 20 70 61 72 74 69 74 69 6f 6e 20 74 61 lid partition ta
140 62 6c 65 0 45 72 72 6f 72 20 6c 6f 61 64 69 6e ble.Error loadin
150 67 20 6f 70 65 72 61 74 69 6e 67 20 73 79 73 74 g operating syst
160 65 6d 0 4d 69 73 73 69 6e 67 20 6f 70 65 72 61 em.Missing opera
170 74 69 6e 67 20 73 79 73 74 65 6d 0 0 0 0 0 ting system.....
180 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................
190 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................
1a0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................
1b0 0 0 0 0 0 0 0 0 d 6 78 22 0 0 80 1 ..........x"....
1c0 1 0 c fe ff 9a 3f 0 0 0 c1 77 dd 1 0 0 ......?....w....
1d0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................
1e0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................
1f0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 aa ..............U.
BOOTLOADER: PartitionTable[0] Flag:0x80, Type:0xc, Start:0x3F, Size:0x1DD77C1
BOOTLOADER: PartitionTable[1] Flag:0x0, Type:0x0, Start:0x0, Size:0x0
BOOTLOADER: PartitionTable[2] Flag:0x0, Type:0x0, Start:0x0, Size:0x0
BOOTLOADER: PartitionTable[3] Flag:0x0, Type:0x0, Start:0x0, Size:0x0
BOOTLOADER: trying partition 0
BOOTLOADER: Active partition type is FAT32
BOOTLOADER: FileIoInit() calling read_sector to read MBR for active partition
BOOTLOADER: FileIoInit() copying BPB into FilesysInfo structure.
BOOTLOADER: boot sector BPB for valid partition
BOOTLOADER: sector size:     200
BOOTLOADER: sec/cluster:     10
BOOTLOADER: rsvd sectors:    8C2
BOOTLOADER: # FATs:          2
BOOTLOADER: media descipt:   F8
BOOTLOADER: sec/track        3F
BOOTLOADER: # heads          FF
BOOTLOADER: root dir str cl: 2
BOOTLOADER: b# total sectors:1DD77C1
BOOTLOADER: b# sec/fat:      3B9F
BOOTLOADER: b# hidden sec:   1
BOOTLOADER: FileIoInit() initializing data structures.
OEMPreDownload: Ethernet
+Cpsw3gInit(0x4a100000, 0x00000001, 0x8feffedc) v0.3
g_cpsw3g_reg_base = 0xb0500000
And then nothing. Platform Builder waits for BOOTME messages on my computer.

The images have been built in DEBUG with KITL option configured to Yes.

Do you have any clue ?
When I read the code, I see a lot of ++FIXME parts in cpsw3g code. Does it mean that this part was never tested ?
May 31, 2016 at 1:52 PM
My bad, the issue was incoming from an invalid setting in pad config (PROFILE_1 was not enabled).

Now everything works fine and I can debug my drivers.