Author
Topic: 8 characters in the path or file name ? and starting AXON not on USB... (Read 1816 times)

I can download a program with the FBOOT GUI (that just rolls off your tongue doesn't it) that has more than 8 charaters in its path and file name but I thought I remembered reading something about an 8 charater limit. But, it will only start up if the board is connected to the USB and the computer is powered on.

It seems unlikely this has to do with any character limit (there are no spaces).

Anyway, at "power on" the program starts fine if the USB is plugged in. If not, it doesn't want to boot up and the program will not run. Program size is about 32K using a DroneCell/GPS/Display/Keypad configuration, like a homemade cell phone. Homemade cell is pretty worthless if I have to lug around my laptop too

The 8 character limit is if you use the FBOOT17.exe directly. I don't recall why. But it's one of the most frustrating things to forget about, and then subsequently lose hours tracing the problem down.

I'm not sure what's up with the actual problem you're describing... Are you using the USB's UART in your code? I've had problems (Axon light flashing, webbotlib error) when I use the other UART's in code, but don't have the physical UART's connected to anything.

I am using the 4 UARTs. 1 for the USB connection1 for a GPS module1 for a DroneCell modem1 for future expansion to OBD II data.

I will text, if I can figure out a way to get SMS into MySQL, or use a TCP connection to get the data to a record in MySQL but that's a story for another day.

If the Axon is connected to the computer via the USB and download a program it runs fine, and even if I shut down and restart the board via the switch (which is VERY convenient BTW) it still runs fine. All I need to do is have the USB plugged into a live computer.

If I unplug the USB, after checking just now and playing some more is I get weird characters on the LCD which in adjusting a delay on startup goes away except for I now have a flashing block as the location of the cursor so I need to figure out how to turn that off because it's bothersome.

But it appears to be working for whatever reason with the delay and perhaps there is a command I need to send to the LCD to turn off blinking cursor but I will check that out.

This is somewhat LCD influenced because USB plugged and poewered inits with a blank LCD and unplugged inits with rows 0 and 2 black box and 1 and 3 as clear instead of all clear when plugged into the USB, and as I said powered up.

For whatever reason having the USB plugged in and laptop powered up is the key, like it needs that power to the LCD or something. I'm running off a wall transformner that's at 6VDC output that is poretty clean according to the scope so power should be no problem on droops etc, although I haven't confirmed that and maybe it's charing the big cap. Is that the thing?

All grounds are connected by pluggin leads and are pretty solid.Grounds for the LCD are on the 5V regulated stripGrounds for the GPS are on the 5V regulated stripGrounds for the DroneCell are on the 6V (battery) strip

Yes the code is using the USB UART.

I'm beginning to suspect the capacitor charging time constant but does that explain the blinking cursor? I need to figure out how to set the default for that.

Maybe I misspoke. If I unplug the Axon after starting connected to the PC USB with power on the PC everything works fine, no problems.

It's only when I start/power up by the switch with USB unplugged and only getting power from the wall transformer that I get strange LCD behavior and on a rare occasion nothing comes up on the LCD although something is happening as LED blinks. I am getting more and more convinced this is a problem caused by charging the big cap. Is that possible? Maybe I should just sit idle for a bit longer at init.

A quick check of time constant on the cap.... at a 1K load that 3300uF cap has a time constant of 3.3 seconds, scales proportionate to that for higher loads. 2K is 6.6 vseconds and so on. And, that's just to get to 63% charge. Tomorrow I will try to get a trace on the scope to see what the voltage is doing, should have done that first I guess.

Does the USB connection actually keep the capacitor charged?

SPI is setup in the project from Project Designer (Webbotlib) but not yet implemented for an SD card, so no connections to those pins yet.

What is your current draw? Yea, definitely see what the voltage is doing. Your wall wart could be acting funny.

Quote

It's only when I start/power up by the switch with USB unplugged and only getting power from the wall transformer that I get strange LCD behavior and on a rare occasion nothing comes up on the LCD although something is happening as LED blinks.

Ok, so everything else works fine, but just the LCD acts strange?

Do you have the LED blinking in your code? A blinking LED could mean your mcu is resetting.

Quote

SPI is setup in the project from Project Designer (Webbotlib) but not yet implemented for an SD card, so no connections to those pins yet.

I'm not using a debug adapter so I can't see what registers or ports are doing but....

infrequently but it has happened..... yes the LED blinks but not like it's resetting in fact it's very rythmic 8 flashes and a pause, 8 flashes and a pause, and so on that may have originated by a reset, but the flashing doesn't occur every power up. I suspect there is a timing issue with the DroneCell also doing an init and not related to anything else.

The real manifistation of odd behavior is what the LCD does during power up (with or without the USB plugged in) and ultimately do I have a blinking cursor or no blinking cursor. I don't mind the blinking cursor, but would prefer to be able to turn it on or off with software, not left to chance. So, before I go on with this I need to resolve this LCD issue.

I'll check voltage across the cap tomorrow and try to get a current reading.

// There is no appropriate prescale value for the frequency you want#define NO_APPROPRIATE_TIMER_PRESCALE_VALUES -8Which I have no idea what that's referring to

This error can also be verified if you have the UART assigned to error messages (assigned when you generate the project code) hooked up to Hyperterminal or PuTTY (or similar) on the computer. What I see when I have errors is "WebbotlibError: 11", or something like that...

--------------

There's also a way to do a remote reset of the Axon without actually toggling power. Admin knows more about that. This might help indicate if it's a problem related to the capacitor. The test would go like this:1. USB plugged in, power axon on, display works2. Unplug USB3. Trigger Axon reset (again, I don't know how this step is done)4.

Or more precisely - WebbotLib is trying to report an error as to why your code isn't working. Not necessarily a problem caused by WebbotLib - but may be something Project Designer could alert you about beforehand. It could be that you are trying to use the same timer for lots of different things - some quick and some slow. Hence the 'NO_APPROPRIATE_TIMER_PRESCALE_VALUES' error - ie - it cannot set up the timer to cope suitably.

Without at least a Project File (.prj), and preferably some code, then its just speculation.

@Lester: if you don't want to post it on this website for any reason then feel free to email it to me direct.

I am beginning to suspect the timing issue is the source of the error codes.

My project file is attached as a .txt I suppoose a simple rename to prj will suffice?

My sincere apologies for the delays but work is upside down with layoffs etc and reorg so first things first. If there is something odvious in my project file I'd appreciate aheads up. I will get back on it in due course.