On Wednesday, 18 June 2014 20:18:47 UTC+2, john3909 wrote: > > What you say is not accurate. The USB100V2 is less than $100 and is plenty > fast enough. >
TI itself points to the fact that you need much patience when using USB100V2. I don't know what size your application has but with a .bin file above 100 kByte there is time to get a cup of coffee until .GEL file is executed and firmware is loaded. Beside of that restarting the code on BBB does not work, so you reload the code quite often. > The TinCan Tools just doesn’t work and there are several users on this > mailing list that have tried and failed. > TinCan Tools I mentioned are the header (that is required for Black) and an adapter to connect with the TI debugger - so just some passive pieces of metal that work fine for me. Don't have any experience with their debuggers. While the USB100V2 can be used for Linux Kernel code (Drivers, Modules, > etc) development, it isn’t really Linux OS aware (CCSV4 did have this > feature, but this was dropped in CCSV5). You can see Linux kernel source > code, set breakpoints, view global and local variables, but you cannot > switch to another kernel process or view many of the kernel data > structures. Debugging Kernel Modules is almost impossible. For real Linux > Kernel code development I recommend using Lauterbach which is Linux Kernel > OS Aware, and takes advantage of the AM335x internal 32k trace buffer, but > it is > $5,000. > > I'm using it for bare metal programming with Starterware only, no Linux involved. There the debugger works quite poor, also with CCS6. Fred > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
