Search found 11 matches

by madboy-software
Mon 2019-06-17 11:23
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Hey Panu, I have sent the code over to support@vlsi.fi.
by madboy-software
Mon 2019-06-17 8:44
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Yes, I figured that out by myself. Does that output look good, is it fragmented? Should I do something to combat fragmentation? Some more possible options we have been thinking about: Is it possible to use the VLSI VS23S010 or VS23S040 for additional (I)RAM? Would you folks at VLSI like to take a lo...
by madboy-software
Mon 2019-06-17 7:29
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Hello again. I copied over a backup of a version that has been confirmed working with lots of memory available. Now, it's warning me that there is only about 460W free on IMEM. This shouldn't happen, right? The previous test of this software was with the same VSOS version, same memory (Internal SPI)...
by madboy-software
Fri 2019-06-14 13:13
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Hello Henrik and Panu, I ran your updated version of the "Rec" command and I got it to work with keyboard input. Here is the output for different input combinations: Pressing Alt Gr and the "^ ¨ ~" key (next to Å key) ONCE and typing 0209 <enter>, produces "~0209" in notepad and ~209 !cmdUnknown In ...
by madboy-software
Thu 2019-06-13 18:11
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

I will try some of these things tomorrow. However, the -d option was only for debugging and will not be used in the future. As I said, you don't have to worry about the Rec command VU meter, since it won't be used in the future. We have actually tried changing the output/input buffer sample amount a...
by madboy-software
Thu 2019-06-13 11:18
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Update:

I accidentally bricked the internal flash of the dev board by calling AuInput with a wrong -p pointer. I got it restored, but now I'm running out of memory on BOOT!!! What's going on? Was some sort memory map file corrupted?
by madboy-software
Thu 2019-06-13 7:09
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Thank you for the answer. Regarding the implementation by UART console, the loaded "MyProg" would not be required that way. I don't think memory would be an issue if we would go that route. We have still made good progress on developing our own software and I think we will use that. UART console see...
by madboy-software
Wed 2019-06-12 12:09
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

I am happy tell you that we have now advanced quite nicely on the project, partially thanks to your help. But the issue of running out of memory still persists. Here is a list of currently loaded libraries, from the UART console: 11 libs loaded: 11 libs loaded: 3300: RUN 38i + 0x + 0y 3326: AUOSPDA ...
by madboy-software
Wed 2019-06-05 14:32
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

An update on this issue. We have just realized that it is actually unnecessary to write any input changing code for the VLSI chip if we can just boot it in UART console mode and control it from the front panel using that. A couple of problems arise with this approach: #1: Is it possible to change th...
by madboy-software
Wed 2019-06-05 8:31
Forum: VS1005 and VSOS Software
Topic: Memory management issues
Replies: 19
Views: 214

Re: Memory management issues

Thanks for the reply. We changed from the external memory of the chip to the internal memory and that made it somehow not run completely out of memory. The "only ****w free!" warnings are still appearing, but we don't know if the previous programmer had the same issue. We are now working on getting ...