bug in VSIDE Solution VS1063 player/recorder2016 version

Designing hardware that use VLSI Solution's devices as the system controller for the entire design.
maris_n_s
User
Posts: 4
Joined: Thu 2017-01-26 13:36

bug in VSIDE Solution VS1063 player/recorder2016 version

Postby maris_n_s » Wed 2017-03-22 14:37

Good day
I've studied
vs1063-standalone-vside-20161026 solution, then
After compiling solution VSIDE says that is no
asm-clocksdi.s file , and after I've copied it
says that is no 1053.h header file.
I copied this two missed from other resourses
h1053 folder from vs1053-standalone-vside-130
and
asm-clocksdi.s from vs1063-standalone-recorder-120120

Compiler has build solution, but I've get error
could not load executable!
I tested older version of solution, it is loadable to VS1063 Prototiping board V2.1
Could you correct this two bugs, or send my right missing files?
Could you show better (simplier,shorter) example about playing/recording (one that is in First step with VS1053 is to simply).
This is ok if all not needed optional things will be removed.

User avatar
pasi
VLSI Staff
Posts: 1331
Joined: Thu 2010-07-15 16:04

Re: bug in VSIDE Solution VS1063 player/recorder2016 version

Postby pasi » Wed 2017-03-22 16:47

Hi, it seems that asm-clocksdi.s is in the vs1063-standalone-lib.project file while the file itself has been eliminated. Thanks for the report.

You can make an empty asm-clocksdi.s to get around this. (Or load vs1063-standalone-lib.project into an editor and remove references to "asm-clocksdi.s" from it.)

The solution will then compile properly, creating both the standalone player and the standalone recorder.

I'm not sure what the issue with loading is. I don't think I loaded the executable for a file. You should be able to use the VSIDE Prommer/Flasher utility to program the active project into the EEPROM.

Also note that the recorder will only work if programmed into the boot EEPROM, because it watchdog-resets vs1063a at least once for each recording.

(Edit: I also fixed the offending file in the package.)
Visit https://www.facebook.com/VLSISolution VLSI Solution on Facebook

User avatar
pasi
VLSI Staff
Posts: 1331
Joined: Thu 2010-07-15 16:04

Re: bug in VSIDE Solution VS1063 player/recorder2016 version

Postby pasi » Fri 2017-03-24 12:51

For programming: You first need to prevent boot from SPI by removing the "BOOT SPI" JP10, then power up the card, then run the prommer utility. You can then re-insert JP10.
Visit https://www.facebook.com/VLSISolution VLSI Solution on Facebook

maris_n_s
User
Posts: 4
Joined: Thu 2017-01-26 13:36

Re: bug in VSIDE Solution VS1063 player/recorder2016 version

Postby maris_n_s » Wed 2017-04-12 17:40

Thank, for answer, it works!!
But it is another bug here, if I put #define USE_DEBUG: option
Firsts declaration of puthex function in standalone.h is faulty, it should correct to void puthex(u_int16 d);
But I still have unsolved errors:
ERROR: vslink: could not allocate 0:memory for section FatIterateOverFreeSectorsLimited (262 words)
ERROR: vslink: relocation failed

Could you help me solve it?

User avatar
pasi
VLSI Staff
Posts: 1331
Joined: Thu 2010-07-15 16:04

Re: bug in VSIDE Solution VS1063 player/recorder2016 version

Postby pasi » Thu 2017-04-13 12:23

Memory is in short supply, especially the instruction memory.

If you enable debug, you need to disable something else. Unfortunately there are no good rules on which things fit in together.
Visit https://www.facebook.com/VLSISolution VLSI Solution on Facebook


Return to “Stand-Alone Applications”

Who is online

Users browsing this forum: No registered users