> SB libraries assume USB_BASE_ADDRESS as the beginning of USB RAM Where is USB RAM? I would like to find a way for USB RAM to be reserved so JALv2 knows how much ram is being used when compiling a program with current device files.
>From the post you showed, is this correct? const USB_BASE_ADDRESS = 0x0200 or const USB_BASE_ADDRESS = 0x0400 How big is USB RAM? When reading over the USB generic sample, I see a direct read from POSTINC1. This should not get called directly, it should be part of a small buffer'get function: function usb_buffer'get() return byte is pragma inline return POSTINC1 end function I don't understand how the address POSTINC1 gets set, or how it knows where to read memory. I also noticed there are not enough comments in USB files. Maybe some should be added to make it more understandable? Seb, if you have a chance to add some comments why you look for a fix, please do! Albert did not use PRINT library for debugging, this makes the current implementation of debugging difficult. Again, not enough comments. When I enable debugging, I mostly see a bunch of junk hex that I have no clue about. I am still looking into USB MSD (mass storage), but I have trouble sending data back to the PC. Troubleshooting methods are limited, and so is my knowledge on USB. Albert did make a great USB library, it seems that there are a few small improvements that could be made. Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
