VSOS 3.43 INITNAND on custom board

Discussion about writing software for VS1005 and the VSOS Operating System. Also posts about VS1005-related hardware design and device drivers should be posted here.
Post Reply
Passionate Jaguar
Senior User
Posts: 69
Joined: Sun 2014-05-04 9:17

VSOS 3.43 INITNAND on custom board

Post by Passionate Jaguar » Fri 2017-05-26 10:36

Hello,

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".

UART messages:

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
It seems to want to mount the External SPI Flash, a seemingly different behavior that with our previous VSOS 3.27 setup on the Dev Board v1.8.

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.

Any ideas???
Thanks,
Scott
VS1005 Demo Board v1.8, custom designed VS1005 boards, with VSOS 3.43 - VSIDE v2.42

User avatar
Panu
VLSI Staff
Posts: 2406
Joined: Tue 2010-06-22 13:43

Re: VSOS 3.43 INITNAND on custom board

Post by Panu » Fri 2017-05-26 17:34

Oh, crap. I didn't think anyone used that.

Ok. so, we moved some of the less often used libraries, including NFBADMAP.DL3 etc to the SYS_everything folder from the root proper to save some space. Please copy the NFBADMAP.DL3 to your S:SYS/ and try again.

Sorry about this.

Just to be clear, did your nand flash setup work with some existing kernel/root/driver combination?
- Panu

PS.
Also note that it shows "Driver: K9F4G... 'E'nfbadmap not found' even though [it's mounting it as N, not E]
E'msg' is the VSOS SystemError(msg) output. The error message is encapsulated in E' ' to make it more machine parseable, e.g. when your microcontroller is scanning VSOS UART output and it sees E' then it can make note of the error. Or that's the idea anyways :)
Info: Line In and Line Out, VS1000 User interface, Overlay howto, Latest VSIDE, MCU Howto, Youtube
Panu-Kristian Poiksalo, VLSI Solution Oy

Passionate Jaguar
Senior User
Posts: 69
Joined: Sun 2014-05-04 9:17

Re: VSOS 3.43 INITNAND on custom board

Post by Passionate Jaguar » Fri 2017-05-26 20:59

Hi, Panu,
Oh, crap. I didn't think anyone used that.
Yes, although NAND Flash tends to be a bit psychotic when left to worldly things, with proper early training, it handles RAW stuff well so far with little delay. I was sure intent on this Cypress NAND working with the existing driver. I'm quite sure you were, too!
Please copy the NFBADMAP.DL3 to your S:SYS/ and try again.
Yes, it worked perfectly, thanks.
Just to be clear, did your nand flash setup work with some existing kernel/root/driver combination?
Yes, on VSOS 3.27. Now, so far, everything is working. Still need to remap audio/GPIO pins so I can actually send audio to the NAND Flash on our board and will update you if I find any bugaboos.

Thanks,
Scott
VS1005 Demo Board v1.8, custom designed VS1005 boards, with VSOS 3.43 - VSIDE v2.42

Post Reply

Who is online

Users browsing this forum: No registered users