GPU computing Stay up to date in OpenCL, DirectCompute, CUDA, CAL and OpenGL information

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Monday, 7 December 2009

Nvidia Nexus beta1 GPU debugger shipped!

Posted on 16:04 by Unknown
Hi,
I just get access to Nexus beta 1 dated 2-12-2009!


Below is readme:
NVIDIA Code-name Nexus 1.0 Beta 1 Notes 12.02.09
Requirements
To use the Nexus Debugger for hardware debugging CUDA C or HLSL code, you will need to use two machines, a host (with Visual Studio) and a target with a supported GPU (for running your application) in order to debug remotely over a normal TCP/IP network connection.
To use only the Nexus Analyzer or Graphics Inspector, you may either use a single machine with a single supported GPU installed, or use it remotely as described for the debugger. If using a single machine, your ‘host’ and ‘target’ machine are the same physical machine. More information is available in the Nexus Knowledge Base accessible by signing in through www.nvidia.com/nexus.
Host machine:
 Operating System: Windows 7 or Vista SP1, 32 or 64-bit.
 GPU: Any DX10-capable GPU
 Visual Studio: Visual Studio 2008 with Service Pack 1 (Standard edition or above)
 Other Software: .NET framework 3.5 with Service Pack 1
 Optional: CUDA SDK, DirectX SDK (Mar 2009 or Aug 2009)
Target machine:
 Operating System: Windows 7 or Vista SP1, 32 or 64-bit.
 GPU: An NVIDIA G92 or GT200 based GPU (GeForce, Quadro, or Tesla)
 Other Software: .NET framework 3.5 with Service Pack 1
 Optional: CUDA SDK, DirectX SDK (Mar 2009 or Aug 2009)
Download and Installation steps
1. Sign-in to the NVIDIA Nexus Support site. You can get here by signing in from www.nvidia.com/nexus.
2. Go to the Downloads page.
3. Download a host installer. You will install this installer on the machine that has Visual Studio on it.
o For 32-bit: NVIDIA_Nexus_Host_Win32_Beta1_12_01_2009
o For 64-bit: NVIDIA_Nexus_Host_Win64_Beta1_12_01_2009
4. Download a monitor installer. The monitor is the debug ‘server’ you will connect to, either on another machine or on your existing machine.
o For 32-bit Monitor: NVIDIA_Nexus_Monitor_Win32_Beta1_12_01_2009
o For 64-bit Monitor: NVIDIA_Nexus_Monitor_Win64_Beta1_12_01_2009
5. Download the display driver required by Nexus.
a. 195.62 driver (32-bit): http://www.nvidia.com/object/win7_winvista_32bit_195.62_whql.html
b. 195.62 driver (64-bit): http://www.nvidia.com/object/win7_winvista_64bit_195.62_whql.html
6. Install the driver on the ‘target’ machine (that has a GPU with a G92 or GT200 chip) but do not reboot.
7. Install the Nexus Monitor installer on the same ‘target’ machine in Step 4 (that has the G92 or GT200 GPU in it).
8. Install the Nexus Host on the 'host' machine, where Visual Studio 2008 SP1 is installed.
9. Read the release notes by choosing Start | All Programs | NVIDIA Nexus 1.0 | Release Notes
10. Open the User Guide by choosing Start | All Programs | NVIDIA Nexus 1.0 | User Guide and follow all the steps under the “Walkthroughs” section. This is important as it will validate that you are able to debug and analyze with the samples provided.
If you would like to use your existing project with Nexus, please read “Migration from An Existing Project” in the User Guide.
Notes and Known Issues
- Samples: Nexus ships with samples located (by default) in C:\ProgramData\NVIDIA Nexus 1.0.
- Documentation: Nexus includes a User Guide located on your machine (after installation) at Start | All Programs | NVIDIA Nexus 1.0 | User Guide.
- Release Notes: Choose Start | All Programs | NVIDIA Nexus 1.0 | Release Notes to view the full release notes.
- Graphics shader debugging is only supported when the ‘host’ machine is physically a separate machine than the ‘target’ machine. Attempting to do shader debugging on the same machine as the ‘host’ machine will hang your system.
- Note: Hardware source debugging (either CUDA kernels or HLSL shaders) is only supported when your ‘host’ machine is physically separate machine than your target machine and they remotely communicate over TCP/IP. Information on experimental single-machine Debugger support (for machines with 2 GPUs) for CUDA C debugging only is available in the Nexus Knowledge Base (sign-in through www.nvidia.com/nexus)
- Note: If using Vista, you can check if you have SP1 installed by opening the Control Panel, clicking on the System icon, and looking for the words “Service Pack 1” in the “Windows edition” section.
- Note: Installer: Some commands are executed that bring up the command prompt during installation.
- Known issue (Stability): Analysis: Starting an Analysis session while stopped at a breakpoint causes the system to crash.
- Known issue (Stability): Under some circumstances, using Stop Debugging (Shift + F5) when halted at a breakpoint in a CUDA C kernel will cause your target machine to hang. The workaround is to remove all breakpoints, and hit Continue (F5) before stopping your debug session.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Porting CUDA to OpenCL!
    Well so you want to port CUDA code to OpenCL: you are in AMD GPU competition of porting Cuda codes to opencl (see previous post) or you are ...
  • Megapost!
    Today fools{ *GTX 485 is 512 cores 3gbytes gddr5 and 850/1750 shaders.. *ati 5990 has 4 gpus in board.. *bulldozer benchmarks }end fools.. A...
  • About ATI and Nvidia drivers (OCL included)!
    Hi I have been investigating AMD and Nvidia drivers.. for 10.3 there are 3d hooks support for 120hz monitors but is d3d9 d3d10 or d3d11 enab...
  • things found in CUDA forums
    Also some CUDA news: Mandelbulb stereo angalyph -> have to port to 3D Vision http://forums.nvidia.com/index.php?showtopic=150985&st=2...
  • opencl/opengl linux interop! seen in opencl cuda 3.0 sdk samples
    Following my OpenCL/OpenGL Window interop work: now has come to Linux  for Nvidia GPU computing registered developers via 195.17 driver! Als...
  • State of the blog..
    Sorry for the delay guys of posting code of Apple OpenCL demos port.. the blog has been with no updated for more than 2 weeks in this rapid ...
  • Optix and OpenCL SDKs with Visual Studio 2010
    Optix 1.0 ========= install cg download Cmake 2.80 cmake says error dumpbin not found and it is cuda doesn't work with vc2010 so copy pt...
  • CUDA 3.0 forums stuff!
    1.Getting CUBIN instead of ELF If you need the older text format, you can disable ELF cubins in nvcc.profile by changing "CUBINS_ARE_EL...
  • News from the web!
    Some things learned in AMD forums: 1.Why 3xxx no OpenCL: Compute shader mode is a hardware feature that did not exist in the HD38XX line of ...
  • Shaders: measuring perf, source translation and parsing different languages!
    Hi, I hope to be pretty exhaustive of options for parsing and translating between graphics and compute shaders ( some open source) For DX sh...

