Boot Monitor conflicts with connected device on MOD5270

[sblair]

Thanks Dan. Good to know!

I can understand not wanting to release your source code for Boot. What might be useful is having a compiled image that can be distributed and loaded via BDM. For example we used the PE Micro Cyclones for production programming a lot at my past job. http://www.pemicro.com/products/product ... ategory=12 Where we could just load a compiled image into it with the flashing script. Even their cheap USB/BDM dongles as I recall will take a compiled image and the script telling it how to program the flash.

Just food for thought!

Thanks.
Scott

[dciliske]

Good news: I think we can get you set up with the BDM procedure and image. Alternatively, we can also give you a monitor which would require entering an entire word to abort to the monitor.

Go ahead and submit a support ticket, and we can get that ball rolling. This way when you get stuck in a trap loop at 0 seconds delay, you can recover.

-Dan

[sblair]

Thanks Dan! Being able to have it silently boot without the alert message to enter the boot monitor and then entering an entire keyword would be great solutions so that hopefully I wouldn't get to the point of needing the BDM.

I'll wait a bit before opening a ticket on it to figure out whether I'll need this on the MOD5270 or not right away. I've got a dozen pilot units we built before the MOD54415 came out that may be going out on a big concert tour where I may need this solution we've discussed otherwise I'm trying to hold off until we get migrated to the 54415 where it won't be a problem as you mentioned because of the alternate boot monitor.

Thanks!
Scott

[dciliske]

Sounds good.