kuykens

Thorsten, Got it working at last. I had an additional space in the tool chain folder. After fixing that I still needed to do an addiotnal export of the SVN tree to roll back modifications I did to the make environment. Then, it worked.

Well this snippet was of a file that grew to 700k (!) in a few seconds. I was unable to upload it to the topic. Almost all files create the same problem in the logging. Indeed no modifications in the SVN download. The make file test also succeeded, so no conflict in make tooling. The computer also is a relatively clean system. I had delayed my endeavors to solve this myself until I got message from you. Guess I have to pick it up again and see whether this is solvable. Such a pity.

HI All, I have been struggling some days with getting the programming environment in place. I have followed the instructions on setting up the toolchain according to: http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core I have installed MIOS32 from SVN in : C:\Users\jillejille\Documents\MIOS32\trunk If I open a command window on one of the tutorial projects: C:\Users\jillejille\Documents\MIOS32\trunk\apps\tutorials\001_forwarding_midi and do a make the utility ends up in an endless loop not displaying anything. If I start make with -d switch I get endless lines of debug info. A snippet of that output is included below: Trying pattern rule with stem `freertos_heap.d'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.p'. Looking for a rule with intermediate file `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.p'. Avoiding implicit rule recursion. Avoiding implicit rule recursion. Trying pattern rule with stem `freertos_heap.d'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.web'. Trying pattern rule with stem `freertos_heap.d.p'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.p,v'. Trying pattern rule with stem `freertos_heap.d.p'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/RCS/freertos_heap.d.p,v'. Trying pattern rule with stem `freertos_heap.d.p'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/RCS/freertos_heap.d.p'. Trying pattern rule with stem `freertos_heap.d.p'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/s.freertos_heap.d.p'. Trying pattern rule with stem `freertos_heap.d.p'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/SCCS/s.freertos_heap.d.p'. Trying pattern rule with stem `freertos_heap.d'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.web'. Looking for a rule with intermediate file `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.web'. Avoiding implicit rule recursion. Avoiding implicit rule recursion. Avoiding implicit rule recursion. Trying pattern rule with stem `freertos_heap.d.web'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/freertos_heap.d.web,v'. Trying pattern rule with stem `freertos_heap.d.web'. Trying implicit prerequisite `project_build//C/Users/jillejille/Documents/MIOS32/trunk/programming_models/traditional/RCS/freertos_heap.d.web,v'. Environment variables are set up as follows: MIOS32_BIN_PATH=C:\Users\jillejille\Documents\MIOS32\trunk\bin MIOS32_BOARD=MBHP_CORE_LPC17 MIOS32_FAMILY=LPC17xx MIOS32_GCC_PREFIX=arm-none-eabi MIOS32_LCD=universal MIOS32_PATH=/C/Users/jillejille/Documents/MIOS32/trunk MIOS32_PROCESSOR=LPC1769 Path is setup as: Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32 \WindowsPowerShell\v1.0\;C:\MSYS\1.0\bin;c:\mios32_toolchain\bin;C:\Program File s\TortoiseSVN\bin;C:\Program Files\Microchip\xc8\v1.33\bin This runs on a 32 bits Win7 machine Any pointers how to solve this would be welcome... regards Hans

Ha! :) got it working! I now used update_without_installed_mios.hex and that worked OK! Could upload application. All seems well. Thanks for the hints, Throsten. I'll keep you updated about sd-card progress... regards: Hans

Hi Thorsten, I tried your suggestion but without success... Some more info: The board already worked previously. I demolished the PIC when I was trying to solder an additional power circuit for sd-card support. I ordered 2 PIC18F452's at Wouter van Ooijen's web shop who also programmed the bootloader for me. I indicated the MIDIBOX website for download so I assume he burned the latest bootloader. I'll check with him... When I started I noticed the repetitive download requests. So, the bootloader was there and no MIOS installed. Then, I used MIOS Studio to upload MIOS with the results as displayed in the LOG file in my previous message in this thread. When I use smart mode the process stops when hitting the 0x07c00 address range. When I use manual mode the process continues but repeatedly complains about write errors in the 0x7c00 to 0x7fff range. The LCD keeps displaying the single black top-line. It used to work before, however due to fault connection at a point I may have destroyed it. So this is currently not a reliable monitor for signs of MIOS life. After MIOS upload a reboot of the board now gives only two sysex upload requests which may indicate that at least part of the MIOS upload was succesfull. When I tried to upload: update_with_old_mios.hex the upload succeeded but the device did not automatically reboot. WHen I rebooted manually : no response on the LCD. To verify whether MIOS was alive I tried to upload an aplication but that failed with no response from the board. After reading some messages about power requirements during burning I repeated the process using a power adapter allowing 800mA. Without success. Are there any other options to check whether or what parts of MIOS are alive? I hope for any other pointers to solve this problem. regards: Hans

