15 May 2021, 01:22 | #281 |
Registered User
Join Date: Jul 2017
Location: Oxford
Posts: 104
|
|
15 May 2021, 03:11 | #282 | |
Registered User
Join Date: Dec 2017
Location: Austin, TX
Age: 41
Posts: 405
|
Quote:
Would love to see cycle/DMA profiling to help tune my (not very optimal) attempts at demo effects. |
|
15 May 2021, 20:31 | #283 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
Before that, I'm reworking the binaries management with a download inside the extension and a generation of the example workspace. That will help at the startup for new users. Meanwhile you can try this : https://marketplace.visualstudio.com...tes.68kcounter http://eab.abime.net/showthread.php?t=106546&highlight=vscode+extension from @gigabates. |
|
15 May 2021, 21:15 | #284 | |
Registered User
Join Date: Jul 2017
Location: Oxford
Posts: 104
|
Quote:
I just tested in RUN mode (putting an error in case the library is successfully opened), and it works... it just fails in debug mode. Weird. |
|
15 May 2021, 22:43 | #285 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
The Run and bug modes are different.
I've tried to explain it here: https://github.com/prb28/vscode-amig...ing-to-the-ide For this reason you must absolute paths, and get some differences with the normal CLI launch. It's different in the winuae integration, you can try to use it with wine. Some did it with success. |
12 July 2021, 17:33 | #286 |
Registered User
Join Date: Jan 2008
Location: somewhere
Posts: 45
|
Hi,
Do you think it's possible to debug custom rom code with your extension ? I mean, I want to debug a custom ROM made from scratch, not the official roms. |
13 July 2021, 18:22 | #287 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
You can debug a program launched by some kind of cli start. This program must have line debug information to have a source debugging. You can try to have a dummy program and add some breakpoints in the address you want (in your rom), but even with it you may not be able to access all the memory in the emulator. |
|
16 July 2021, 16:30 | #288 |
Registered User
Join Date: Jul 2021
Location: Sandy, UT
Age: 55
Posts: 230
|
Just came in to say that this is great! Easiest path (for me) getting back into Amiga asm coding Thank you so much.
|
17 July 2021, 02:42 | #289 |
Phone Homer
Join Date: Jun 2006
Location: 5150
Posts: 5,773
|
Someone just quickly explain to a lamer like myself how these addons for Visual Studio/.net work because obviously you can't compile them and run them etc
|
17 July 2021, 10:09 | #290 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
|
17 July 2021, 10:17 | #291 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
I'm working on a simpler way to get a working example with "one" click. Slowly in progress.... For now, You have to :
|
|
20 July 2021, 14:03 | #292 |
Registered User
Join Date: Jun 2020
Location: Brno
Posts: 90
|
Hello!
Does Amiga Assembly extension support standard WinUAE shift-F12 debugging? I just recently noticed that whenever I try to open that debugger, the execution goes into VSCode and addon stops the program. Is it because the Amiga Assembly uses its own custom build of WinUAE and that debugging feature is disabled? Or is there any other way how to open the debug console in WinUAE? |
20 July 2021, 15:46 | #293 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
This integration was done by bartman and I'm not enough aware of the winuae internals to give you a better answer without digging in the source... What is the option missing in vscode that makes you want to access to the internal debugger ? |
|
21 July 2021, 20:15 | #294 | |
Registered User
Join Date: Jun 2020
Location: Brno
Posts: 90
|
Quote:
It is sometimes handy. Not a big deal though. I can always run it within a standard WinUAE. Last edited by defor; 21 July 2021 at 20:59. |
|
15 April 2022, 19:54 | #295 |
Registered User
Join Date: Jun 2020
Location: Brno
Posts: 90
|
Hi! I've update VSCode to version 1.66.2 and installed Amiga Assembly v1.2.0.
Now when I start VSCode, it tries to download some needed files (something about it you wrote on your project's wiki, I think). Unfortunately after a few seconds, it displays the error message "The "streams" argument must be specified". Is there some problem with the latest VSCode? Which version do you recommend for Amiga Assembly 1.2.0? Also, does the latest version of the addon come with more recent version of WinUAE? Previously I was using version 0.21.3 and the recommended workspace (vscode-amiga-wks-example-windows_x64) comes with quite old WinUAE 4.4.0. Thank you. |
16 April 2022, 00:27 | #296 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
I’ve proposed a pull request to fix it, but it seems abandoned. You can download a fixed version attached to the GitHub issue. I’ll certainly get rid of it in the next weeks if there is no movement from the owner of this download extension. I’ve updated the winuae in the last 2 moths to winuae 4.9.0. |
|
16 April 2022, 17:37 | #297 | |
Registered User
Join Date: Jun 2020
Location: Brno
Posts: 90
|
Quote:
|
|
16 April 2022, 19:29 | #298 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
I try to keep it simple, but sometimes some breaking changes are needed. |
|
17 April 2022, 12:40 | #299 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Fixed in pre-release v 1.3.2 and the next release v1.4.
|
30 April 2022, 20:06 | #300 |
Registered User
Join Date: Apr 2019
Location: UK
Posts: 172
|
Environment variables in vasm args
Is it possible to use environment variables in vasm args? I'm trying to remove all relative paths to make my sample/demo project folders movable on disk and build from anywhere.
I have an environment variable set called "INCLUDE" pointing to my include directory. I also have "NDK" env var and others I would like to use. I've set up an "echo" task above the "amigaassembly" task: Code:
{ "version": "2.0.0", "tasks": [ { "label": "echo", "type": "shell", "command": "echo workspaceFolder=${workspaceFolder} env:INCLUDE=${env:INCLUDE}" }, { "type": "amigaassembly", "vasm": { "enabled": true, "command": "${config:amiga-assembly.binDir}/vasmm68k_mot", "args": [ "-m68000", "-Fhunk", "-I../../../../include", "-I../../../../../toolchain/NDK/Include_I", "-I${env:INCLUDE}", "-linedebug" ] }, Code:
workspaceFolder=C:\GitHub\Hop\amiga-assembly\target\samples\hardware\copper\copperbars env:INCLUDE=C:\GitHub\Hop\amiga-assembly\target\include Code:
Compiling_________________________________________ building c:\amiga-assembly\target\samples\hardware\copper\copperbars\build\copperbars.o c:\Users\Hop\AppData\Roaming\Code\User\globalStorage\prb28.amiga-assembly\downloads\vscode-amiga-assembly-binaries-@-1.3.3\vscode-amiga-assembly-binaries-windows_x64/vasmm68k_mot -m68000 -Fhunk -I../../../../include -I../../../../../toolchain/NDK/Include_I -I${env:INCLUDE} <snip> Is there a way to make this work? Thanks |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
assembly code to test for assign (2.0+) | jotd | Coders. System | 2 | 27 December 2017 23:16 |
very basic C/ASM/Visual Studio hand holding | Sephnroth | Coders. C/C++ | 2 | 08 March 2016 20:15 |
Amiga Audio/Visual | KhneFr | request.Other | 6 | 03 January 2015 10:25 |
Profiling WinUAE with Visual Studio 2013 | mark_k | support.WinUAE | 3 | 14 January 2014 20:26 |
amiga visual editor | thinlega | request.Apps | 1 | 22 January 2003 15:48 |
|
|