sprintf

hello , after a few problems my LPC_ NG is running again. im wondering if there is a way to offset the display ( shift to the right ) by 1 or 2 pixels . since my 1.3" SSD1306 are shifted 1 (or 2?) pixels to the left . if im doing the offset via ngc ( which would be a workaround ) im losing a couple more pixels . ( since shifting the letters one position to the right , id loose a letter ) in mios32_lcd.h the offset is "forbidden" ( it says : // fixed format, dont change! ) is there a way to do this , other than via ngc ? ps : im happy to be back working on this after many years :)

Thank you , im measuring something similar . so this seems normal . i can replicate the behaviour now and i hope this will help to track down my problem . when i connect my core with NG 1.036 to a external psu ( no usb data connection ) the app / core is always starting properly . when i connect the core to usb ( as long as there is no data handshake with mios , ableton or any software ) it will boot fine . when the core is connected to usb (power) and i start mios or any other app on the mac (e.g. ableton , logic etc ) the core is crashing. the hard fault adress is always 0x000189ce . i can workaround this crash if i boot with "Bootloader HOLD Mode jumper" and remove the jumper afterwards. how can i find out about the hard fault adress ? ps . you are right about "disable UART.." from config file . this is preventing the hard fault (as well) . but then i loose the midi in / out ( 5 pole DIN ) :( actually after reactivating UART and reducing encoders ( from 125 to 33 ) as well as reducing aout channels (from 32 to 8) , the hard fault seems to have vanished. i still would like to know how to find and identify the hard fault adress

hello again . i also have hard faults with 1.036 now . but only every 2nd or third time i reconnect the usb cabel . im wondering if maybe something got seriously damaged . how warm will the lpc get usually ? the mcu is getting warm . i can still touch it but im wondering why it is warm at all with such small duties . this is the normal official release from the download page . is there a way to identify the hard fault adress ?

Looks very nice and neat .I didnt know you are so busy with things . (Thank you for your support). I was working a lot with max/msp and m4l too. Its a lot of fun , but it takes a lot of time as well :) . Enjoy and keep up this amazing work.

It is confirmed the actual NG-Firmware was not tested for a LPC-Core (maybe someone made changes, but tested it only on STM32? The actual NG Release (1.037) in the github trunk does not work on LPC-Core ! see this thread :

Thank you for all your effort . I was really getting frustrated . _ this is really sad news , since i was actually working with this release . now i cant compile any more. UART here , has either something to do with Ethernet / RS-232 Interface or a Serial Connection ? i will check if i can use the release properly without UART .

vielen dank , dann habe ich das richtig gedacht. so werde ich es auch machen .

so this means , its better to edit the mios-config , before i compile ,right ?

could you ,please try to compile the ng from the github trunk and see if its working ?

this version is what comes out when you compile ng from the actual github trunk . i successfully used it for maybe 2 weeks now. then suddenly it broke . and i cant even use it after i compiled it again from src . ??

i used the ngc to deactivate srios . i only use 4 at the moment. the display says HARD FAULT and (meanwhile) changing hex codes.

sorry , i forgot to write its LPC. strange. how its possible that suddenly it happened . even with a freshly compiled one ?

project.hex

mios32_config.h

it wont let me upload the file .