VS1005 - MP3 Player

[Panu]

Hi!

First step: see that the "Autodetect" button in Solution Properties -> Debugging works and detects the IC.

-Panu

[patrickino]

Hi Panu,

Yes, the chip was detected.

I can see this information:
Chip Type: VS1005
Serial Port: COM11
Initial Speed: 115200

Thanks
Patrick

[Panu]

Try the programming right after autodetection. It should work. Do you see the "Stdin/Stdout" window? Maybe it has closed for some reason.

The programmer window does not close by itself. The last prompt in the stdout will ask you to close the window.

Please see my "educational videos" thread viewtopic.php?f=13&t=1273 . In the first thread I download and install the kernel. See if your flow is similar or different.

-Panu

[patrickino]

Hi Panu,

I'va added a capture of my screen.
So, as you can see I don't have any kind of text line on stdin/stdout.

Capture.PNG (68.09 KiB) Viewed 4758 times

Thanks
Patrick

[Panu]

That is really weird.

Anything in the log window?

Try fooling around with powers and resets.

It's the only VS1005 in the system, right? And you're using a recent VSIDE?

You're using your own board, right? Do you have GPIO0.7 pull-up (to select 3 volt IOVDD). What about TEST pin? Can you measure voltages (IOVDD, CVDD, AVDD) after power-up?

-Panu

[patrickino]

Hi Panu,

I've only this sentence in the log windows under "Debugging Output": Loading 'C:/Program Files/VSIDE/bin/extflash1005g.bin'...

Yes, I've only VS1005 in the system and I use the VSIDE 2.28.

You're using your own board, right?

Yes.

Do you have GPIO0.7 pull-up (to select 3 volt IOVDD).

Yes, pin 16 of VS1005 have a pull-up with a 100k resistor.

What about TEST pin?

Test pin is connected to the ground.

Can you measure voltages (IOVDD, CVDD, AVDD) after power-up?

Yes, of course: IOVDD (3.21V), CCVD (1.78V) ans AVDD (3.78V).

Patrick

[Panu]

Weird, weird, absolutely weird. As a desperate step, can you reinstall your VSIDE to C:\VSIDE folder. And change the USB port of the serial cable.

Well, with new boards it can always be a bit tricky to get them to run the first time. The thing which is so weird here is that I've never seen a board to first successfully autodetect and then fail the programming right after. Can you check if you can run a "VS1005 Hello, World" application directly by pushing the "Play" button on the VSIDE.

One step which is somewhat helpful and sometimes necessary is to install a "boot helper" image into the internal flash. It can be done by instantiating any VS1005 solution such as the kernel and modifying the eeprom_i.map file so that you remove the line "4096 eeprom.img". Then, when the VS1005 internal flash prommer is run, only the rescue/boot helper image is programmed and nothing else.

If you prom the kernel or other application to the internal flash, you must be careful: for security reasons, the internal memory boot can ONLY be prevented by setting the ERASE INTERNAL FLASH gpio pin state at bootup, which may or may not be possible in your board. It means that if you prom a bonk image to the internal flash and cannot set those gpio pins, then your board can be in a state where it's impossible to connect to it or reflash it. As the board autodetects, this has not happened to you.

Next we will synthesize the command line to run the prommer from the CMD.EXE command prompt by invoking VS3EMU directly, which can give us more information about what is happening.

-Panu

[Panu]

I guess it's time to do some serious bughunting. Open your kernel solution, right-click the "main.c" editor tab title to get a pop-up menu to open a command prompt to your project folder.

Then give the following command:

c:\vside\bin\vs3emu -chip vs1002b -monaddr 0x8000 -m mem_desc_debug_all.mem -s 115200 -p 11

You should see something similar to the screenshot below:

vs3emu.jpg (83.61 KiB) Viewed 4736 times

If you get so far, then the next step is to run the prommer. That is done with another VS3EMU invocation:

c:\vside\bin\vs3emu -chip vs1002b -monaddr 0x8000 -m mem_desc_debug_all.mem -s 115200 -p 11 -l c:\vside\bin\extflash1005g.bin

And when you get the prompt, give the commands:

g 0x50
e

The prommer will then run. It will open eeprom.img file on your PC and push it to the board.

prom.jpg (298.85 KiB) Viewed 4736 times

-Panu

[patrickino]

Hi Panu,

First of all thanks to much for your support.
So, I have done the tests that you ask me to do; this is the result:

Weird, weird, absolutely weird. As a desperate step, can you reinstall your VSIDE to C:\VSIDE folder. And change the USB port of the serial cable.

No changes!

Well, with new boards it can always be a bit tricky to get them to run the first time. The thing which is so weird here is that I've never seen a board to first successfully autodetect and then fail the programming right after. Can you check if you can run a "VS1005 Hello, World" application directly by pushing the "Play" button on the VSIDE.

The VSIDE print this error string

Capture.PNG (6.04 KiB) Viewed 4727 times

c:\vside\bin\vs3emu -chip vs1002b -monaddr 0x8000 -m mem_desc_debug_all.mem -s 115200 -p 11

Result of this command is the same as you have posted

c:\vside\bin\vs3emu -chip vs1002b -monaddr 0x8000 -m mem_desc_debug_all.mem -s 115200 -p 11 -l c:\vside\bin\extflash1005g.bin

Command result is as you can see

Capture3.PNG (48.95 KiB) Viewed 4727 times

Thanks
Patrick

[patrickino]

Hi Panu,

Any idea?

Thanks
Patrick