Blog Archive

  • ►  2013 (5)
    • ►  September (1)
    • ►  March (3)
    • ►  February (1)
  • ►  2012 (1)
    • ►  December (1)
  • ►  2010 (46)
    • ►  July (4)
    • ►  May (1)
    • ►  April (3)
    • ►  March (9)
    • ►  February (15)
    • ►  January (14)
  • ▼  2009 (125)
    • ▼  December (51)
      • GPU computing on AMD.. an history perspective!
      • Catalyst 9.12: hotfix (III)
      • Catalyst 9.12 Linux and Windows links and release ...
      • Source code of DirectCompute bechmark(OpenCL and D...
      • Catalyst 9.12 adds OpenGL 3.2 support (and more..)!
      • 16/12 news!
      • Catalyst 9.12 released
      • PS3 OpenCL work and AMD OpenCL ICD
      • Christmas Wish list (I): Monitors
      • 3d Stereoscopic players!
      • Today news!
      • What will I do if I have 3D Vision OpenGL QB
      • GLEW,GLUT,Freeglut, MesaGLUT and more
      • Nvidia 195 new drivers and Flash player beta 2!
      • Running ATI GPUs in Sisoft Sandra 2010!
      • Memcheck GPUs!
      • Emulate 3D kernel launch grid
      • things found in CUDA forums
      • Siggraph 2009 (Asia too..)!
      • Architecture ideas for future GPUs!
      • Dificulties in coding, achieving high perf an meas...
      • Learned from HPG09 stuff!
      • Nvidia driver 187.98 add new files!
      • What I would want to know and get from vendors par...
      • What I would want to know and get from vendors par...
      • Some news II (post #100!)
      • What I would want to know and get from vendors par...
      • physics on GPU: source code!
      • OpenCL with MingW! (and more)
      • Some news!
      • String matching on GPUs!
      • Lots of OpenCL soft coming!
      • 10 Raytracing GPU demos! (more or less)
      • New Nvidia tools and crossvendor GPU instrumentati...
      • About Catalyst 9.12 and 10.1!
      • CUDA 3.0 forums stuff!
      • Upcoming GPU tutorials!
      • News from the web! (9 December)
      • Compiling the CUDA compiler!
      • Understanding Nvidia GT200 GPU and CUDA implementa...
      • Open Source GPU Computing benchmarks
      • CUDA TopCoder contest stuff (with source code of t...
      • CUDPP news!
      • DirectCompute stuff!
      • Nvidia GPU computing news!
      • GPU Computing calendar for December 09 and January...
      • Nexus FAQ!
      • Nvidia Nexus beta1 GPU debugger shipped!
      • GPU virtualization (and what to expect in VMs)!
      • AMD OpenCL news! (almost all..)
      • News posted 2/12/2009! (megacompilation)
    • ►  November (53)
    • ►  October (21)
Powered by Blogger.

About Me

Unknown
View my complete profile