Using Cypress S34ML04G1 NAND Flash on our custom board, INITNAND.BAT and INITSPI.BAT (to external Flash) ran perfectly. External Flash formated and VSOS 3.43 flashed perfectly. We got the same Command Prompt output you noted here: viewtopic.php?f=13&t=1553&p=7298#p7298
Loaded newest SYS folder and our app .ap3. Everything worked correctly except getting the NAND Flash to mount to USB using S4 on our test bed (works the same as Dev Board 1.8 to keep OS mods manageable).
How do we get it to mount for formating?? Also, it seems to not be handling the bad blocks correctly as shown in your UART outputs in the above mention link. Unlike in your link above, multiple Reset presses did not change how NAND Flash organized itself, even after "cleaning".
Code: Select all
Hello. VSOS 3.43 build May 24 2017 02:13:23 VLSI Solution Oy 2012-2017 - www.vlsi.fi Starting the kernel.. Starting Devices... External SPI Flash Installed system devices: S: SPI Flash 0114, handled by FAT. Load drivers, config 4... Driver: K9F4G... E'nfbadmap not found' Cleaning Nand.. No Nand or FS. N: Nand Flash, handled by None 1 driver(s) loaded. VSOS running with 5 tasks: Task I/O Stack:0010-020f (512w), free:178 Task Int Stack:0210-024f ( 64w), free:28 Task Net Stack:0250-0251 ( 2w), free:1 Task UI Stack:0252-0253 ( 2w), free:1 Task DECOD Stack:0254-03cf (380w), free:379 Interrupts: INT0_DAC:2->37765 INT13_RX:1->32923 INT15_TI1:1->525 INT16_TI2:1->10221 Load S:INIT.AP3... S:INIT.AP3 not found. Nothing to do.USB publishing disk: SPI Flash 0114. Size 1.9 MB. SCSI START BRST BRST BRST
Also note that it shows "Driver: K9F4G... E' even though it actually does finally attempt to mound as drive "N" as defined in CONFIG.TXT.
So what did I miss between VSOS 3.27 and 3.43 regarding getting a new board up and running. Only problem so far seems to be the NAND Flash. With no buttons pressed, Our app runs as expected except for accessing the yet unprepared NAND Flash.