I have trouble uploading MIOS V 1.9 on my PIC18f452 board. :'( The log of the upload is included below. The problem occurs when the following block (write?) occurs: Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl This was an expected error - please ignore! The problem persists while trying several different settings in MIOS studio. Anybody got a clue what's going on? regards: Hans Starting upload of mios_v1_9d_pic18f452.hex Hex file contains code in MIOS range, forcing reboot! Received Upload Request Sending block 00000400-000004FF Received Checksum: 71 - OK Sending block 00000500-000005FF Received Checksum: 29 - OK Sending block 00000600-000006FF Received Checksum: 40 - OK Sending block 00000700-000007FF Received Checksum: 52 - OK Sending block 00000800-000008FF Received Checksum: 59 - OK Sending block 00000900-000009FF Received Checksum: 37 - OK Sending block 00000A00-00000AFF Received Checksum: 6B - OK Sending block 00000B00-00000BFF Received Checksum: 7E - OK Sending block 00000C00-00000CFF Received Checksum: 59 - OK Sending block 00000D00-00000DFF Received Checksum: 5A - OK Sending block 00000E00-00000EFF Received Checksum: 3E - OK Sending block 00000F00-00000FFF Received Checksum: 35 - OK Sending block 00001000-000010FF Received Checksum: 29 - OK Sending block 00001100-000011FF Received Checksum: 62 - OK Sending block 00001200-000012FF Received Checksum: 3A - OK Sending block 00001300-000013FF Received Checksum: 3E - OK Sending block 00001400-000014FF Received Checksum: 0D - OK Sending block 00001500-000015FF Received Checksum: 0B - OK Sending block 00001600-000016FF Received Checksum: 2B - OK Sending block 00001700-000017FF Received Checksum: 48 - OK Sending block 00001800-000018FF Received Checksum: 6D - OK Sending block 00001900-000019FF Received Checksum: 76 - OK Sending block 00001A00-00001AFF Received Checksum: 34 - OK Sending block 00001B00-00001BFF Received Checksum: 25 - OK Sending block 00001C00-00001CFF Received Checksum: 04 - OK Sending block 00001D00-00001DFF Received Checksum: 46 - OK Sending block 00001E00-00001EFF Received Checksum: 33 - OK Sending block 00001F00-00001FFF Received Checksum: 74 - OK Sending block 00002000-000020FF Received Checksum: 1A - OK Sending block 00002100-000021FF Received Checksum: 59 - OK Sending block 00002200-000022FF Received Checksum: 2D - OK Sending block 00002300-000023FF Received Checksum: 1B - OK Sending block 00002400-000024FF Received Checksum: 0A - OK Sending block 00002500-000025FF Received Checksum: 34 - OK Sending block 00002600-000026FF Received Checksum: 5C - OK Sending block 00002700-000027FF Received Checksum: 05 - OK Sending block 00002800-000028FF Received Checksum: 1C - OK Sending block 00002900-000029FF Received Checksum: 00 - OK Sending block 00002A00-00002AFF Received Checksum: 3B - OK Sending block 00002B00-00002BFF Received Checksum: 61 - OK Sending block 00002C00-00002CFF Received Checksum: 7D - OK Sending block 00002D00-00002DFF Received Checksum: 02 - OK Sending block 00002E00-00002EFF Received Checksum: 22 - OK Sending block 00002F00-00002FFF Received Checksum: 7E - OK Sending block 00003000-000030FF Received Checksum: 22 - OK Sending block 00003100-000031FF Received Checksum: 60 - OK Sending block 00003200-000032FF Received Checksum: 40 - OK Sending block 00003300-000033FF Received Checksum: 3F - OK Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl This was an expected error - please ignore! Error: Received unexpected Upload Request Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Sending block 00007C00-00007CFF Received error code 05: Write access failed (invalid address range) - used by 1st level bsl Aborting after 16 errors