I'm only talking about the Hardware firmware now. I can't even try with my Android App since my hardware doesn't even boot and therefore doesn't establish the bluetooth or USB connection. As I said I am using the IOIO V5.x as plain as I can. I will try again without changing anything at all, but chances are there might be something that I need to modify that I don't see.
As you say it is hard to find the problem since I have custom hardware and therefore need to modify the Firmware a bit. Le vendredi 27 mars 2015 08:43:31 UTC+1, Ytai a écrit : > > There are too many things that can go wrong in your setup: custom IOIO, > custom forward with changes that are very likely to break stuff and a fair > amount of complexity in your app. > I recommend that you start by eliminating some possible causes (e.g. test > your app on a stock IOIO with stock firmware or run a rigorous test on your > custom hardware/firmware, such as the IOIO torture test. > Otherwise you'd be wasting our time. > On Mar 26, 2015 9:30 AM, "Vincent Nadon" <[email protected] > <javascript:>> wrote: > >> >> - So I tried the V5.X firmware, as plain vanilla as I could. I have >> put some call for LEDs to light up during boot process and I connected an >> Arduino USB2Serial to monitor the logging. >> >> As it is, no LEDs light up and I don't see anything in the logging, >> no "***** Hello from app-layer! *******", nothing... Even my bluetooth >> dongle doesn't seem to light up anymore. >> >> >> >> I did configure everything to suit my hardware (PIC24FJ256DA206) and then >> also changed the pins for my UART according to what I had working in my >> previous firmware, and changed few pins for LEDs. I also configured the >> ENABLE_LOGGING in the pic30-gcc preprocessor macros. >> >> >> >> >> libusb, libconn, libbtstack, libadb, Bootloader and AppLayerV1 all build >> without errors. >> >> >> >> - I have also another question, in my previous firmware version I had >> to set Memory_Model to Large Data, Large code and small scalar. I also >> had >> to modify QUEUE_SIZE in protocol.c to 128 (instead of 8192) to fit the >> code >> to program my DSPs in the pic memory. Would you have a better suggestion >> to >> provide the memory space for DSP code? (I use the pic to program my DSPs >> at >> bootup) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ioio-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/ioio-users. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
